| Summary: | Wrong terminology in multiple package instances in a snigle package slot error | ||
|---|---|---|---|
| Product: | Portage Development | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
| Status: | CONFIRMED --- | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
It's possible for a conflict like this to involve two package instances of the *same* version. For example, you could have one installed instance that has different USE settings from an ebuild of the same version that got pulled in. |
!!! Multiple package instances within a single package slot have been pulled !!! into the dependency graph, resulting in a slot conflict: net-misc/curl:0 (net-misc/curl-7.26.0::gentoo, ebuild scheduled for merge) pulled in by <net-misc/curl-7.27.0 required by (dev-cpp/libcmis-0.1.0-r1::gentoo, ebuild scheduled for merge) (net-misc/curl-7.28.0-r1::gentoo, ebuild scheduled for merge) pulled in by (no parents that aren't satisfied by other packages in this slot) Portage 2.2.0_alpha142 (default/linux/x86/10.0/desktop, gcc-4.5.3, glibc-2.15-r2, 3.6.0-gentoo i686) The problematic terms: - package instances --> versions - other packages in this slot --> other versions in this slot I will also open a new bug for the case itself as it seems Portage could handle this automatically.