| 1 |
Am 15.08.2011 23:33, schrieb Paul Hartman: |
| 2 |
|
| 3 |
> Use --tree to get a better idea what package wants the newer ExtUtils-ParseXS |
| 4 |
|
| 5 |
I narrowed it down to |
| 6 |
|
| 7 |
emerge perl-core/Module-Build -vp |
| 8 |
|
| 9 |
These are the packages that would be merged, in order: |
| 10 |
|
| 11 |
Calculating dependencies ... done! |
| 12 |
[ebuild U ] perl-core/ExtUtils-ParseXS-3.20.0 [2.22.06] 0 kB |
| 13 |
[ebuild R ] perl-core/Module-Build-0.380.0 0 kB |
| 14 |
|
| 15 |
Total: 2 packages (1 upgrade, 1 reinstall), Size of downloads: 0 kB |
| 16 |
|
| 17 |
The following keyword changes are necessary to proceed: |
| 18 |
#required by virtual/perl-ExtUtils-ParseXS-3.20.0, required by |
| 19 |
perl-core/Module-Build-0.380.0, required by perl-core/Module-Build |
| 20 |
(argument) |
| 21 |
>=perl-core/ExtUtils-ParseXS-3.20.0 ~amd64 |
| 22 |
|
| 23 |
and Module-Build-0.380.0 has >=virtual/perl-ExtUtils-ParseXS-2.22.05 in |
| 24 |
DEPEND. |
| 25 |
|
| 26 |
So yes autounmask was actually right, because I masked |
| 27 |
perl-core/ExtUtils-ParseXS-3.20.0 but not the virtual-3.20.0. |
| 28 |
After doing that everything is fine here. |
| 29 |
|
| 30 |
But why was autounmask=y complaining but not autounmask=n? |
| 31 |
The dependency of the virtual was missing both times so shouldn't emerge |
| 32 |
spit some error out both times? |
| 33 |
|
| 34 |
Greetings |
| 35 |
|
| 36 |
Sebastian |
Archives