Due to a regression in 1.7 that is fixed in the upcoming 1.8 release, I need a live ebuild for biber. This used to exist in the mrueg overlay (as biber-9999) before biber entered the main tree. I would be grateful if it is revived in the main tree. Reproducible: Always
Sorry, i don't plan to maintain a live ebuild in tree. The problem is the mozilla-ca patch which tends to fail from time to time and I don't want to add mozilla-ca as another package in tree. Meanwhile: biber 1.8 is in tree.
(In reply to Manuel Rüger from comment #1) > Sorry, i don't plan to maintain a live ebuild in tree. > The problem is the mozilla-ca patch which tends to fail from time to time > and I don't want to add mozilla-ca as another package in tree. Ok, I understand; I'll close this bug. (I much appreciate your maintainership of the standard ebuild. But you know: once you give a hand, people would like an arm ;-).) > Meanwhile: biber 1.8 is in tree. That version should solve my issue; however, it indirectly depends on a version of perl that is not in the main tree. Do you get your perl elsewhere? # emerge -qa =dev-tex/biber-1.8 emerge: there are no ebuilds to satisfy "~dev-lang/perl-5.17.11". (dependency required by "virtual/perl-Exporter-5.680.0" [ebuild]) (dependency required by "dev-perl/autovivification-0.120.0" [ebuild]) (dependency required by "dev-tex/biber-1.8" [ebuild]) (dependency required by "=dev-tex/biber-1.8" [argument])
This is related to https://bugs.gentoo.org/show_bug.cgi?id=490524
(In reply to Erik Quaeghebeur from comment #2) > (In reply to Manuel Rüger from comment #1) > > Sorry, i don't plan to maintain a live ebuild in tree. > > The problem is the mozilla-ca patch which tends to fail from time to time > > and I don't want to add mozilla-ca as another package in tree. > > Ok, I understand; I'll close this bug. (I much appreciate your > maintainership of the standard ebuild. But you know: once you give a hand, > people would like an arm ;-).) > What's missing in my last reply: You could try to upstream the drop-mozilla-ca.patch, then I think there will be no problem in adding a live ebuild.
