"Unknown dependency: vibe-d" when building ddox

[Geod24]

geod@Barsoom:~/dub$ rm -rf ~/.dub/packages/*
geod@Barsoom:~/dub$ dub init testdoc vibe.d
Successfully created an empty project in '/home/geod/dub/testdoc'.
geod@Barsoom:~/dub$ cd testdoc/
geod@Barsoom:~/dub/testdoc$ dub --build=ddox
Fetching vibe-d 0.7.20 (getting selected version)...
Placing vibe-d 0.7.20 to /home/geod/.dub/packages/...
Fetching libevent ~master (getting selected version)...
Placing libevent ~master to /home/geod/.dub/packages/...
Fetching openssl ~master (getting selected version)...
Placing openssl ~master to /home/geod/.dub/packages/...
Fetching libev ~master (getting selected version)...
Placing libev ~master to /home/geod/.dub/packages/...
Building configuration "libevent", build type ddox
Running dmd...
[DDOC warnings...]
Building configuration "application", build type ddox
Running dmd...
DDOX is not present, getting it and storing user wide
Fetching ddox 0.9.22...
Placing ddox 0.9.22 to /home/geod/.dub/packages/...
DDOX in /home/geod/.dub/packages/ddox-0.9.22/ is not built, performing build now.
Error executing command run: Unknown dependency: vibe-d

Which is pretty odd, as I have no problem building the app itself. My dub built on master.
Can you reproduce ?

Note: dub build inside ~/.dub/packages/ddox-0.9.22 worked fine.

[s-ludwig]

I've tried on Windows (removing all local packages first) and didn't get an error there. Which version does dub -h print for you?

[Geod24]

DUB version 0.9.21, built on Jul 3 2014

Oddly it doesn't show the github commit anymore. Is it on purpose ?

But it's built from:
* 2586401 - (HEAD, upstream/master, master) Fix possible range violation error when accessing the upgrade cache. (21 hours ago) <Sönke Ludwig>

[s-ludwig]

Interesting, no, it should print the commit hash. Did you maybe build it with dub build instead of ./build.sh? But I'll try again to reproduce on Linux.

[Geod24]

Hum, yes I used dub.
I just rebuilt it using ./build.sh, get DUB version 0.9.22-beta.4+2-g2586401, built on Jul 3 2014 & the same error.

[p0nce]

Was able to reproduce this with the mentionned method, Windows machine, DUB version = 617bdf0
All dub state cleared (no local or installed packages).

[p0nce]

Making a regression bisection points to d2270a9 as the origin.
To expose the bug you should remove dub.selections.json after each DUB run else it might halt before.

[s-ludwig]

@p0nce Thanks for the further investigation. I think I've tracked it down to a missing call to upgrade(UpgradeOptions.select). Preparing the fix now.