Emerge want's to downgrade packages

faz

Hi,

The only thing i have done to be able to build KDE 3.1 rc1 was unmasking KDE3.1rc1 by removing it from packages.mask. I do this every time after a emerge rsync.

Now emerge -up world suggests downgrading a lot of packages. I don't know why. These packages were not masked packages. When I do a emerge -up world i see:

These are the packages that I would merge, in order.

Calculating world dependencies ...done!
[ebuild U ] sys-libs/glibc-2.2.5-r7
[ebuild U ] sys-devel/binutils-2.13.90.0.4
[ebuild U ] sys-devel/flex-2.5.4a-r5
[ebuild U ] sys-apps/grub-0.90-r7
[ebuild U ] sys-devel/autoconf-2.53a
[ebuild U ] sys-devel/automake-1.6.1-r6
[ebuild U ] sys-apps/bash-2.05a-r3
[ebuild U ] sys-libs/readline-4.2a-r1
[ebuild U ] sys-apps/texinfo-4.2-r5
[ebuild U ] dev-lang/python-2.2.1-r5
[ebuild U ] sys-devel/gcc-3.2-r1
[ebuild U ] dev-libs/glib-1.2.10-r5
[ebuild U ] dev-libs/libusb-0.1.5
[ebuild U ] media-gfx/gphoto2-2.0-r1

When I check these packages with emerge -s <packagename>, all of these packages have a higher version installed.

Can somebody explain this and is there a way to have a emerge world that wil NOT downgrade?

thinair · Posted: Sun Nov 10, 2002 11:24 am Post subject:

Have you delete the ACCEPTING_KEYWORDS="~arch" (arch your system)
In make.conf ?

--
thinair

faz · Posted: Sun Nov 10, 2002 2:16 pm Post subject:

No, that's not what I want. I don't want to be on the bleeding edge of Gentoo, I just wanted KDE 3.1 rc1. How can I update world on stable without emerge wanting packages to downgrade?