> > Because the driver is not unmasked. Just ignore emerge. > > It really wants to downgrade since the unmasked version > > is lower. I'm seeing it too every time I do a emerge -uD > > world -p so I ignore it. You can fix it by editing the > > ebuild and taking the ~x86 out of the KEYWORDS entry. > > > > Brett, > Your response has all the words I expected to see, but somehow it's > not > registering in my feeble brain. I assume that all of the Alsa-1.0.0rc2 > set of packages are masked. I have all of those packages installed. > Why does emerge only mention alsa-driver-0.9.8? Why doesn't it do the > same thing for alsa-tools, alsa-utils, etc?
Alsa-driver-1.0.0_rc2 is ~x86, 0.9.8 is ordinary x86. They are slotted depending on your kernel-version. It now seems as the kernel-version has changed since you installed 1.0.0_rc2 and so portage wants to install alsa-driver for your current kernel-version (in a new SLOT) and since you're not running~x86 it wants to install 0.9.8 instead. If you want 1.0.0_rc2 for your current kernel version you should emerge alsa-driver again with~x86, i.e: KEYWORDS="~x86" emerge alsa-driver > Also, what do you mean 'so I ignore it'. I've been ignoring it for > a few > days thinking that some emerge sync operation would fix it, but it > hasn't. My method of ignoring it is to explicitly type in package > names (i.e. emerge -U package1 package2 package3) instead of removing > the 'p' from emerge -Up world. What is it you do to get around this? > Edit all the rc2 ebuilds? You might want to try unmasking alsa-driver in /etc/portage/package.unmask also by adding this line into the file: =media-sound/alsa-driver-1.0.0_rc2 Patrick B�rjesson -- Public key ID: 4C5AB0BF Public key available at wwwkeys.pgp.net
pgp00000.pgp
Description: PGP signature
