| Summary: | sys-apps/portage fails to recognize a conflict | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Sebastian Pipping <sping> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
Shell session demo
emerge --info |
||
This looks like a duplicate of bug 367555. See bug 371055, comment #6. Created attachment 276567 [details]
emerge --info
I mean bug 367555, comment #6. It's the "Why doesn't emerge account for reverse dependencies sometimes?" question in the faq: http://www.gentoo.org/proj/en/portage/doc/faq.xml Sigh. My vote on sane (but slow) defaults. |
Created attachment 276563 [details] Shell session demo I currently have these two packages installed: net-libs/xulrunner-1.9.2.17 dev-java/swt-3.5.2[xulrunner] The latter of these depends on =net-libs/xulrunner-1.9* which is why portage cannot update xulrunner to 2.0.1-r1 on update world. So far so good. Now the problem occurs when I run "emerge net-libs/xulrunner". emerge now installs xulrunner 2.0.1-r1 (same slot "1.9") which turns swt-3.5.2 into an installed state of one un filled dependency. See my shell session for a more visual version of this.