i installed the mini-packages newly prepared for kde3.4 and while the whole system works just fine, k3b won't install because it depends on kdebase -- which is blocked by all sorts of other smaller packages (kdesktop, konqueror, kate etc.) Reproducible: Always Steps to Reproduce: 1. emerge konsole 2. emerge k3b Actual Results: # emerge -av k3b These are the packages that I would merge, in order: Calculating dependencies ...done! [blocks B ] =kde-base/kcheckpass-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdebase-kioslaves-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kate-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdebase-startkde-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/konqueror-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kcminit-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdesu-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/ksplashml-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/konsole-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kwin-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kstart-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kreadconfig-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kpersonalizer-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/ksysguard-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdesktop-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/ksmserver-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kicker-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/nsplugins-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdebase-data-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kxkb-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/klipper-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kcontrol-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/kdm-3.4* (is blocking kde-base/kdebase-3.4.0) [blocks B ] =kde-base/libkonq-3.4* (is blocking kde-base/kdebase-3.4.0) [ebuild N ] app-cdr/cdrtools-2.01-r2 -crypt -unicode 0 kB [ebuild N ] dev-util/pccts-1.33.33 0 kB [ebuild N ] app-cdr/cdrdao-1.1.9 +debug -gnome 0 kB [ebuild N ] app-cdr/dvd+rw-tools-5.21.4.10.8 0 kB [ebuild N ] kde-base/kdebase-3.4.0 -arts -cups +debug -hal -ieee1394 +java -kdeenablefinal -ldap +lm_sensors +logitech-mouse +opengl +pam -samba +ssl -xinerama 0 kB [ebuild N ] sci-libs/fftw-3.0.1-r1 (-3dnow) (-altivec) +debug -mpi (-sse) 0 kB [ebuild N ] media-libs/libsamplerate-0.1.1-r1 -sndfile -static 0 kB [ebuild N ] media-video/vcdimager-0.7.20-r2 +xml2 0 kB [ebuild N ] media-sound/sox-12.17.5-r1 +debug +encode -mad +oggvorbis 0 kB [ebuild N ] media-libs/audiofile-0.2.6-r1 0 kB [ebuild N ] media-sound/normalize-0.7.6-r2 +audiofile -mad +nls +xmms 0 kB [ebuild N ] app-cdr/k3b-0.11.18 -arts +debug +dvdr +encode -flac +kde -kdeenablefinal -mad +oggvorbis -xinerama 0 kB Total size of downloads: 0 kB !!! Error: The above package list contains packages which cannot be installed !!! on the same system.
You are mixing arch and ~arch packages: k3b in ~arch is already fixed to manage split packages, but the one in arch is not (as the split packages aren't in ~arch).
Try with >=app-cdr/k3b-0.11.19, preferably with >=app-cdr/k3b-0.11.22 Reopen if those still don
Try with >=app-cdr/k3b-0.11.19, preferably with >=app-cdr/k3b-0.11.22 Reopen if those still don´t work.
*** Bug 90485 has been marked as a duplicate of this bug. ***
Well if my bug http://bugs.gentoo.org/show_bug.cgi?id=90485 is a duplicate of this, why doesn't it work then? I got app-cdr/k3b ~amd64 in my /etc/portage/package.keywords and am obviously trying to install a newer version of k3b (app-cdr/k3b-0.11.23-r2) than the ones in this bug report. So I guess I have to reopen this bug again then.
Reopened, someone please explain this better, seems it
Reopened, someone please explain this better, seems it´s still not clear.
I guess you have conflicting entries in package.keywords. Something like kde-base/kdebase kde-base/some_split_kdebase_package can't work.
I had indeed kdebase ~amd64 in my package.keywords. Sorry, my fault i guess. Anyway after I took it out it still doesn't take my installed split ebuilds. Here are the steps I did: bash-2.05b$ cat /etc/portage/package.keywords | grep kdebase kde-base/kdebase ~amd64 kde-base/kdebase-data ~amd64 kde-base/kdebase-startkde ~amd64 kde-base/kdebase-kioslaves ~amd64 kde-base/kdebase-pam ~amd64 bash-2.05b$ su - Password: logon root # nano -w /etc/portage/package.keywords I deleted kdebase from the file. logon root # emerge -p k3b These are the packages that I would merge, in order: Calculating dependencies ...done! [ebuild NS ] kde-base/kdelibs-3.3.2-r8 [ebuild N ] kde-base/kdebase-3.3.2-r1 [ebuild N ] app-cdr/k3b-0.11.23-r2 logon root # Now k3b depends on kde 3.3.2 which I do not want to have installed. Maybe you can tell me how to fix this too?
I think you just need to unmask kde-base/kdesu in package.keywords (but note that this file should contain all the other kde-base packages you installed, it's not good to install from ~amd64 without unmasking first)
kdesu-3.4.1 is now stable amd64, looks like bug can be closed
All the keywording stuff should behave now, remember to cleanup your package.keywords files as needed.
