1 |
Heads up to any ~arch users who might run into this. |
2 |
|
3 |
I've just spent too many annoying hours dealing with perl-5.24 and it's |
4 |
modules. As usual with recent perl upgrades, many modules have moved |
5 |
around and now there's a whole whack of new virtuals. One or more are |
6 |
causing problems like this: |
7 |
|
8 |
!!! Multiple package instances within a single package slot have been pulled |
9 |
!!! into the dependency graph, resulting in a slot conflict: |
10 |
|
11 |
dev-lang/perl:0 |
12 |
|
13 |
(dev-lang/perl-5.22.2:0/5.22::gentoo, installed) pulled in by |
14 |
=dev-lang/perl-5.22* required by |
15 |
(virtual/perl-NEXT-0.650.0-r4:0/0::perl-experimental, installed) |
16 |
^ ^^^^^ |
17 |
dev-lang/perl:0/5.22=[-build(-)] required by |
18 |
(perl-gcpan/GnuPG-0.19:0/0::splog-musicbrainz-mirror, installed) |
19 |
^^^^^^^^ |
20 |
(and 435 more with the same problems) |
21 |
|
22 |
(dev-lang/perl-5.24.0:0/5.24::gentoo, ebuild scheduled for merge) |
23 |
pulled in by |
24 |
=dev-lang/perl-5.24* required by |
25 |
(virtual/perl-Exporter-5.720.0-r1:0/0::gentoo, installed) |
26 |
^ ^^^^^ |
27 |
(and 59 more with the same problem) |
28 |
|
29 |
and portage bails out. |
30 |
BUT IT'S NOT A HARD BLOCKER. |
31 |
|
32 |
I've given up trying to figure this out. Masking perl-5.24 and running |
33 |
emerge with "--backtrack=99" gets portage back into a state where it's |
34 |
willing to continue. |
35 |
|
36 |
Perhaps someone else with more patience can figure this one out. |
37 |
|
38 |
|
39 |
-- |
40 |
Alan McKinnon |
41 |
alan.mckinnon@×××××.com |