This bug looks exactly like bug #5098, but it occurs with the ~x86 version 2.10.1 of the ebuild. This prevents gnome-session-2.10.0.r2 from being configured. Fixed this by reverting to gconf-2.10.0. Tried moving forward to gconf-2.10.1 twice. Could not get /usr/bin/gconf-sanity-check-2 either time. Reproducible: Always Steps to Reproduce: 1. emerge gconf-2.10.1 2. emerge gnome-session-2.10.0-r2 3. Actual Results: Reports a failur to find "usrbin/gconf-sanity-check-2" during configuration. Fails ebuild. Expected Results: Successful ebuild of gnome-session-2.10.0-r2. Note that gconf-2.10.1 is ~x86 right now, so those with USE=x86 for gconf won't see this yet.
Sorry everybody. I guess those who do not know the bugs, are doomed to re-introduce them... I really wish portage had a way to specify dependencies with specific USE flags in the *DEPEND variables. This should be fixed in gconf-2.10.1-r1. Thanks for reporting this. As a side note, and for future reference, please remember to always include the output from "emerge --info" and attach the full output from the emerge process when reporting bugs like this one.
In case this is still any help: root@charon:bin # emerge --info Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.5-r0, 2.6.12-gentoo-r5 i686) ================================================================= System uname: 2.6.12-gentoo-r5 i686 Pentium III (Coppermine) Gentoo Base System version 1.6.13 distcc 2.18.3 i386-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] ccache version 2.3 [enabled] dev-lang/python: 2.3.5 sys-apps/sandbox: 1.2.11 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.5 sys-devel/binutils: 2.15.92.0.2-r10 sys-devel/libtool: 1.5.18-r1 virtual/os-headers: 2.6.11-r2 ACCEPT_KEYWORDS="x86" AUTOCLEAN="yes" CBUILD="i386-pc-linux-gnu" CFLAGS="-O2 -mcpu=pentium3 -fomit-frame-pointer" CHOST="i386-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3.4/env /usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -mcpu=pentium3 -fomit-frame-pointer" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://gentoo.mirrors.tds.net/gentoo http://ftp.heanet.ie/pub/gentoo/ ftp://gentoo.blueyonder.co.uk/mirrors/gentoo ftp://mir.zyrianes.net/gentoo-distfiles/ http://gentoo.blueyonder.co.uk" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.us.gentoo.org/gentoo-portage" USE="x86 X alsa apm arts avi berkdb bitmap-fonts bonobo crypt cscope cups curl eds emacs emboss encode esd fam flac foomaticdb fortran gd gdbm gif gpm gtk2 gtkhtml imagemagick imlib java jpeg junit kde ldap libg++ libwww mad mikmod motif mozilla mp3 mpeg ncurses nls ogg oggvorbis opengl oss pam pdflib perl png postgres python qt quicktime readline samba sdl slang speex spell ssl svga tcpd tiff truetype truetype-fonts type1-fonts vorbis xine xml xml2 xmms xv zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LC_ALL, LDFLAGS, LINGUAS
The gconf-2.10.1-r1 update fixed the problem. /usr/bin/gconf-sanity-check-2 was installed, and gnome-session-2.10.0-r2 compiled without the previous error.
