Summary: | portage/eix-0.13.3 failed to emerge due to missing module docutils.core | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Sascha <sjirous> |
Component: | Third-Party Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Sascha
2008-09-20 23:31:02 UTC
I just updated dev-python/docutils-0.4-r1 to 0.4-r3, and afterwards eix could successfully be emerged. IMHO dependency of eix-0.13.3 to (at least) dev-python/docutils-0.4-r3 should be considered in ebuild. I can confirm this bug. I had dev-python/docutils-0.4-r3 but after reemerging it, eix could actually be emerged. So adding a dependency as suggested in comment #1 would not have helped me. Just for reference, it's very likely that both of you forgot to run python-updater after upgrading from python-2.4 to 2.5 (so python-2.5 was used, but the docutils modules (and all others as well) were in the 2.4 site-packages directory). (In reply to comment #3) I tend to exclude that was the issue. I had docutils-0.5 installed and python2.6 only. emerging eix gave me the same error, and the only way to successfully emerge it has been to re-emerge docutils. To give you guys some more information, I had no other slots of python installed, no residuals from python recovery (you know, if you accidentally unmerge it and install another version manually, it puts files in /usr/local/* instead of /usr etc.), and obviously running python-updater did notghing beacuse nothing had to be done. (In reply to comment #4) excuse me, I forgot to specify the eix version: this happened to me with eix-0.16.0 |