Portage require packege dirs and names be the same but doesn't have an axplicit test about it. /portage/app-foo/bar/bar-1.2.ebuild is ok and /portage/app-foo/bar/bar-doc-1.2.ebuild is not Reproducible: Always Steps to Reproduce: matteo matteo # ebuild app-office/scribus/scribus-temp-all-1.2.ebuild digest Note that for my error path and package name differs! Actual Results: I get this error that doesn't help me a lot. !!! aux_get(): ebuild path for 'app-office/scribus-temp-all-1.2' not specified: !!! None !!! /app-office/scribus-temp-all/scribus-temp-all-1.2.ebuild not found in any porttrees! !!! aux_get(): ebuild path for 'app-office/scribus-temp-all-1.2' not specified: !!! None doebuild(): aux_get() error; aborting. Expected Results: Adding this two line at line 5000 of portage.py: else: print "!!! /"+mysplit[0]+"/"+psplit[0]+"/"+mysplit[1]+".ebuild"+" not found in porttrees!" I can have this explaining error: !!! /app-office/scribus-temp-all/scribus-temp-all-1.2.ebuild not found in any porttrees! [... same as before ...] Now I can see some portage internal pathmagicks and correct my error.
Fixed a while ago.
*** Bug 80813 has been marked as a duplicate of this bug. ***
Released in 2.0.53_rc6