the title is pretty straight forward. on the amd64 architecture, when i try to update the system on my amd64 platform, xorg-x11 get's blocked, meaning the whole emerge job fails. what is particularly strange about apparently what is happening is xorg is blocking its own dependancy. when i tried to emerge xorg by itself, it gave me the same error. here is the result of pretend install: # emerge --pretend xorg-x11 These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] <=app-emulation/emul-linux-x86-xlibs-1.2-r3 (is blocking x11-base/xorg-x11-6.8.2-r1) [ebuild U ] x11-base/xorg-x11-6.8.2-r1 [6.8.0-r5] I also tried removing "emul-linux-x86" from my make.conf temporarily, and the result was the same. Reproducible: Always Steps to Reproduce: 1. on amd64, emerge --sync 2. emerge xorg-x11 3. watch in shear horror ;) Actual Results: xorg-x11 and emul-linux-x86-xlibs fail to build. Expected Results: emerge successfully completes without errors. :) Portage 2.0.51.19 (default-linux/amd64/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-gentoo-r14 x86_64) ================================================================= System uname: 2.6.9-gentoo-r14 x86_64 AMD Athlon(tm) 64 Processor 3400+ Gentoo Base System version 1.4.16 Python: dev-lang/python-2.3.4-r1 [2.3.4 (#1, Mar 2 2005, 12:03:25)] ccache version 2.3 [enabled] dev-lang/python: 2.3.4-r1 sys-devel/autoconf: 2.59-r6, 2.13 sys-devel/automake: 1.7.9-r1, 1.8.5-r3, 1.5, 1.4_p6, 1.6.3, 1.9.4 sys-devel/binutils: 2.15.92.0.2-r1 sys-devel/libtool: 1.5.10-r4 virtual/os-headers: 2.6.8.1-r2 ACCEPT_KEYWORDS="amd64" AUTOCLEAN="yes" CFLAGS="-march=athlon64 -O2 -pipe -fweb -frename-registers" CHOST="x86_64-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/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-march=athlon64 -O2 -pipe -fweb -frename-registers" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs autoconfig ccache distlocks sandbox" GENTOO_MIRRORS="http://gentoo.chem.wisc.edu/gentoo ftp://ftp.ussg.iu.edu/pub/linux/gentoo http://csociety-ftp.ecn.purdue.edu/pub/gentoo" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="amd64 X aac acpi alsa apm arts audiofile avi berkdb bitmap-fonts bzlib cdrcrypt cups curl dga dio divx4linux dvd emul-linux-x86 fam flac font-server foomaticdb fortran gif gpm imagemagick imlib java jikes jp2 jpeg kde kdexdeltas ldaplive lzw lzw-tiff mad motif mp3 mpeg multilib nas ncurses network nls nocd oav oggvorbis openal opengl oss pam pdflib perl png python qt quicktime readline real samba slang spell ssl symlink szip tcpd tiff truetype truetype-fonts type1-fonts usb userlocales videos xml2 xmms xpm xrandr xv xvid zlib" Unset: ASFLAGS, CBUILD, CTARGET, LANG, LC_ALL, LDFLAGS
xorg-x11 blocks <=emul-linux-x86-xlibs but xlibs-1.2-r7 is now stable so: # emerge emul-linux-x86-xlibs # emerge xorg-x11 i.e get the latest emul-linux-x86-xlibs first and then xorg-x11 will be happy. However as has been pointed out this is not obvious to the user. Maybe the block should be removed and replaced by some logic to detect the an old -xlibs which causes the ebuild to die and print a message structing the user to upgrade first?
aww heck, i should have thought of that! :] thank you, that fixed the problem.
