emerge -up world & downgrading despite injecting

swimmer

Hi all,

I recently started my daily 'emerge sync && emerge -up world' and got the following list:

Calculating world dependencies ...done!
[ebuild U ] dev-libs/openssl-0.9.6i-r1 [0.9.6i]
[ebuild UD] media-sound/alsa-driver-0.9.0_rc6 [0.9.1]
[ebuild U ] kde-base/arts-1.1.1 [1.1.0]
[ebuild UD] media-libs/alsa-lib-0.9.0_rc6 [0.9.1]
[ebuild U ] kde-base/kdelibs-3.1.1 [3.1-r2]
[ebuild U ] media-sound/mpg123-0.59r-r2 [0.59r-r1]
[ebuild U ] kde-base/kdemultimedia-3.1.1 [3.1]
[ebuild U ] kde-base/kdegames-3.1.1 [3.1]
[ebuild U ] kde-base/kdeedu-3.1.1 [3.1-r1]
[ebuild U ] dev-java/blackdown-jdk-1.3.1-r7 [1.4.1]
[ebuild U ] kde-base/kdebase-3.1.1 [3.1-r1]
[ebuild U ] kde-base/kdeutils-3.1.1 [3.1]
[ebuild U ] kde-base/kdenetwork-3.1.1 [3.1]
[ebuild U ] kde-base/kdepim-3.1.1 [3.1]
[ebuild UD] media-gfx/gphoto2-2.1.0 [2.1.1]
[ebuild U ] kde-base/kdegraphics-3.1.1 [3.1]
[ebuild U ] x11-terms/rxvt-2.7.8-r6 [2.7.8-r5]
[ebuild U ] kde-base/kdetoys-3.1.1 [3.1]
[ebuild U ] x11-libs/gtk+-1.2.10-r10 [2.2.1]
[ebuild UD] dev-libs/DirectFB-0.9.12 [0.9.17]
[ebuild U ] media-sound/xmms-1.2.7-r19 [1.2.7-r15]
[ebuild U ] kde-base/kdeaddons-3.1.1 [3.1]
[ebuild U ] kde-base/kdeartwork-3.1.1 [3.1]
[ebuild U ] kde-base/kdeadmin-3.1.1 [3.1]
[ebuild U ] kde-base/kde-3.1.1 [3.1]

I actually do *not* understand why I got all those 'downgrades' because those packages are already injected in the /var/cache/edb/world:

>=media-sound/alsa-utils-0.9.1
>=media-video/nvidia-glx-1.0.4191-r1
>=media-video/nvidia-kernel-1.0.4191-r2
>=media-gfx/gphoto2-2.1.1
>=media-sound/alsa-driver-0.9.1
>=media-libs/alsa-oss-0.9.1
>=media-libs/alsa-lib-0.9.1
>=dev-libs/DirectFB-0.9.17
>=media-sound/alsa-tools-0.9.1

Injecting them again with 'emerge inject' is refused

!!! Not injecting media-sound/alsa-driver-0.9.1; Package already exists.
!!! Not injecting media-libs/alsa-lib-0.9.1; Package already exists.
!!! Not injecting media-gfx/gphoto2-2.1.1; Package already exists.
!!! Not injecting dev-libs/DirectFB-0.9.17; Package already exists.

Can someone explain me what's going on here ?

Thx in advance
Stefan

Y z

I experience the same thing, but then the other way around. I have
pinned the nvidia-{kernel,glx} version in the world file:

networx · Posted: Thu Mar 20, 2003 1:33 pm Post subject: Same problem

I have the same problem here:

KBAKEP · n00b Joined: 07 Dec 2002 Posts: 58 Location: Russia

Check for the package that depends on an "old" GTK+.

networx · Posted: Thu Mar 20, 2003 2:22 pm Post subject:

Ahh, found it; thanks !

XMMS was causing the problem, "emerge -u --nodeps xmms" seemed to do the trick...

swimmer · Posted: Fri Mar 21, 2003 10:21 am Post subject:

Any ideas here ?

Nobody seems to have this problem - I don't get replies neither here nor in the IRC channels

Plz give me a hint !!

Regards
Stefan

konqueror · Tux's lil' helper Joined: 16 Mar 2003 Posts: 76

as KBAKEP hinted, something might be requiring that downgraded version of the ebuilds instead of the ones that you currently have. I'm not familiar enough with the portage system enough (or with qpkg) to recommend anything specific, but you could try looking around at your world file (/var/cache/edb/world), and then emerging those packages one by one with '-p' to see which ones trigger the downgrade (of course you could also write a short shell script for that).

On the other hand, if you're sure that you want to keep with your current versions, you could try 'emerge inject <package-old-version>' before doing your emerge sync and world, and then at the end, 'emerge clean <package-old-version>' again. See if this works for you.

konqueror · Tux's lil' helper Joined: 16 Mar 2003 Posts: 76

oh yeah using --nodeps is also another alternative as networx did.