public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/biber] epel10.2: Provide bcfversion for textlive-biblatex to depend on
Date: Tue, 18 Aug 2026 11:40:28 GMT [thread overview]
Message-ID: <178705322888.1.973145197493012411.rpms-biber-5d63d5339c84@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/biber
Branch : epel10.2
Commit : 5d63d5339c842f28d019a9333641fb60602c2a18
Author : Petr Písař <ppisar@redhat.com>
Date : 2022-01-31T14:50:58+01:00
Stats : +18/-20 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/biber/c/5d63d5339c842f28d019a9333641fb60602c2a18?branch=epel10.2
Log:
Provide bcfversion for textlive-biblatex to depend on
---
diff --git a/biber.spec b/biber.spec
index ec342de..fdbce40 100644
--- a/biber.spec
+++ b/biber.spec
@@ -2,8 +2,10 @@
%bcond_without biber_enables_extra_test
Name: biber
+# Export $BCF_VERSION from lib/Biber/Constants.pm, bug #2048536
+%define bcfversion 3.8
Version: 2.17
-Release: 1%{?dist}
+Release: 2%{?dist}
Summary: Command-line bibliographic manager, BibTeX replacement
# bin/biber: Artistic 2.0
# data/texmap.xsl: Artistic 2.0
@@ -137,25 +139,18 @@ Requires: perl(Text::BibTeX) >= 0.88
# Unicode::Collate::Locale version from Unicode::Collate in Build.PL
Requires: perl(Unicode::Collate::Locale) >= 1.29
Requires: perl(XML::LibXSLT)
-# Biber does not use biblatex, but it expects a compatible biblatex file format
-# (see doc/biber.tex "Compatibility Matrix"):
-# biber | texlive-biblatex
-# ------+-----------------
-# 1.8 | 2.8a
-# 2.1 | 3.0
-# 2.6 | 3.5, 3.6
-# 2.7 | 3.7 (bug #1401482)
-# 2.8 | 3.8
-# 2.9 | 3.9
-# 2.10 | 3.10
-# 2.11 | 3.11
-# 2.12 | 3.12
-# 2.13 | 3.13
-# 2.14 | 3.14
-# (biblatex also has minimum biber requirements). Provided that texlive-biblatex
-# package (e.g. 2020) does not RPM-export biblatex's version (e.g. 3.14) and
-# biblatex reached 3.14 version many years ago, it does not make sense to keep
-# the dependency from biber on texlive-biblatex >= 7:svn42680 here.
+# Biber does not use biblatex, but it requires a compatible version of
+# a biblatex control file (BCF) which is produced by biblatex. See @bcfversion
+# definition in /usr/share/texlive/texmf-dist/tex/latex/biblatex/biblatex.sty
+# and a corresponding $BCF_VERSION in lib/Biber/Constants.pm. Unfortunally,
+# Biber supports only one version of BCF. See "Compatibility Matrix" in
+# doc/biber.tex.
+# Because Biber does not use texlive-biblatex, Biber cannot Require it's exact
+# version. Because it is expensive to rebuild texlive, it's not good to
+# Require a specific biber version from texlive-biblatex.
+# Hence I proposed a bcfversion dependency which both packages can agree on
+# (bug #2048536).
+Provides: bcfversion = %{bcfversion}
# Version at least the main module
Provides: perl(Biber) = %{version}
@@ -263,6 +258,9 @@ export HARNESS_OPTIONS=j$(perl -e 'if ($ARGV[0] =~ /.*-j([0-9][0-9]*).*/) {print
%changelog
+* Mon Jan 31 2022 Petr Pisar <ppisar@redhat.com> - 2.17-2
+- Provide bcfversion for textlive-biblatex to depend on (bug #2048536)
+
* Wed Jan 26 2022 Petr Pisar <ppisar@redhat.com> - 2.17-1
- 2.17 bump
reply other threads:[~2026-08-18 11:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178705322888.1.973145197493012411.rpms-biber-5d63d5339c84@fedoraproject.org \
--to=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox