Bugzilla Bug 159317

Hello,

like in the URL on Gentoo forums I got a problem with kde-env.
I don't have kde-env installed, and want to update kde-meta 3.5.3 to
kde-meta-3.5.5, but
kde-base/kde-env blocks the update of kde-base/kdelibs.

Code:
# emerge -pvuDt world
[blocks B     ] >=kde-base/kdelibs-3.5.4-r2 (is blocking kde-base/kde-env-3-r4)
...
[ebuild     U ]  kde-base/kdebase-meta-3.5.5 [3.5.2] 0 kB
...
[nomerge      ]   kde-base/kcminit-3.5.0  USE="arts kdeenablefinal -debug
-kdehiddenvisibility -kdexdeltas -xinerama"
[ebuild     UD]    kde-base/kdelibs-3.5.2-r6 [3.5.5-r5] USE="alsa arts cups
jpeg2k ssl tiff -acl -debug -doc -kdeenablefinal -kdehiddenvisibility -kerberos
-legacyssl -openexr -spell -xinerama -zeroconf (-fam%) (-lua%) (-utempter%)"
LINGUAS="(-he%)" 0 kB
[ebuild  N    ]     kde-base/kde-env-3-r4  0 kB




Found out, that the ebuild of kdebase-meta depends on kcminit-3.5.0 up to
3.5.5.
code:
RDEPEND="
$(deprange 3.5.0 $MAXKDEVER kde-base/kcminit)


For my old installation (kde-meta-3.5.3) I have kcminit-3.5.0 installed, which
depends on kde-libs-3.5.0 up to 3.5.2.
kdelibs gets downgraded to version 3.5.2, which in turn pulls kde-env, which
prevents the upgrade of kdelibs.

A fix to kdebase-meta-3.5.5.ebuild helped:
code:
# diff -u kdebase-meta-3.5.5.ebuild.bak kdebase-meta-3.5.5.ebuild
--- kdebase-meta-3.5.5.ebuild.bak       2006-12-11 16:06:02.000000000 +0100
+++ kdebase-meta-3.5.5.ebuild   2006-12-29 00:32:21.000000000 +0100
@@ -18,7 +18,7 @@
 $(deprange $PV $MAXKDEVER kde-base/kappfinder)
 $(deprange $PV $MAXKDEVER kde-base/kate)
 $(deprange 3.5.0 $MAXKDEVER kde-base/kcheckpass)
-$(deprange 3.5.0 $MAXKDEVER kde-base/kcminit)
+$(deprange 3.5.3 $MAXKDEVER kde-base/kcminit)
 $(deprange $PV $MAXKDEVER kde-base/kcontrol)
 $(deprange 3.5.1 $MAXKDEVER kde-base/kdcop)
 $(deprange 3.5.0 $MAXKDEVER kde-base/kdebugdialog)

The fix pulls in kcminit-3.5.3, which allows kdelibs-3.5.5.


Though I don't think, that you'll change kdebase-meta-3.5.5.ebuild,
it may help for the next release of kdebase-meta.


regards

*** Bug 159324 has been marked as a duplicate of this bug. ***

Sorry, late...