the portage was up-to-date. $ sudo emerge revelation Calculating dependencies... done! >>> Verifying ebuild Manifests... >>> Emerging (1 of 1) x11-misc/revelation-0.4.11 to / * revelation-0.4.11.tar.bz2 RMD160 SHA1 SHA256 size ;-) ... [ ok ] * checking ebuild checksums ;-) ... [ ok ] * checking auxfile checksums ;-) ... [ ok ] * checking miscfile checksums ;-) ... [ ok ] * checking revelation-0.4.11.tar.bz2 ;-) ... [ ok ] >>> Unpacking source... >>> Unpacking revelation-0.4.11.tar.bz2 to /home/tmp/portage/x11-misc/revelation-0.4.11/work * Fixing OMF Makefiles ... [ ok ] >>> Source unpacked. >>> Compiling source in /home/tmp/portage/x11-misc/revelation-0.4.11/work/revelation-0.4.11 ... * econf: updating revelation-0.4.11/config.guess with /usr/share/gnuconfig/config.guess * econf: updating revelation-0.4.11/config.sub with /usr/share/gnuconfig/config.sub ./configure --prefix=/usr --host=powerpc-unknown-linux-gnu --mandir=/usr/share/man --infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc --localstatedir=/var/lib --disable-dependency-tracking --disable-desktop-update --disable-mime-update --build=powerpc-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for powerpc-unknown-linux-gnu-gcc... powerpc-unknown-linux-gnu-gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether powerpc-unknown-linux-gnu-gcc accepts -g... yes checking for powerpc-unknown-linux-gnu-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of powerpc-unknown-linux-gnu-gcc... none checking for a Python interpreter with version >= 2.3... python checking for python... /usr/bin/python checking for python version... 2.5 checking for python platform... linux2 checking for python script directory... ${prefix}/lib/python2.5/site-packages checking for python extension module directory... ${exec_prefix}/lib/python2.5/site-packages checking Python include path... /usr/include/python2.5 checking for powerpc-unknown-linux-gnu-pkg-config... no checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for PYGTK... yes checking for GNOME_PYTHON... yes checking for GNOME_PYTHON_EXTRAS... yes checking for pygtk-codegen-2.0... /usr/bin/pygtk-codegen-2.0 checking path to pygtk defs... /usr/share/pygtk/2.0/defs checking how to run the C preprocessor... powerpc-unknown-linux-gnu-gcc -E checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking build system type... powerpc-unknown-linux-gnu checking host system type... powerpc-unknown-linux-gnu checking for intltool >= 0.35.0... 0.35.0 found checking for perl... /usr/bin/perl checking for XML::Parser... ok checking for iconv... /usr/bin/iconv checking for msgfmt... /usr/bin/msgfmt checking for msgmerge... /usr/bin/msgmerge checking for xgettext... /usr/bin/xgettext checking locale.h usability... yes checking locale.h presence... yes checking for locale.h... yes checking for LC_MESSAGES... yes checking libintl.h usability... yes checking libintl.h presence... yes checking for libintl.h... yes checking for ngettext in libc... yes checking for dgettext in libc... yes checking for bind_textdomain_codeset... yes checking for msgfmt... /usr/bin/msgfmt checking for dcgettext... yes checking for gmsgfmt... /usr/bin/gmsgfmt checking for xgettext... /usr/bin/xgettext checking for catalogs to be installed... de checking for FascistCheck in -lcrack... yes checking cracklib dictionary database... using builtin checking for mkdict... no checking for crack_mkdict... no checking for cracklib-format... /usr/sbin/cracklib-format checking for packer... no checking for crack_packer... no checking for cracklib-packer... /usr/sbin/cracklib-packer checking for mlockall... yes checking for munlockall... yes checking for gconftool-2... /usr/bin/gconftool-2 Using config source xml:merged:/etc/gconf/gconf.xml.defaults for schema installation Using $(sysconfdir)/gconf/schemas as install directory for schema files checking for update-desktop-database... /usr/bin/update-desktop-database checking for update-mime-database... /usr/bin/update-mime-database checking python module Crypto... yes checking python module bonobo... no configure: error: failed to find module bonobo !!! Please attach the following file when seeking support: !!! /home/tmp/portage/x11-misc/revelation-0.4.11/work/revelation-0.4.11/config.log * * ERROR: x11-misc/revelation-0.4.11 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 1446: Called gnome2_src_compile 'src_compile' 'src_compile' '--disable-dependency-tracking' * environment, line 1083: Called gnome2_src_configure '--disable-desktop-update' '--disable-mime-update' '--disable-dependency-tracking' * environment, line 1097: Called econf '--disable-desktop-update' '--disable-mime-update' '--disable-dependency-tracking' * ebuild.sh, line 519: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/home/tmp/portage/x11-misc/revelation-0.4.11/temp/build.log'. * The ebuild environment file is located at '/home/tmp/portage/x11-misc/revelation-0.4.11/temp/environment'. * * Messages for package x11-misc/revelation-0.4.11: * * ERROR: x11-misc/revelation-0.4.11 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 1446: Called gnome2_src_compile 'src_compile' 'src_compile' '--disable-dependency-tracking' * environment, line 1083: Called gnome2_src_configure '--disable-desktop-update' '--disable-mime-update' '--disable-dependency-tracking' * environment, line 1097: Called econf '--disable-desktop-update' '--disable-mime-update' '--disable-dependency-tracking' * ebuild.sh, line 519: Called die * The specific snippet of code: * die "econf failed" * The die message: * econf failed * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/home/tmp/portage/x11-misc/revelation-0.4.11/temp/build.log'. * The ebuild environment file is located at '/home/tmp/portage/x11-misc/revelation-0.4.11/temp/environment'. *
Created attachment 168238 [details] A complete build log
Created attachment 168242 [details] The ebuild environment file
First I thought it depends on dev-python/libbonobo-python but not clearly specified in ebuilds, thus I try to emerge libbonobo-python and ends up requiring dev-python/gnome-desktop-python which blocks dev-python/gnome-python that I already installed. The fact there is "gnome-desktop-python" and "gnome-python" is wired to me enough, not knowing how things are called in the python world, gnome is a desktop environment so I don't see the difference of naming "gnome-desktop-python" and "gnome-python" It all starts that during emerging borg I was required to upgrade python, and some python application stopped working after the upgrade (even run python-updater). Others are fixed by re-emerge, but revelation failed to re-emerge. I also hit other several tons of problem during emerging borg, including getting my java-config broken, which is another story. Finally I found the shortest cut is to download borg from their website instead of emerging it. (OT)
I think you're right about the missing dev-python/libbonobo-python dependency. Can you show the output from your attempted merge of libbonobo-python? It seems wrong that these packages are blocking each other.
$ sudo emerge -av libbonobo-python These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/gnome-python-base-2.22.3 USE="-debug" 575 kB [ebuild N ] dev-python/libgnomecanvas-python-2.22.3 USE="-debug -examples" 0 kB [ebuild N ] dev-python/libbonobo-python-2.22.3 USE="-debug -examples" 0 kB [blocks B ] <dev-python/gnome-python-2.22.1 (is blocking dev-python/libbonobo-python-2.22.3, dev-python/gnome-python-base-2.22.3, dev-python/libgnomecanvas-python-2.22.3) Total: 3 packages (3 new, 1 block), Size of downloads: 575 kB !!! Error: The above package list contains packages which cannot be installed !!! at the same time on the same system. For more information about Blocked Packages, please refer to the following section of the Gentoo Linux x86 Handbook (architecture is irrelevant): http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?full=1#blocked
I think I solved this problem on my own notebook, though maybe you might think of a more general solution that works for everybody before you can say this bug can be closed. zhangweiwu@esmeralda:~$ equery depends gnome-python [ Searching for packages depending on gnome-python... ] dev-python/gnome-python-desktop-2.20.0 (>=dev-python/gnome-python-2.10.0) dev-python/gnome-python-extras-2.14.2-r1 (>=dev-python/gnome-python-2.10) zhangweiwu@esmeralda:~$ equery depends gnome-python-extras [ Searching for packages depending on gnome-python-extras... ] net-im/gajim-0.11.4 (gnome? dev-python/gnome-python-extras) x11-misc/revelation-0.4.11 (dev-python/gnome-python-extras) zhangweiwu@esmeralda:~$ equery depends gnome-python-desktop [ Searching for packages depending on gnome-python-desktop... ] net-im/gajim-0.11.4 (gnome? dev-python/gnome-python-desktop) x11-misc/revelation-0.4.11 (>=dev-python/gnome-python-desktop-2.16) zhangweiwu@esmeralda:~$ sudo emerge --unmerge gajim revelation gnome-python-desktop gnome-python-extras gnome-python dev-python/gnome-python-desktop selected: 2.20.0 protected: none omitted: none net-im/gajim selected: 0.11.4 protected: none omitted: none dev-python/gnome-python-extras selected: 2.14.2-r1 protected: none omitted: none x11-misc/revelation selected: 0.4.11 protected: none omitted: none dev-python/gnome-python selected: 2.20.1 protected: none omitted: none >>> 'Selected' packages are slated for removal. >>> 'Protected' and 'omitted' packages will not be removed. >>> Waiting 5 seconds before starting... >>> (Control-C to abort)... [...] zhangweiwu@esmeralda:~$ sudo emerge -pv revelation These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild N ] dev-python/gnome-python-2.20.1 USE="-debug -doc -examples" 0 kB [ebuild N ] dev-python/gnome-python-desktop-2.20.0 USE="-X -debug -doc" 430 kB [ebuild N ] dev-python/gnome-python-extras-2.19.1-r1 USE="-X -debug -doc -firefox -seamonkey -xulrunner" 354 kB [ebuild N ] x11-misc/revelation-0.4.11 USE="-debug" 0 kB Total: 4 packages (4 new), Size of downloads: 784 kB
However I still didn't succeed. dev-python/gnome-python-extras-2.19.1-r1 failed to compile. It can be another problem.
Created attachment 168264 [details] A complete build log for dev-python/gnome-python-extras-2.19.1-r1
This is how dev-python/gnome-python-extras-2.19.1-r1 failed. (I'll file in separte bug report if someone can point me out if this is unrelated to the problem reported first) [...] /bin/sh ../libtool --tag=CC --mode=link powerpc-unknown-linux-gnu-gcc -O2 -mcpu=G3 -fno-strict-aliasing -pipe -Wall -module -avoid-version -export-symbols-regex initgtkmozembed -R -o gtkmozembed.la -rpath /usr/lib/python2.5/site-packages/gtk-2.0 gtkmozembedmodule.lo gtkmozembed.lo -Wl,-R/usr/lib/nspr -L/usr/lib/xulrunner-1.9/lib -L/usr/lib/nspr -lxpcomglue_s -lxul -lxpcom -lplds4 -lplc4 -lnspr4 -lpthread -lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpangocairo-1.0 -lpango-1.0 -lcairo -lgobject-2.0 -lgmodule-2.0 -ldl -lglib-2.0 libtool: link: only absolute run-paths are allowed make[2]: *** [gtkmozembed.la] Error 1 make[2]: Leaving directory `/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/work/gnome-python-extras-2.19.1/gtkmozembed' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/work/gnome-python-extras-2.19.1' make: *** [all] Error 2 * * ERROR: dev-python/gnome-python-extras-2.19.1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3006: Called gnome2_src_compile * environment, line 2235: Called die * The specific snippet of code: * emake || die "compile failure" * The die message: * compile failure * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/temp/build.log'. * The ebuild environment file is located at '/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/temp/environment'. * * Messages for package dev-python/gnome-python-extras-2.19.1-r1: * * ERROR: dev-python/gnome-python-extras-2.19.1-r1 failed. * Call stack: * ebuild.sh, line 49: Called src_compile * environment, line 3006: Called gnome2_src_compile * environment, line 2235: Called die * The specific snippet of code: * emake || die "compile failure" * The die message: * compile failure * * If you need support, post the topmost build error, and the call stack if relevant. * A complete build log is located at '/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/temp/build.log'. * The ebuild environment file is located at '/home/tmp/portage/dev-python/gnome-python-extras-2.19.1-r1/temp/environment'. * * GNU info directory index is up-to-date.
in the gnome python world, packages name are after the library they bind. We now use splitted out versions since they used to be provided in 3 big blocks (which is why you see blockers btw). Since it seems you recently migrated to python 2.5, note that you have to run python-updater to the end before things start to work again. If it stops at some point, just emerge --resume --skipfirst and re-run python-updater once the first pass is done.
interlacely use python-updater and emerge --resume --skipfirst did not solve my problem of not being able to compile revelation, it still fail, with the same behavior as described in comment #9.
*** This bug has been marked as a duplicate of bug 232354 ***
