The latest ebuild of dev-python/pyvorbis-1.4-r1 seems to be directly dependant on dev-python/pyogg. However, portage doesn't seem to handle this dependancy. See this thread: http://forums.gentoo.org/viewtopic-t-414704-highlight-pyvorbis.html It can be reproduced: # emerge dev-python/pyvorbis-1.4-r1 Workaround: # emerge -av pyogg pyvorbis
Every single version depends on it, just read the ebuild. You didn't run python-updater after upgrading python, apparently. *** This bug has been marked as a duplicate of 121686 ***
How this is not a bug? I should be able to update my system automatically any time, or be informed of what needs to be done, to be updated, not just some package breakage. Because it is breakage of portage, since it does not say, for me to run python-update. At the very least when python related package that needs python update , should inform me that I need to do this. rsync out.
(In reply to comment #2) Thats what I thought when I posted this "bug". This is a nasty flaw and really has no place in portage, which up until now I've had very few problems with. I expect an "emerge -uavDN world" to be successfull without me having to interfere. Is there anything preventing us from automatically executing a simple "python-updater" command after updating python? I'm just curious.
(In reply to comment #2) > How this is not a bug? I should be able to update my system automatically any > time, or be informed of what needs to be done, to be updated, not just some > package breakage. Because it is breakage of portage, since it does not say, for > me to run python-update. At the very least when python related package that > needs python update , should inform me that I need to do this. > rsync out. Kindly read the einfo you get when upgrading python more carefully. (In reply to comment #3) > Is there anything preventing us from automatically executing a > simple "python-updater" command after updating python? I'm just curious. Yes. Calling emerge from within emerge is not safe, and won't happen (likewise with perl-cleaner etc.) *** This bug has been marked as a duplicate of 121686 ***
