Attempts to emerge nvidia-glx fail, citing issues with the opengl-update dependency candidates being masked. Reproducible: Always Steps to Reproduce: 1. emerge -v(p) nvidia-glx 2. 3. Actual Results: Emerge did not complete successfully. Expected Results: Emerged new nvidia-glx without issues. Output of emerge attempt: arubis@daltoris: timestamp[ 17:19:27 on Sun Jul 18 ] ~ $ sudo emerge -vup nvidia-glx These are the packages that I would merge, in order: Calculating dependencies \ !!! all ebuilds that could satisfy ">=x11-base/opengl-update-1.8.1" have been masked. !!! possible candidates are: - x11-base/opengl-update-1.8.1 (masked by: ~keyword) !!! (dependency required by "media-video/nvidia-glx-1.0.6106-r3" [ebuild]) !!! Error calculating dependencies. Please correct. arubis@daltoris: timestamp[ 17:19:41 on Sun Jul 18 ] ~ Output of emerge info: Portage 2.0.50-r9 (default-x86-1.4, gcc-3.3.3, glibc-2.3.3.20040420-r0, 2.6.7-gentoo-r3) ================================================================= System uname: 2.6.7-gentoo-r3 i686 AMD Athlon(tm) MP 2000+ Gentoo Base System version 1.4.16 distcc 2.13 i686-pc-linux-gnu (protocols 1 and 2) (default port 3632) [disabled] Autoconf: sys-devel/autoconf-2.59-r3 Automake: sys-devel/automake-1.8.3 ACCEPT_KEYWORDS="x86" AUTOCLEAN="no" CFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" COMPILER="gcc3" CONFIG_PROTECT="/etc /usr/X11R6/lib/X11/xkb /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/bind /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O3 -march=athlon-mp -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoaddcvs ccache sandbox strict userpriv" GENTOO_MIRRORS="http://gentoo.oregonstate.edu http://distro.ibiblio.org/pub/Linux/distributions/gentoo" MAKEOPTS="-j3" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="3dnow X X509 Xaw3d aalib acl acpi alsa apache2 apm avi berkdb bonobo cdr crypt cups curl dga dillo directfb dvd emacs encode esd ethereal evms2 evo faad fam fbcon flac flash foomaticdb gb gd gdbm ggi gif gnome gnomedb gnutls gpm gtk gtk2 gtkhtml guile imap imlib innodb ipv6 jack java jikes jpeg ladcca lcd ldap leim libg++ libgda libwww mad maildir mbox memlimit mikmod mmx motif mozilla mpeg mule mysql nas ncurses nls nvidia odbc offensive oggvorbis opengl oss pam pda pdflib perl plotutils png postgres ppds pwdb python qt quicktime readline ruby samba sasl sdl skey slang slp spell sse ssl tcltk tcpd tetex theora tiff transcode truetype usb v4l videos wxwindows x86 xface xine xinerama xml xml2 xmms xosd xv xvid zlib"
Dont personally unmask nvidia-kernel or nvidia-glx and then complain tell us that you have dep problems because you are using unstable drivers. Check /etc/portage/packages.mask and add opengl-update as appropriate (or remove nvidia-glx).
Wow, that's embarrassing...I completely forgot I did that. My apologies.
I think this is a valid bug. The ~x86 nvidia-glx package is needed by the 2.6.x kernel. The current stable package doesn't work at all. I think the reporter has a valid point and shouldn't be told to just go away and to expect this behavior from portage. I know the nvidia packages suck, but they do need to work, even if masked.
I have exactly the same thing without manually unmasking the nvidia-glx or any other package. I've been waiting four days now to see if this would resolve itself, but apparently it hasn't and if this is the dev attitude, it might be a while I'm afraid
This is straight from CVS which hasnt been changed recently. andrew@asteroid opengl-update $ grep KEYWORDS ./* ./opengl-update-1.5.ebuild:KEYWORDS="x86 ppc sparc alpha hppa amd64 ia64 mips" ./opengl-update-1.7.1.ebuild:KEYWORDS="x86 ppc sparc mips alpha arm hppa amd64 ia64 ppc64" ./opengl-update-1.7.2.ebuild:KEYWORDS="x86 ppc sparc mips alpha arm hppa amd64 ia64 ppc64" ./opengl-update-1.8.1.ebuild:KEYWORDS="~x86 amd64" andrew@asteroid nvidia-glx $ grep KEYWORDS ./* ./nvidia-glx-1.0.4363-r1.ebuild:KEYWORDS="-* x86" ./nvidia-glx-1.0.4496-r2.ebuild:KEYWORDS="-* x86" ./nvidia-glx-1.0.4499-r1.ebuild:KEYWORDS="-* amd64" ./nvidia-glx-1.0.5328-r2.ebuild:KEYWORDS="-* ~x86" ./nvidia-glx-1.0.5332-r2.ebuild:KEYWORDS="-* amd64" ./nvidia-glx-1.0.5336-r2.ebuild:KEYWORDS="-* ~x86" ./nvidia-glx-1.0.6106-r3.ebuild:KEYWORDS="-* ~x86 amd64" From this we can see that in order for nvidia-glx unmasked to depend on opengl-update masked, you must be using X86 architecture, and you must be using one of the 4*** driver versions. Unfortunately only 6106 explicity states that you must have opengl-update-1.8.1 installed. Both of these are masked on x86 and both are unmasked on amd64, I shall let you conclude what you may. Try resyncing your tree or checking other deps.
