Hide Forgot
Description of problem: Currently, when using biber in conjunction with texlive. There is an error that the versions don't match: Process started: biber "201908_LoansOilIndustry_Article" INFO - This is Biber 2.11 INFO - Logfile is '201908_LoansOilIndustry_Article.blg' INFO - Reading '201908_LoansOilIndustry_Article.bcf' ERROR - Error: Found biblatex control file version 3.5, expected version 3.4. This means that your biber (2.11) and biblatex (3.12) versions are incompatible. See compat matrix in biblatex or biber PDF documentation. INFO - ERRORS: 1 Process exited with error(s) Version-Release number of selected component (if applicable): biber - 2.11-6 How reproducible: Compile tex file with biblatex and execute biber afterwards. Actual results: Citations are not displayed. Expected results: Citations are properly displayed in the document.
It should be updated to 2.12, not to the latest version 2.13, because this would then again be incompatible.
FEDORA-2019-4f075bc426 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2019-4f075bc426
biber-2.12-1.fc31 has been pushed to the Fedora 31 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2019-4f075bc426
On a related note, would it be somehow possible to check the compatibility of the versions on the rpm level? I mean could texlive require the necessary version of the biber package? This would prevent this from happening again.
Yeah it should definitely be improved. See #1561929. Would be happy for your help/input/debugging over there: I don't really know enough about texlive packaging to accomplish what I want to happen (see TODOs at top of spec file and comments by @spot).
biber-2.12-1.fc31 has been pushed to the Fedora 31 stable repository. If problems still persist, please make note of it in this bug report.