public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Tom Callaway <spot@fedoraproject.org>
To: git-commits@fedoraproject.org
Subject: [rpms/biber] epel10.2: update to 2.14 for TL 2020
Date: Tue, 18 Aug 2026 11:40:19 GMT	[thread overview]
Message-ID: <178705321931.1.6112368058271942236.rpms-biber-254484302a9f@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/biber
Branch : epel10.2
Commit : 254484302a9fc09cbee0058f22155d801b9646f1
Author : Tom Callaway <spot@fedoraproject.org>
Date   : 2020-05-14T18:47:51-04:00
Stats  : +8/-11 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/biber/c/254484302a9fc09cbee0058f22155d801b9646f1?branch=epel10.2

Log:
update to 2.14 for TL 2020

---
diff --git a/.gitignore b/.gitignore
index 069695f..53dcb3b 100644
--- a/.gitignore
+++ b/.gitignore
@@ -5,3 +5,4 @@
 /v2.7.tar.gz
 /v2.11.tar.gz
 /v2.12.tar.gz
+/v2.14.tar.gz

diff --git a/biber.spec b/biber.spec
index 6d5829d..1d7cb06 100644
--- a/biber.spec
+++ b/biber.spec
@@ -1,16 +1,12 @@
 Name:           biber
-Version:        2.12
-Release:        2%{?dist}
+Version:        2.14
+Release:        1%{?dist}
 Summary:        Command-line bibliographic manager, BibTeX replacement
 License:        (GPL+ or Artistic 2.0) and Artistic 2.0
 URL:            http://biblatex-biber.sourceforge.net/
 Source0:        https://github.com/plk/biber/archive/v%{version}.tar.gz
 # not appropriate for upstream: http://github.com/plk/biber/pull/97
 Patch0:         biber-drop-builddeps-for-monolithic-build.patch
-# Adapt tests to Unicode-Collate-1.27, bug #1674692, in upstream after 2.12
-Patch1:         biber-2.12-backport-test-changes-for-U-C-fix.patch
-Patch2:         biber-2.12-Updated-tests-after-U-C-upgrade-changed-sortinit.patch
-Patch3:         biber-2.12-backport-test-changes-after-U-C-fix.patch
 BuildArch:      noarch
 
 BuildRequires:  perl-interpreter
@@ -146,9 +142,6 @@ functionality.  It is often used with the popular BibLaTeX package
 %prep
 %setup -q -n biber-%{version}
 %patch0 -p1
-%patch1 -p1
-%patch2 -p1
-%patch3 -p1
 
 
 %build
@@ -166,7 +159,7 @@ chmod u+w %{buildroot}%{_bindir}/*
 
 
 %files
-%doc README.md Changes THANKS TODO.org
+%doc README.md Changes TODO.org
 %{_bindir}/%{name}
 %{_mandir}/man3/*
 %{_mandir}/man1/*
@@ -174,6 +167,9 @@ chmod u+w %{buildroot}%{_bindir}/*
 
 
 %changelog
+* Thu May 14 2020 Tom Callaway <spot@fedoraproject.org> - 2.14-1
+- update to 2.14 for TL 2020
+
 * Tue Jan 28 2020 Fedora Release Engineering <releng@fedoraproject.org> - 2.12-2
 - Rebuilt for https://fedoraproject.org/wiki/Fedora_32_Mass_Rebuild
 

diff --git a/sources b/sources
index a4ca1ce..ff5fdb3 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (v2.12.tar.gz) = 72f1a05224dc2735b32e92ac376d392fb631bf788a15de449471fdc5a94182ad4434ce71f95281e4cfc3a06cd275d2ff98e526d540c2979cd3e0dfa15b5c75ff
+SHA512 (v2.14.tar.gz) = dd42aabdb8f469ea759a4a7bb97cbe27ebe57e46d1b6dde7d293d1b046a55e20ac889bf9c8c6b6219ee827b162a280bf7aca239af1f357ee1ccc90600a5dcfc1

                 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=178705321931.1.6112368058271942236.rpms-biber-254484302a9f@fedoraproject.org \
    --to=spot@fedoraproject.org \
    --cc=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