Summary: | =dev-tex/biblatex-3.4 breaks biblatex with =dev-tex/biber-2.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Martin Wegner <gentoo-bugs> |
Component: | Current packages | Assignee: | Manuel Rüger (RETIRED) <mrueg> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | diazona, eugene.shalygin, hendrik, karl.j.linden, mvaenskae, tex |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 585928 | ||
Bug Blocks: |
Description
Martin Wegner
2016-05-25 09:40:53 UTC
I can confirm that, same here. I added biber-2.5 to my own overlay. https://github.com/JelteF/jelte-overlay I also think a dependency constraint would make sense. However that would need to be updated every time for a new version. So I don't know if it would help that much. The solution is to bump biber to 2.5. i have created a ticket to bump biber 2.5: Bug 585928 Can the biblatex packages not have biber added as a runtime dependency, or at least a helpful post-merge message telling the user which version of biber they should install? Compatability matrix here (page 6): http://tug.ctan.org/macros/latex/exptl/biblatex/doc/biblatex.pdf Currently biber depends on >=dev-tex/biblatex-3.2. In my opinion that should be dev-tex/biblatex-3.3* (or whatever version is required as listed in the matrix). No need for a dependency from biblatex to biber for that. Okay that would work too, I was figuring that most people pull in biblatex rather than biber, but of course biblatex does work without it. As long as the dependencies are sorted out so that correct biblatex/biber versions are installed together. But it needs to be taken care of properly as this bites me every time a new version of biber/biblatex hits the tree. This is infrequent enough that I have forgotten what the problem/solution was the next time it comes around and a new hour of frantic googling ensues, and I can't be the only one... (In reply to Jelte Fennema from comment #2) > I added biber-2.5 to my own overlay. > https://github.com/JelteF/jelte-overlay > > I also think a dependency constraint would make sense. However that would > need to be updated every time for a new version. So I don't know if it would > help that much. Thanks for the overlay. However, according to portage, the tar.gz file I download directly from biber's sourceforge repository fails the checksum, and there doesn't seem to be anywhere else to find the "correct" version. Can you double-check that the file's hash is correct, or post a link? > Thanks for the overlay. However, according to portage, the tar.gz file I
> download directly from biber's sourceforge
blah blah blah.
Sorry, I am dumb and impatient. Portage eventually found the github repository and got the "correct" version of the file. Cheers.
Cheers, this issue is still not resolved in the official repository. When can we expect a fix? It seems to have been now close to 2 months. I am still on devaway till the beginning of August, as I moved recently.[1] You can still use biblatex-3.3 with biber-2.4. [1] https://www.gentoo.org/inside-gentoo/developers/unavailable-developers.html > You can still use biblatex-3.3 with biber-2.4.
Could this be enforced with a more strict version dependency?
I also just ran into this issue and it took me q
...uite a while to figure things out (sorry, accidentally hit send). Note that #585928 mentions version bumps which would also fix this issue. As upstream says it should be used with 3.4, I've updated the requirement for bibtex-2.5 commit e3f4fa273dc2ae5948900fe44c2c76931e963a0b Author: Manuel Rüger <mrueg@gentoo.org> Date: Mon Sep 26 21:49:23 2016 +0200 dev-tex/biber: Require ~biblatex-3.4 Package-Manager: portage-2.3.1 |