Summary: | sys-apps/portage-2.1.10.44 tries to pull in dev-lang/perl-5.10.1 for virtual/perl-Time-Local-1.19.01 | ||
---|---|---|---|
Product: | Portage Development | Reporter: | William Throwe <wtt6> |
Component: | Core - Dependencies | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED OBSOLETE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
William Throwe
2012-02-18 21:20:28 UTC
(In reply to comment #0) > virtual/perl-Time-Local-1.19.01 can be satisfied by either dev-lang/perl-5.10.1 > or perl-core/Time-Local-1.19.01. Portage can't figure out that it should > install the latter because the former is masked. > > wthrowe@mim ~ $ emerge -pq perl-Time-Local > [ebuild UD] dev-lang/perl-5.10.1 [5.12.4-r1] > [ebuild N ] virtual/perl-Time-Local-1.19.01 virtual/perl-Time-Local-1.19.01 depends on RDEPEND="|| ( ~dev-lang/perl-5.10.1 ~perl-core/Time-Local-${PV} )" KEYWORDS were: | virtual/perl-Time-Local-1.19.01 arm | perl-core/Time-Local-1.19.01 arm | perl-core/Time-Local-1.200.0 arm but was only | virtual/perl-Time-Local-1.200.0 ~arm So I guess the problem was that virtual/perl-Time-Local-1.19.01 doesn't depend on the best visible version of any of the dependencies?! Anyway: I've added the missing stable keywords to virtual/perl-Time-Local-1.200.0 and the problem should be gone. |