librss needs bump "-r1" , kde-env blocks again... i can't update -D : >=kde-base/kdelibs-3.5.4-r2 (is blocking kde-base/kde-env-3-r4) and it's not a dupe of bug #154999 even if the effect is very similar emerging with deep option looks in /var/db/pkg/kde-base/librss-3.5.0/librss-3.5.0.ebuild and finds that it needs "MAXKDEVER=3.5.4" while this has been fixed in portage tree emerge is still looking for the ebuild from installation time and wants to downgrade kdelibs and arts [nomerge ] kde-base/kdesktop-3.5.5 [nomerge ] kde-base/kdenetwork-meta-3.5.5 [nomerge ] kde-base/librss-3.5.0 [binary UD] kde-base/kdelibs-3.5.2-r6 [3.5.5-r5] [binary UD] kde-base/arts-3.5.2-r1 [3.5.5] [ebuild N ] kde-base/kde-env-3-r4 which brings again the ugly kde-env... the ebuild should have been bumped -r1 when this change have been made such that the update is forced Unless there is a cleaner thing to do or the breakage is on my side, but it don't seems to. thanks in advance Aurl
librss needs bump "-r1" , kde-env blocks again... i can't update -D : >=kde-base/kdelibs-3.5.4-r2 (is blocking kde-base/kde-env-3-r4) and it's not a dupe of bug #154999 even if the effect is very similar emerging with deep option looks in /var/db/pkg/kde-base/librss-3.5.0/librss-3.5.0.ebuild and finds that it needs "MAXKDEVER=3.5.4" while this has been fixed in portage tree emerge is still looking for the ebuild from installation time and wants to downgrade kdelibs and arts [nomerge ] kde-base/kdesktop-3.5.5 [nomerge ] kde-base/kdenetwork-meta-3.5.5 [nomerge ] kde-base/librss-3.5.0 [binary UD] kde-base/kdelibs-3.5.2-r6 [3.5.5-r5] [binary UD] kde-base/arts-3.5.2-r1 [3.5.5] [ebuild N ] kde-base/kde-env-3-r4 which brings again the ugly kde-env... the ebuild should have been bumped -r1 when this change have been made such that the update is forced Unless there is a cleaner thing to do or the breakage is on my side, but it don't seems to. thanks in advance Aurléien
I was wrong with the /var/db/pkg/ stuff. It actually comes from binary packages from portage/packages/All/ who are built during previous merge with FEATURES="buildpkg" in make.conf. They contains the old ebuild and the "MAXKDEVER=3.5.4" line. The actual problem is slightly different but the casue is the same and the fix too ... adding a -rX to the ebuild would cause a bump and a painless update But tens of ebuilds seems to be concerned, that's a lot of upgrades for a so litle change ... Aur
I was wrong with the /var/db/pkg/ stuff. It actually comes from binary packages from portage/packages/All/ who are built during previous merge with FEATURES="buildpkg" in make.conf. They contains the old ebuild and the "MAXKDEVER=3.5.4" line. The actual problem is slightly different but the casue is the same and the fix too ... adding a -rX to the ebuild would cause a bump and a painless update But tens of ebuilds seems to be concerned, that's a lot of upgrades for a so litle change ... Aurélien
*** This bug has been marked as a duplicate of 154999 ***
