KDE 3.2.3 wants to be 3.2.2!

Offler · n00b Joined: 12 Jun 2004 Posts: 58

I'm very new to Gentoo so be kind :wink:

. I've just recently emerged the new KDE 3.2.3 and now whenever I try to emerge world portage tries to remerge KDE 3.2.2. This is rather annoying if I use the -u flag it would install 3 odd packages and the old KDE: if I use the -U flag it emerges NOTHING?, what I'm worrying about is what happened to the other 3 packages? Those other packages are marked U, so why do they not show up when I use the -U flag? Anyone who has KDE 3.2.3 could you tell me what you do to update your system? Well I'm off to try Xorg again

, I just know Xfree is going to be re-emerged with an Xorg emerge.

Sipi · Guru Joined: 03 Apr 2003 Posts: 406 Location: Hungary

-u means that it tries to upgrade the packages. But sometimes it occurs that actually it will be a downgrade. It menas that there should be a package which eas compile with older kde, or a package is installed that needs old version, not new. Use "qpkg -q kde-3.2.2" to find if there are any packages which needs older kde.

-U means that it tries to upgrade only. It will not downgade anything. That's why you will not see the 3 older kde package. Generally, better to use this switch.

Sipi

Voltago · Posted: Wed Jun 16, 2004 1:02 pm Post subject:

mrv · Posted: Wed Jun 16, 2004 2:23 pm Post subject:

Hi,

Actually this problem started bugging me too after I upgraded from KDE 3.2.2 to 3.2.3 (yes, I'm using ~x86 in /etc/portage/package.keywords with KDE).

Yesterday (and also today) I synced my portage tree. When I made "emerge -Dupv world" I noticed that for some reason portage wants to downgrade kdelibs into 3.2.2-r1 and arts into 1.2.2:

dyqik · Posted: Wed Jun 16, 2004 2:29 pm Post subject:

KDE-3.2.3 is ~x86? If so, you can prevent emerge -u world from downgrading it by creating /etc/portage/package.keywords and adding "kde-base/kde ~x86" to it. Do this for any ~x86 packages you want to install.

DO NOT USE emerge -U world. There are several threads about why this is unsafe. Use the package.keywords method instead, or a portage overlay, if the ebuild are ~x86 masked

Offler · n00b Joined: 12 Jun 2004 Posts: 58

OK, thank you all for your replies!.

Sipi: I wasn't very clear in describing the prob so I think I confused you - what I meant was those 3 packages were NOT kde packages but things like openssl and sys utils like grep (I dont remember exactly what they were) and included in those updates when I used the -u flag was kde 3.2.2. So I tried using the -U flag because the KDE pack were marked UD and the other packages were marked U: but it didn't work kde 3.2.2 was not pulled in but neither were the other updates that were before!.

Voltago: Yep I found that code on the Xorg thread and I took your kde stuff aswell so now kde does not want to return to 3.2.2; as for my Xfree prob, it seems to have worked the second time, I unmerged Xfree and then attempted to merge xorg and Xfree was not listed as a depen!!. I'm now happily using Xorg and Xfree does not need to be masked!. So thanks for the kde ~x86 code.

dyqik: I remember reading somewhere else that I should not use -U, so I'll stay away from it then.

This is just a general Q: now that I have kde and xorg as ~x86 they will both update themselfes when i run emerge -u world according to what is available in ~x86 right? So basically I should remove them both from the package.keywords file once they are in portage right? Does anyone know when they are likely to be marked x86? - they both seem very stable to me. Hopefully over the next few days I'll get my updates back working as normal again

.

mrv · Posted: Wed Jun 16, 2004 4:41 pm Post subject:

Correction to my own earlier post; I was using kdesdk-3.2.2 instead of kdesdk-3.2.3. That's why it wanted to downgrade kdelibs and arts...

-mrv-