Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 507718 - >dev-tex/biber-1.7-r1 depends on dev-lang/perl-5.18
Summary: >dev-tex/biber-1.7-r1 depends on dev-lang/perl-5.18
Status: RESOLVED INVALID
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Manuel Rüger (RETIRED)
URL: http://sources.gentoo.org/cgi-bin/vie...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-15 12:08 UTC by Fabian Köster
Modified: 2014-04-15 15:10 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Köster 2014-04-15 12:08:55 UTC
Is there any particular reason dev-tex/biber-1.7 has been dropped? I do not want to upgrade to 1.8 because it indirectly depends on perl-5.18 (via dev-perl/autovivification) and perl-5.18 is not stable yet.

I am running an almost stable system and do not want to maintain long keyword lists. So it would be nice if biber-1.7 would still be supported in main tree until perl-5.18 is becoming stable.

Also having a stable biber version in the future whould be nice, but I will file a separate bug report on this.

Reproducible: Always
Comment 1 Jeroen Roovers (RETIRED) gentoo-dev 2014-04-15 14:31:12 UTC
It isn't gone. You can put the ebuild in a local overlay if you want.
Comment 2 Fabian Köster 2014-04-15 14:40:01 UTC
(In reply to Jeroen Roovers from comment #1)
> It isn't gone. You can put the ebuild in a local overlay if you want.

Thats what I did. But maybe I am not the only one with this concern and it would be nice to know if biber-1.7 is still supported in some way or maybe has been removed because of serious known issues.
Comment 3 Manuel Rüger (RETIRED) gentoo-dev 2014-04-15 14:50:12 UTC
Can you paste your dependency tree? 


You should not need to install perl 5.18 for biber-1.8. It works with perl 5.16.2
Comment 4 Fabian Köster 2014-04-15 15:03:03 UTC
I just saw Portage was wrong about blaming dev-perl/autovivification for depending on perl-5.18. Really it is virtual/perl-Exporter-5.680.0 which depends on 

>=dev-lang/perl-5.17.11
Comment 5 Fabian Köster 2014-04-15 15:10:39 UTC
Ok, I found out I can use perl-core/Exporter-5.680.0 as provider for virtual/perl-Exporter-5.680.0 by kewording it. Then I am able to use it with perl-5.16. Sorry for the noise and thanks for your help!