Summary: | phantom packages | ||
---|---|---|---|
Product: | Portage Development | Reporter: | ivo welch <ivo.welch> |
Component: | Documentation | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED INVALID | ||
Severity: | enhancement | CC: | darkside |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
ivo welch
2008-09-25 13:28:05 UTC
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 |