Summary: | Portage-2.1.5_rc6 does not correctly update slotted ebuilds when emerge -u world | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Alexander Wright <bugzilla> |
Component: | [OLD] Core system | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | normal | CC: | jmbsvicetto |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
kde packages in world
packages.keywords packages.unmask |
Description
Alexander Wright
2008-04-23 18:51:16 UTC
Is kdelibs in your world file? (In reply to comment #1) > Is kdelibs in your world file? > Yes, as follows: $grep kdelibs /var/lib/portage/world kde-base/kdelibs kde-base/kdelibs:3.5 It was not just kdelibs, that was having the problem. I'll look over the emerge log to see if the other packages were later on this evening. Please post the output of "grep kde-* /var/lib/portage/world" and attach your package.unmask and package.keywords file. If you look in http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.8-r3.ebuild?rev=1.8&view=markup you can see that kdelibs-3.5.9 is still keyworded ~amd64. If you only unmasked and keyworded kde-4.0.*, as you should, there's no kdelibs update package as 3.5.9 is masked by the ~amd64 keyword. Created attachment 150856 [details]
kde packages in world
Attached my KDE packages in world
(In reply to comment #3) > If you look in > http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.8-r3.ebuild?rev=1.8&view=markup > you can see that kdelibs-3.5.9 is still keyworded ~amd64. If you only unmasked > and keyworded kde-4.0.*, as you should, there's no kdelibs update package as > 3.5.9 is masked by the ~amd64 keyword. In that case, a separate emerge kdelibs:3.5 wouldn't have worked would it? Created attachment 150858 [details]
packages.keywords
Concatenated from several files, as I use autounmask and directories for packages.keywords and packages.unmask
Created attachment 150860 [details]
packages.unmask
Created as for packages.keywords with the following script, if anyones interested in doing similar:
cd /etc/portage/packages.unmask
for x in `ls *`; do grep -v "^#" $x |grep -v "^$" >> ~/packages.unmask; done;
(In reply to comment #1) > Is kdelibs in your world file? > Other packages that did not auto upgrade were: kde-base/ark:3.5 kde-base/kcalc:3.5 kde-base/kcheckpass:3.5 kde-base/kdebase-startkde:3.5 kde-base/kdemultimedia-kioslaves:3.5 kde-base/kdepasswd:3.5 kde-base/kdesktop:3.5 kde-base/kdm:3.5 kde-base/kgpg:3.5 kde-base/kmix:3.5 kde-base/kompare:3.5 kde-base/konsole:3.5 kde-base/kpersonalizer:3.5 kde-base/kreadconfig:3.5 kde-base/ksmserver:3.5 kde-base/ksplashml:3.5 kde-base/ktimer:3.5 kde-base/kwin:3.5 kde-base/libkcddb:3.5 (In reply to comment #5) > (In reply to comment #3) > > > If you look in > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.8-r3.ebuild?rev=1.8&view=markup > > you can see that kdelibs-3.5.9 is still keyworded ~amd64. If you only unmasked > > and keyworded kde-4.0.*, as you should, there's no kdelibs update package as > > 3.5.9 is masked by the ~amd64 keyword. > > In that case, a separate emerge kdelibs:3.5 wouldn't have worked would it? > No, it wouldn't.(In reply to comment #5) > (In reply to comment #3) > > > If you look in > > http://sources.gentoo.org/viewcvs.py/gentoo-x86/kde-base/kdelibs/kdelibs-3.5.8-r3.ebuild?rev=1.8&view=markup > > you can see that kdelibs-3.5.9 is still keyworded ~amd64. If you only unmasked > > and keyworded kde-4.0.*, as you should, there's no kdelibs update package as > > 3.5.9 is masked by the ~amd64 keyword. > > In that case, a separate emerge kdelibs:3.5 wouldn't have worked would it? > Did you add the "kde-base/kdelibs ~amd64" line to the keywords file before trying to update? If not, no, running emerge kdelibs:3.5 wouldn't work. You're doing the worst thing you can do which is to mix *heavily* stable and unstable packages - don't get surprised if things start to break. You also should clean your files as you're using everything from "kde-base/PN:kde-4 **", "=kde-base/P ~amd64" to "kde-base/PN ~amd64. I would suggest you use /etc/portage/package.{keywords,unmask}/kde[4] files as it would make things clearer. Also, you might want to clean your world file as it seems quite a few of those kde packages are deps to another packages. As it is, I think this is an invalid bug. Clean your system and try to update again. If portage "forgets" to update any package, open the bug again. (In reply to comment #9) > Did you add the "kde-base/kdelibs ~amd64" line to the keywords file before > trying to update? If not, no, running emerge kdelibs:3.5 wouldn't work. > You're doing the worst thing you can do which is to mix *heavily* stable and > unstable packages - don't get surprised if things start to break. I have not changed any of the keywords or mask files before or after doing any of these actions above. As I've stated, emerge -uavDN did not update any of the files I've quoted above, but explicitly emerging them as emerge kdelibs:3.5 did upgrade them, without changing any mask or keywords file. I know I've a mix of stable and unstable packages, and I'd expect them to break, and indeed am quite happy for them to do so. How else am I to report bugs? This (possible) bug is to do with the installation of these packages, so I don't see how them being stable or unstable would make a difference. > You also should clean your files as you're using everything from > "kde-base/PN:kde-4 **", "=kde-base/P ~amd64" to "kde-base/PN ~amd64. I would > suggest you use /etc/portage/package.{keywords,unmask}/kde[4] files as it > would make things clearer. I do actually have them split up as several files, but I agree that they should be cleaned up. Several years running does tend to build up unnecessary things in these files. > Also, you might want to clean your world file as it seems > quite a few of those kde packages are deps to another packages. Will do. > As it is, I think this is an invalid bug. Clean your system and try to update > again. If portage "forgets" to update any package, open the bug again. Hmm, I think that this is still a bug, but I see your point. Its an edge case in any case. I'll clean up and see how I get on. |