i cant 'emerge -up world' anymore Reproducible: Always Steps to Reproduce: 1.emerge -up world 2. 3. Actual Results: eagle xfree # emerge -up world These are the packages that I would merge, in order: Calculating world dependencies / !!! all ebuilds that could satisfy "virtual/x11" have been masked. !!! (dependency required by "media-libs/libungif-4.1.0.1b" [ebuild]) !!! Problem with ebuild media-video/mplayer-0.90_rc4 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. Expected Results: as usual :) it's not http://bugs.gentoo.org/show_bug.cgi?id=5121 i tried 'emerge regen' and 'regenworld', the problem is still there i don't have the problem with x86 boxes. though i share (through nfs) the same portage tree.
Same problem here. p166-126 root # emerge -Up world >>> --upgradeonly implies --update... adding --update to options. These are the packages that I would merge, in order: Calculating world dependencies / !!! all ebuilds that could satisfy "virtual/x11" have been masked. !!! (dependency required by "app-office/openoffice-1.0.3" [ebuild]) !!! Problem with ebuild app-office/openoffice-1.0.3 !!! Possibly a DEPEND/*DEPEND problem. !!! Depgraph creation failed. p166-126 root # emerge info Portage 2.0.47-r10 (default-x86-1.4, gcc-3.2.2, glibc-2.3.2-r1) ================================================================= System uname: 2.5.67 i686 AMD Athlon(tm) XP 1800+ GENTOO_MIRRORS="http://trumpetti.atm.tut.fi/gentoo/ http://gentoo.linux.no/" CONFIG_PROTECT="/etc /var/qmail/control /usr/kde/2/share/config /usr/kde/3/share /config /usr/X11R6/lib/X11/xkb /usr/kde/3.1/share/config /usr/share/config" CONFIG_PROTECT_MASK="/etc/gconf /etc/env.d" PORTDIR="/usr/portage" DISTDIR="/usr/portage/distfiles" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR_OVERLAY="/usr/local/portage" USE="x86 3dnow apm avi crypt cups encode gif jpeg libg++ mikmod mmx mpeg ncurses nls pdflib png quicktime spell truetype xml2 xmms xv zlib gtkhtml gdbm berkdb s lang readline arts svga java guile X sdl gpm tcpd pam libwww ssl python esd imli b oggvorbis gtk qt kde opengl aalib acpi alsa bonobo cdr cjk dga directfb doc ev o fbcon flash gb gd -gnome gphoto2 imap ipv6 jikes lcms ldap leim libgda mbox -m otif mozilla mule mysql odbc -oss perl plotutils postgres samba sasl slp snmp so cks5 sse tcltk tetex tiff usb xface nptl" COMPILER="gcc3" CHOST="i686-pc-linux-gnu" CFLAGS="-mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer -mmmx -msse -m3dnow -mfpm ath=sse" CXXFLAGS="-mcpu=athlon-xp -O3 -pipe -fomit-frame-pointer -mmmx -msse -m3dnow -mf pmath=sse" ACCEPT_KEYWORDS="x86" MAKEOPTS="-j2" AUTOCLEAN="yes" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" FEATURES="ccache sandbox" Perhaps this is caused by the xfree-4.3.0-r1 ebuild being ~x86? That is, Portage looks at the virtuals file and finds that virtual/x11 is provided by x11-base/xfree-4.3.0-r1 but can't use it since it's not within my ACCEPT_KEYWORDS. Thus, it thinks that the user doesn't have virtual/x11. If I run "ACCEPT_KEYWORDS="~x86" emerge -Up world" Portage does what it should do. I could work around this by creating and injecting an ebuild named x11 in $PORTDIR_OVERLAY/virtual, but that's eminently unclean...
*** This bug has been marked as a duplicate of 9050 ***
