I was using ancient versions of biblatex and biber long removed from the tree because I was otherwise forced to upgrade to perl-5.22. As things were working fine, I put in some masks and waited for perl-5.22 to stabilize. Now that perl-5.22 is stable, I went on and tried to upgrade to biber 2.4. However, I got the following blockers: (dev-lang/perl-5.24.0-r1:0/5.24::gentoo, ebuild scheduled for merge) pulled in by =dev-lang/perl-5.24* required by (virtual/perl-Digest-1.170.0-r6:0/0::gentoo, installed) ^ ^^^^^ =dev-lang/perl-5.24* required by (virtual/perl-Digest-MD5-2.540.0-r1:0/0::gentoo, installed) ^ ^^^^^ =dev-lang/perl-5.24* required by (virtual/perl-Digest-SHA-5.950.0-r1:0/0::gentoo, installed) ^ ^^^^^ =dev-lang/perl-5.24* required by (virtual/perl-Unicode-Normalize-1.250.0-r1:0/0::gentoo, ebuild scheduled for merge) ^ ^^^^^ =dev-lang/perl-5.24* required by (virtual/perl-Unicode-Collate-1.140.0-r1:0/0::gentoo, ebuild scheduled for merge) ^ ^^^^^ I think the perl-Digest* ones are mistakes, given that those versions are stable and I have them installed. However, perl-Unicode-Normalize-1.250.0 and perl-Unicode-Collate-1.140.0-r1 do indeed depend on perl-5.24. I haven't found all biber's explicit dependencies, but I find it strange that biber-2.4 would depend on perl-5.24 modules, given that it explicitly depends on just perl-5.16! Could it be that there is some error here? I would really like to install a version of biber that is in the tree, but am not willing to install perl-5.24 as I run a (mostly) stable system. I'm not the first to encounter this kind of problem with biber, see bug 507718 (RESOLVED INVALID, but still).
> Could it be that there is some error here? I would really like to install a version of biber that is in the tree, but am not willing to install perl-5.24 as I run a (mostly) stable system. This is a dangerous thing to attempt with Perl, and means you entertain the risk of a future upgrade where portage gets confused. However, if you wish to run biber ( unstable ), you're going to need to do one of the following: 1. Run unstable perl ( and ideally, make your entire system unstable ) 2. Run unstable copies of all of the following: - virtual/perl-Unicode-Collate - virtual/perl-Unicode-Normalize - perl-core/Unicode-Collate - perl-core/Unicode-Normalize If you pay careful attention to the ebuild you *think* is forcing an upgrade to perl-5.24, you'll find they have a conditional "|| ( )" which says: "This can be satisfied by dev-lang/perl-5.24 OR perl-core/MyName-MyVersion" grep '5.24' virtual/perl-Unicode-*/*.ebuild virtual/perl-Unicode-Collate/perl-Unicode-Collate-1.140.0-r1.ebuild: || ( =dev-lang/perl-5.24* ~perl-core/${PN#perl-}-${PV} ) virtual/perl-Unicode-Normalize/perl-Unicode-Normalize-1.250.0-r1.ebuild: || ( =dev-lang/perl-5.24* ~perl-core/${PN#perl-}-${PV} ) As such, this is not really a "bug", you've just got a misconfigured system. The perl-5.16 dependency from biber itself only indicates that *biber* needs perl 5.16 to run, as long as its dependencies are satisified on 5.16 ( which they can be, using CPAN/perl-core as a provider instead of perl ), then biber should run on Perl 5.16 Please reopen this bug if I'm wrong.
(In reply to Kent Fredric (IRC: kent\n) from comment #1) > > grep '5.24' virtual/perl-Unicode-*/*.ebuild > virtual/perl-Unicode-Collate/perl-Unicode-Collate-1.140.0-r1.ebuild: || ( > =dev-lang/perl-5.24* ~perl-core/${PN#perl-}-${PV} ) > virtual/perl-Unicode-Normalize/perl-Unicode-Normalize-1.250.0-r1.ebuild: || > ( =dev-lang/perl-5.24* ~perl-core/${PN#perl-}-${PV} ) > > As such, this is not really a "bug", you've just got a misconfigured system. Thanks! Adding the two perl-core/Unicode-... packages to my accept_keywords file fixed it.
