On Thu, 15 Jan 2015 11:36:55 +0100, Sönke Ludwig wrote:

Am 05.01.2015 um 17:25 schrieb Luís Marques:

Hey, what am I doing wrong here? 

$ dub list
(...)
glfw-drey 0.0.2: /Users/luismarques/.dub/packages/glfw-drey-0.0.2/
(...)

$ dub add-override glwtf-drey 0.0.2 ~/Projects/glwtf-drey/

$ dub build
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
Package override glwtf-drey 0.0.2 ->  /Users/luismarques/Projects/glwtf-drey/ doesn't reference an existing package.
(...)

$ head -n 2 /Users/luismarques/Projects/glwtf-drey/dub.json
{
	"name": "glwtf-drey",

Hmm, I'll probably need to reproduce that locally, maybe some kind of
issue with the way the tilde is expanded? Can you have a look at the
output of dub build --vverbose to see if there are any additional
clues? In any case, that error message should be extended to name the
exact reason for why it doesn't consider a path a valid package path.

I tried without the tilde. It's not the issue. I don't see anything relevant in the verbose output. I also tried with git head of dub. BTW, the dub list in my original post was incorrectly trimmed to glfw-drey (not glwtf-drey) but I also had glwtf-drey on the list.