* indexing: 741 ebuilds to go !!! Problem with determining the name/location of an ebuild. !!! Please report this on IRC and bugs if you are not causing it. !!! mycpv: www-apps/hotsanic-0.5.0-pre5 !!! mysplit: ['www-apps', 'hotsanic-0.5.0-pre5'] !!! psplit: None !!! error: unsubscriptable object Reproducible: Always Steps to Reproduce: 1. 2. 3. i am working on a hotsanic ebuild in PORTDIR_OVERLAY, and that is it.. esearch probably should ignore PORTDIR_OVERLAY or something
there is no package called 'hotsanic' the package version looks wrong anyways
That's right, there is no package in portage called hotsanic yet, but I am working on ebuilds in my /usr/local/portage directory (portage overlay). I reopened the bug because I am not sure the intended behavior is to break when it comes across ebuilds in the portage overlay dir. Is there any way I can alter my ebuilds so that they don't cause eupdatedb to break?
i told you already the version info on that ebuild looks wrong esearch uses portage as the backend so in reality, it's portage barfing on bad ebuilds, not esearch