RejectedSoftware Forums

Sign up

Dub fails to fetch the correct version

Running "dub fetch dstep" it fails to fetch the latest version
"0.1.0+dub" but succeeds when falling back to master. This is the output:

Fetching dstep 0.1.0+dub...
Placing dstep 0.1.0+dub to /Users/doob/.dub/packages/...
Getting a release version failed: ZipException: no end record
Retry with ~master...
Fetching dstep ~master...
Placing dstep ~master to /Users/doob/.dub/packages/...

When I tried to fetch "dstep" again I got the following output in
addition (before) the output above:

Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'
Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'

The package description in /Users/doob/.dub/packages/mambo-0.0.1-alpha
looks like this:

http://pastebin.com/sEZ4hGNB

Which isn't exactly like it looks in the repository:

https://github.com/jacob-carlborg/mambo/blob/master/dub.json

Running "dub fetch dstep -vv" (I was hoping for a more verbose output)
resulted in this error:

Error processing arguments: Can't parse string: bool should be
case-insensitive 'true' or 'false'
Run 'dub help' for usage information.

If think the error message isn't very descriptive. It should say
something like there isn't a flag "-vv".

Running with verbose output enabled I got this:

http://pastebin.com/zWWt1quE

Running "dub --foo" results in this error:

Error executing command run: Failed to find a package named '--foo'.

I'm wondering if it would be better if Dub assume anything that starts
with a one dash or two dashes is a flag. In this case it's an invalid
flag and Dub would give a descriptive error message for this.

This turned out to be a couple of issues. Perhaps I should reported them
separately on Github?

/Jacob Carlborg

Re: Dub fails to fetch the correct version

Am 21.01.2014 10:36, schrieb Jacob Carlborg:

Running "dub fetch dstep" it fails to fetch the latest version
"0.1.0+dub" but succeeds when falling back to master. This is the output:

Fetching dstep 0.1.0+dub...
Placing dstep 0.1.0+dub to /Users/doob/.dub/packages/...
Getting a release version failed: ZipException: no end record
Retry with ~master...
Fetching dstep ~master...
Placing dstep ~master to /Users/doob/.dub/packages/...

When I tried to fetch "dstep" again I got the following output in
addition (before) the output above:

Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'
Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'

The package description in /Users/doob/.dub/packages/mambo-0.0.1-alpha
looks like this:

http://pastebin.com/sEZ4hGNB

Which isn't exactly like it looks in the repository:

https://github.com/jacob-carlborg/mambo/blob/master/dub.json

Running "dub fetch dstep -vv" (I was hoping for a more verbose output)
resulted in this error:

Error processing arguments: Can't parse string: bool should be
case-insensitive 'true' or 'false'
Run 'dub help' for usage information.

If think the error message isn't very descriptive. It should say
something like there isn't a flag "-vv".

Running with verbose output enabled I got this:

http://pastebin.com/zWWt1quE

Running "dub --foo" results in this error:

Error executing command run: Failed to find a package named '--foo'.

I'm wondering if it would be better if Dub assume anything that starts
with a one dash or two dashes is a flag. In this case it's an invalid
flag and Dub would give a descriptive error message for this.

This turned out to be a couple of issues. Perhaps I should reported them
separately on Github?

It seems to not like the "+" in the version. Fixing.

Re: Dub fails to fetch the correct version

On Tue, 21 Jan 2014 11:21:24 +0100, Sönke Ludwig wrote:

Am 21.01.2014 10:36, schrieb Jacob Carlborg:

Running "dub fetch dstep" it fails to fetch the latest version
"0.1.0+dub" but succeeds when falling back to master. This is the output:

Fetching dstep 0.1.0+dub...
Placing dstep 0.1.0+dub to /Users/doob/.dub/packages/...
Getting a release version failed: ZipException: no end record

This part is fixed now, see below.

Retry with ~master...
Fetching dstep ~master...
Placing dstep ~master to /Users/doob/.dub/packages/...

When I tried to fetch "dstep" again I got the following output in
addition (before) the output above:

Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'
Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'

I couldn't reproduce this part.

The package description in /Users/doob/.dub/packages/mambo-0.0.1-alpha
looks like this:

http://pastebin.com/sEZ4hGNB

Which isn't exactly like it looks in the repository:

https://github.com/jacob-carlborg/mambo/blob/master/dub.json

Running "dub fetch dstep -vv" (I was hoping for a more verbose output)
resulted in this error:

Error processing arguments: Can't parse string: bool should be
case-insensitive 'true' or 'false'
Run 'dub help' for usage information.

If think the error message isn't very descriptive. It should say
something like there isn't a flag "-vv".

This seems to be an issue of std.getopt. The correct flag is --vverbose.

Running with verbose output enabled I got this:

http://pastebin.com/zWWt1quE

Running "dub --foo" results in this error:

Error executing command run: Failed to find a package named '--foo'.

I'm wondering if it would be better if Dub assume anything that starts
with a one dash or two dashes is a flag. In this case it's an invalid
flag and Dub would give a descriptive error message for this.

That's what I'm thinking is the best solution, too.

This turned out to be a couple of issues. Perhaps I should reported them
separately on Github?

It seems to not like the "+" in the version. Fixing.

Original issue fixed by
vibe.d: 11393a4

And made more solid by
dub: 53f0a89 daea72b
dub-registry: bb4beb5

GitHub seems to be a bit overloaded currently and often throws 500 errors or times out, so a few re-tries may be necessary.

Re: Dub fails to fetch the correct version

On Tue, 21 Jan 2014 12:17:52 GMT, Sönke Ludwig wrote:

On Tue, 21 Jan 2014 11:21:24 +0100, Sönke Ludwig wrote:

Am 21.01.2014 10:36, schrieb Jacob Carlborg:

Running "dub --foo" results in this error:

Error executing command run: Failed to find a package named '--foo'.

I'm wondering if it would be better if Dub assume anything that starts
with a one dash or two dashes is a flag. In this case it's an invalid
flag and Dub would give a descriptive error message for this.

That's what I'm thinking is the best solution, too.

Implemented by d5fdb2a.

Re: Dub fails to fetch the correct version

On Tue, 21 Jan 2014 12:17:52 GMT, Sönke Ludwig wrote:

On Tue, 21 Jan 2014 11:21:24 +0100, Sönke Ludwig wrote:

Am 21.01.2014 10:36, schrieb Jacob Carlborg:

When I tried to fetch "dstep" again I got the following output in
addition (before) the output above:

Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'
Failed to parse package description in
/Users/doob/.dub/packages/mambo-0.0.1-alpha
Failed to load package in /Users/doob/.dub/packages/mambo-0.0.1-alpha:
No/Unknown comparision specified: '==~d'

I couldn't reproduce this part.

After a little more trying I got it to reproduce. Fixed by dee53b8.

Re: Dub fails to fetch the correct version

On 2014-01-21 13:31, Sönke Ludwig wrote:

After a little more trying I got it to reproduce. Fixed by dee53b8.

Thanks for the quick response and all the fixes.

/Jacob Carlborg