On Sun, 2004-01-04 at 01:09, Glenn Johnson wrote:
> I am maintaining an "~x86" system and have alsa-lib-1.0.0_rc2 installed.
> When doing an 'emerge -Dup world', portage wants to downgrade
> alsa-lib to 0.9.8. What is strange is that it seems that alsa-lib
> itself is causing this. I did an 'emerge -C alsa-lib' to remove
> alsa-lib-1.0.0_rc2. Then upon doing 'emerge -Dup world' I get the
> following:
>
> ===begin output===
> These are the packages that I would merge, in order:
>
> Calculating world dependencies ...done!
> [ebuild N ] media-libs/alsa-lib-1.0.0_rc2
> ===end output===
>
> So then I do 'emerge alsa-lib', which installs alsa-lib-1.0.0_rc2
>
> Then, after the installation of alsa-lib-1.0.0_rc2, I do the 'emerge
> -Dup world' again and get the following:
>
> ===begin output===
> These are the packages that I would merge, in order:
>
> Calculating world dependencies ...done!
> [ebuild UD] media-libs/alsa-lib-0.9.8 [1.0.0_rc2]
> ===end output===
>
Are you using the -U (capital U) switch? which says, ONLY do UPGRADES
(no downgrades). Hence:
emerge -pvUun world
emerge -Uun
It never wants to down grade a package I have emerged with
ACCEPT_KEYWORDS='~x86'.
--
[EMAIL PROTECTED] mailing list
