Summary: | portage behaves oddly with unslotted deps and ~arch packages | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Rafał Mużyło <galtgendo> |
Component: | Eclasses | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rafał Mużyło
2013-01-26 07:41:13 UTC
*** This bug has been marked as a duplicate of bug 444894 *** (In reply to comment #0) > The following keyword changes are necessary to proceed: > #required by app-arch/libarchive-3.0.4-r1, required by dev-util/cmake-2.8.9, > required by net-libs/libproxy-0.4.10-r1, required by > net-libs/neon-0.29.6-r2[libproxy], required by > dev-vcs/subversion-1.7.7[webdav-neon], required by > dev-vcs/git-1.8.0.2[subversion,perl], required by @selected, required by > @world (argument) > =dev-libs/openssl-1.0.1c ~x86 > > When I added '-t', the output suggested it's python that's pulling > openssl-0.9.8. Now, while it might matter, that python isn't using slotted > deps for openssl, the result is still odd. I think it's partially a quirk of autounmask, and you may get a different result after you update your config file to accept the openssl-1.0.1c ~x86 keyword. |