Heads up to any ~arch users who might run into this.
I've just spent too many annoying hours dealing with perl-5.24 and it's
modules. As usual with recent perl upgrades, many modules have moved
around and now there's a whole whack of new virtuals. One or more are
causing problems like this:
!!! Multiple package instances within a single package slot have been pulled
!!! into the dependency graph, resulting in a slot conflict:
dev-lang/perl:0
(dev-lang/perl-5.22.2:0/5.22::gentoo, installed) pulled in by
=dev-lang/perl-5.22* required by
(virtual/perl-NEXT-0.650.0-r4:0/0::perl-experimental, installed)
^ ^^^^^
dev-lang/perl:0/5.22=[-build(-)] required by
(perl-gcpan/GnuPG-0.19:0/0::splog-musicbrainz-mirror, installed)
^^^^^^^^
(and 435 more with the same problems)
(dev-lang/perl-5.24.0:0/5.24::gentoo, ebuild scheduled for merge)
pulled in by
=dev-lang/perl-5.24* required by
(virtual/perl-Exporter-5.720.0-r1:0/0::gentoo, installed)
^ ^^^^^
(and 59 more with the same problem)
and portage bails out.
BUT IT'S NOT A HARD BLOCKER.
I've given up trying to figure this out. Masking perl-5.24 and running
emerge with "--backtrack=99" gets portage back into a state where it's
willing to continue.
Perhaps someone else with more patience can figure this one out.
--
Alan McKinnon
[email protected]
