I don't know why these are masked, becuase whenever I do a emerge -UDp world, portage complains about the masked packages being installed. A quick look over the bugs filed w/ nvidia-5336 builds appear to be completely irrelavent to this version being masked! The three bugs filed either have work-arounds or appear to be to a specific h/w version -- ie no loss of data, etc.. just lock-ups due to a specific h/w layout for some reason. These probably should be unmasked, however, I'm not going to complain that the latest stable be kept to an earlier release unless portage complains again on emerge -UDp world. Reproducible: Always Steps to Reproduce: 1. 2. 3. I'm probably not the only one out there running nvidia-5336 builds either. ;-)
5336 has been in unstable portage for a month as for your issue with masking, read the portage docs on how to mix unstable with stable
5xxx is still buggy wrt. text consoles. unable to resolve until upstream releases working drivers.
i've had zaro problems. again, the bug your talking about seem relevant to a specific set of h/w setup -- does it not? even then, simply unmasking doesn't necessarily mean that the 5336 version will be made the "latest stable" automagically correct? Making something the "latest stable" version in order for an "emerge -UDp world" requires an additional setting w/i the ebuild doesn't it?
*** Bug 43420 has been marked as a duplicate of this bug. ***
