This is the second time this has happened to me: I have a package that supposedly blocks an emerge, even after the blocking package has been removed. The question is "what to do now?" For example, to illustrate that this can occur: # emerge --search qca Searching... [ Results for search key : qca ] [ Applications found : 9 ] * app-crypt/qca Latest version available: 2.0.0-r2 Latest version installed: 2.0.0-r2 Size of files: 4,986 kB Homepage: http://delta.affinix.com/qca/ Description: Qt Cryptographic Architecture (QCA) License: LGPL-2 ...rest omitted # emerge -up --deep world These are the packages that would be merged, in order: Calculating world dependencies... done! [ebuild NS ] app-crypt/qca-1.0-r2 [ebuild N ] app-crypt/qca-tls-1.0-r3 [ebuild N ] kde-base/kdenetwork-3.5.9 USE="arts rdesktop ssl -debug -jingle -kdeenablefinal -kdehiddenvisibility -sametime -slp -wifi -xinerama" [blocks B ] <app-crypt/qca-1.0-r3 (is blocking app-crypt/qca-2.0.0-r2) (Note, I have even unmerged for the moment all packages that depended on qca.) # equery depends qca [ Searching for packages depending on qca... ] # # emerge --unmerge =app-crypt/qca-1.0-r3 --- Couldn't find '=app-crypt/qca-1.0-r3' to unmerge. >>> No packages selected for removal by unmerge emerge --unmerge =qca-1.0-r3 --- Couldn't find '=qca-1.0-r3' to unmerge. >>> No packages selected for removal by unmerge Reproducible: Always
I don't know why you have qca-2 but certainly qca-1 is pulled by the kdenetwork, and you use emerge -t you might see it more clearly. equery depends does not show it because it by default shows only reverse deps that are installed, which kdenetwork is not yet. Is it clearer now? And if you wonder about the block then you are looking at bug 238000.
thank you also for the specific comments. my suggestion was more for documentation that explains what to do in cases in which a blocking package no longer exists on the system: http://gentoo-wiki.com/FAQ_Blocked_Package Regards, /iaw
Of course. The output says that you are installing 1.0-r2 in a new slot. And apparently you cannot have SLOT=0 and SLOT=2 on the same machine so portage is telling you that the newly soon-to-be-emerged qca-1.0-r2 cannot coexist with the existing 2.0.0-r2 - I'm not sure why it is slotted if the two versions cannot coexist. But that is not what this bug is about, I guess. I think maybe you are suffering from qca-1.0-r3 not being stable on your arch. See bug #238000
(In reply to comment #3) > And apparently > you cannot have SLOT=0 and SLOT=2 on the same machine so portage is telling you Specifically, < 1.0-r3 and SLOT=2
