Am 15.08.2011 23:33, schrieb Paul Hartman: > Use --tree to get a better idea what package wants the newer ExtUtils-ParseXS
I narrowed it down to emerge perl-core/Module-Build -vp These are the packages that would be merged, in order: Calculating dependencies ... done! [ebuild U ] perl-core/ExtUtils-ParseXS-3.20.0 [2.22.06] 0 kB [ebuild R ] perl-core/Module-Build-0.380.0 0 kB Total: 2 packages (1 upgrade, 1 reinstall), Size of downloads: 0 kB The following keyword changes are necessary to proceed: #required by virtual/perl-ExtUtils-ParseXS-3.20.0, required by perl-core/Module-Build-0.380.0, required by perl-core/Module-Build (argument) >=perl-core/ExtUtils-ParseXS-3.20.0 ~amd64 and Module-Build-0.380.0 has >=virtual/perl-ExtUtils-ParseXS-2.22.05 in DEPEND. So yes autounmask was actually right, because I masked perl-core/ExtUtils-ParseXS-3.20.0 but not the virtual-3.20.0. After doing that everything is fine here. But why was autounmask=y complaining but not autounmask=n? The dependency of the virtual was missing both times so shouldn't emerge spit some error out both times? Greetings Sebastian
signature.asc
Description: OpenPGP digital signature
