What is the solution to this:

Unresolvable dependencies to package libdparse:
  dfmt ~master depends on libdparse ~>0.10.7
  libddoc 0.4.0 depends on libdparse ~>0.9.0
Failed to install serve-d (Error code 2)



Where can i download libdparse 0.10.7

The full error file below. i am on windows 10

Installing into C:\Users\Greatsam\AppData\Roaming\code-d\bin
Removing old version
Removed old version
> git clone --recursive https://github.com/Pure-D/serve-d.git serve-d
Cloning into 'serve-d'...
> dub upgrade
Upgrading project in C:\Users\Greatsam\AppData\Roaming\code-d\bin\serve-d
Unresolvable dependencies to package libdparse:
  dfmt ~master depends on libdparse ~>0.10.7
  libddoc 0.4.0 depends on libdparse ~>0.9.0
Failed to install serve-d (Error code 2)

On Wednesday, 14 November 2018 at 13:20:31 UTC, greatsam4sure wrote:
> What is the solution to this:
>
> Unresolvable dependencies to package libdparse:
>   dfmt ~master depends on libdparse ~>0.10.7
>   libddoc 0.4.0 depends on libdparse ~>0.9.0
> Failed to install serve-d (Error code 2)
>
>
>
> Where can i download libdparse 0.10.7
>
> The full error file below. i am on windows 10
>
> Installing into C:\Users\Greatsam\AppData\Roaming\code-d\bin
> Removing old version
> Removed old version
>> git clone --recursive https://github.com/Pure-D/serve-d.git serve-d
> Cloning into 'serve-d'...
>> dub upgrade
> Upgrading project in C:\Users\Greatsam\AppData\Roaming\code-d\bin\serve-d
> Unresolvable dependencies to package libdparse:
>   dfmt ~master depends on libdparse ~>0.10.7
>   libddoc 0.4.0 depends on libdparse ~>0.9.0
> Failed to install serve-d (Error code 2)

Hi,

thanks for the report, I tagged a new version of workspace-d which will fix this issue.

Simply reload vscode and let it rebuild to fix.

Issue was: for a long time dfmt didn't get a new tagged release and wasn't compatible with the dscanner and libdparse version I used anymore, so I changed it to use ~master instead. Since a few days it has been tagged and it was added to workspace-d ~master but serve-d still uses the latest tagged release.

So as dfmt now got updated to an even newer libdparse, the other components don't match that libdparse version anymore and now dfmt is too new for it...

It's a real pain that you can't select specific commits in dub, but I try to keep up with the updates and make them work somehow. Sometimes it feels like unnecessary major (minor) version bumps that just break all the version compatibility with barely any backwards incompatibility in the code.

On Wed, 14 Nov 2018 19:28:44 +0000, WebFreak001 wrote:
> It's a real pain that you can't select specific commits in dub, but I try to keep up with the updates and make them work somehow.

Yeah, I've used submodules and path-based dependencies once or twice because of that. It's not the best.

On Wednesday, 14 November 2018 at 20:44:26 UTC, Neia Neutuladh wrote:
> On Wed, 14 Nov 2018 19:28:44 +0000, WebFreak001 wrote:
>> It's a real pain that you can't select specific commits in dub, but I try to keep up with the updates and make them work somehow.
>
> Yeah, I've used submodules and path-based dependencies once or twice because of that. It's not the best.

that would be the best solution if you don't publish your package to the dub registry. If you do publish it you have all the problems with it not cloning your repo recursively.

On Wednesday, 14 November 2018 at 19:28:44 UTC, WebFreak001 wrote:
> On Wednesday, 14 November 2018 at 13:20:31 UTC, greatsam4sure wrote:
>> [...]
>
> Hi,
>
> thanks for the report, I tagged a new version of workspace-d which will fix this issue.
>
> Simply reload vscode and let it rebuild to fix.
>
> Issue was: for a long time dfmt didn't get a new tagged release and wasn't compatible with the dscanner and libdparse version I used anymore, so I changed it to use ~master instead. Since a few days it has been tagged and it was added to workspace-d ~master but serve-d still uses the latest tagged release.
>
> So as dfmt now got updated to an even newer libdparse, the other components don't match that libdparse version anymore and now dfmt is too new for it...
>
> It's a real pain that you can't select specific commits in dub, but I try to keep up with the updates and make them work somehow. Sometimes it feels like unnecessary major (minor) version bumps that just break all the version compatibility with barely any backwards incompatibility in the code.

thanks,fix after reloading vs code several times with internet connection. DCD was not downloaded i have to manually download it, extract it and copy dcd-client.exe and dcd-server.exe to code-d\bin and set up the path in vs code for auto completion to work