Should detect when a sub package is erroneously used as a root package

[aubade]

Original title: Regression: Dub 0.9.23 and 0.9.24-b2 cannot find subdirectory-based-subpackage dependency for in-file subpackage.

I've got a rather complex project with a subPackage structure like this:

"subPackages":[
    "./Engine/",
    "./Vanilla/",
    "./ICE/",
    {
        "name":"enginetest",
        "targetType":"executable",
        "targetName":"ICE-test",
        "targetPath":"bin",
        "version":"~master",
        "dependencies": {
            "ice:engine":"~master"
        },
        "sourceFiles":["TestApps/testcode2.d"]
    }

]

(The reason for the mixed subpackage structure is that there are several completely independent source files in TestApps/; they're interactive programs for testing things that unit tests really can't)

ice:engine is defined in the subfolder Engine's dub.json file. Dub 0.9.22 was able to resolve this fine, but both 0.9.23 and the latest beta of 0.9.24 error out with the error "Unknown dependency: ice:engine" when building the package.

[s-ludwig]

I tried to reproduce this in 90aa0f1, but everything there works. Is there anything else in your project that could influence this? Any chance of extracting all of the involved package description files for a reproduction case? The output of dub --verbose may also give some hints.

BTW, you should just remove all ~master references there. For referencing sub packages, use "*" and the version of all packages will be inferred, so using an explicit "version" field is usually not required.

[aubade]

Okay! I found the problem! It was expecting it to be called "engine", because of an entry in dub's local-packages file that was either old or mis-entered. Removing the local-packages file made things work fine! Sorry to trouble you.

[s-ludwig]

Oh okay, I see. Sounds like something that DUB should detect on its own, though. I'll change the title and leave this open.