Calculating dependencies ...done! >>> emerge (1 of 2) dev-python/pyvorbis-1.4-r1 to / >>> md5 files ;-) pyvorbis-1.3.ebuild >>> md5 files ;-) pyvorbis-1.4-r1.ebuild >>> md5 files ;-) pyvorbis-1.4.ebuild >>> md5 files ;-) pyvorbis-1.1.ebuild >>> md5 files ;-) files/pyvorbisfile.c-1.4.patch >>> md5 files ;-) files/digest-pyvorbis-1.4-r1 >>> md5 files ;-) files/digest-pyvorbis-1.1 >>> md5 files ;-) files/digest-pyvorbis-1.3 >>> md5 files ;-) files/digest-pyvorbis-1.4 >>> md5 src_uri ;-) pyvorbis-1.4.tar.gz >>> Unpacking source... >>> Unpacking pyvorbis-1.4.tar.gz to /var/tmp/portage/pyvorbis-1.4-r1/work * Applying pyvorbisfile.c-1.4.patch ... [ ok ] >>> Source unpacked. Checking for Ogg ... success Checking for Vorbis ... success Wrote Setup file You must have the Ogg Python bindings installed in order to build and install these bindings. Import of ogg._ogg failed. !!! ERROR: dev-python/pyvorbis-1.4-r1 failed. !!! Function distutils_src_compile, Line 35, Exitcode 1 !!! compilation failed !!! If you need support, post the topmost build error, NOT this status message.
Created attachment 75593 [details] my emerge info output
emerge sync, re-emerge pyogg (dev-python/pyogg-1.3-r1) and try to emerge pyvorbis again. Works fine for me
emerge sync, re-emerge pyogg (dev-python/pyogg-1.3-r1) and try to emerge pyvorbis again. Works fine for me (In reply to comment #1) > Created an attachment (id=75593) [edit] > my emerge info output >
*Before* re-emerging I have this: # emerge -s pyogg Searching... [ Results for search key : pyogg ] [ Applications found : 1 ] * dev-python/pyogg Latest version available: 1.3-r1 Latest version installed: 1.3-r1 Size of downloaded files: 23 kB Homepage: http://www.andrewchatham.com/pyogg/ Description: Python bindings for the ogg library License: LGPL-2 So while re-emerging is a great work-around (it worked for me), there is obviously something subtle missing from the ebuild (compile time dependency?). I clean out /var/tmp/portage/ from time to time, if that helps.
most likely you upgraded python and didn't run python-updater?
I have never run python-updater, and I only update python when portage makes forces me to do so because it is a pre-requ for something else. If python-updater is the problem, then perhaps it is missing from the python ebuild.
no no, you should run python-updater if you're upgrading major versions of python. try just running /usr/sbin/ptyhon-updater and see if it thinks you need to upgrade any packages.
Why shouldn't the ebuild run python-updater for me as needed?
The only place that python-updater is mentioned in the Gentoo documentation is the Gnome 2.12 Upgrade Guide (according to Google). So I doubt many end-users actually know the thing exists. So IMHO, it should automagically run at the end of the python ebuild; it would save you folks alot of python-upgrade related bug reports in the future. By the way, I ran it as you suggested and it emerged about 12 packages. I hope that, like revdep-rebuild, the emerge uses the --oneshot option.
Python-updater is mentioned everytime you emerge python. Unfortunately we can't automatically run it from the ebuild (running emerge inside another emerge is not allowed).
