From: leahneukirchen <leahneukirchen@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: biber: add patch to fix biber on perl 5.36
Date: Mon, 03 Oct 2022 23:37:45 +0200 [thread overview]
Message-ID: <20221003213745.jox1VFRByQ4XvNBmXXvucm63V7t6Ue-3KJi9SbD8yL8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-39682@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1380 bytes --]
There's a merged pull request on the void-packages repository
biber: add patch to fix biber on perl 5.36
https://github.com/void-linux/void-packages/pull/39682
Description:
With perl 5.36, biber now fails with a syntax error:
This patch was taken directly from biber upstream: https://github.com/plk/biber/commit/d9e961710074d266ad6bdf395c98868d91952088 . A clean fix would be updating biber, but as biber is released in lockstep with biblatex (and has strict version requirements going both ways), updating the TeXLive packages isn't really something I'm able to do.
Without this patch, invoking biber at all results in the following crash:
```
$ biber --help
Can't modify undef operator in scalar assignment at /usr/share/perl5/vendor_perl/Biber/Section.pm line 373, near "undef;"
Compilation failed in require at /usr/share/perl5/vendor_perl/Biber.pm line 24.
BEGIN failed--compilation aborted at /usr/share/perl5/vendor_perl/Biber.pm line 24.
Compilation failed in require at /bin/biber line 17.
BEGIN failed--compilation aborted at /bin/biber line 17.
```
#### Testing the changes
- I tested the changes in this PR: **YES**
#### Local build testing
- [x] I built this PR locally for my native architecture, x86_64-glib
- I did **not** build this PR locally for other architectures, as biber is written in perl and the change is relatively minor.
prev parent reply other threads:[~2022-10-03 21:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 21:18 [PR PATCH] " PoroCYon
2022-10-03 21:21 ` [PR PATCH] [Updated] " PoroCYon
2022-10-03 21:37 ` leahneukirchen [this message]
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=20221003213745.jox1VFRByQ4XvNBmXXvucm63V7t6Ue-3KJi9SbD8yL8@z \
--to=leahneukirchen@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).