Github messages for voidlinux
 help / color / mirror / Atom feed
From: tuxliban <tuxliban@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Updated] biber: update to 2.19
Date: Wed, 04 Oct 2023 12:05:11 +0200	[thread overview]
Message-ID: <20231004100511.d0A2--ruyM-nU244m9yLIlLvUhkBtwiXMEQQE7fcFmA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46424@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]

There is an updated pull request by tuxliban against master on the void-packages repository

https://github.com/tuxliban/void-packages biber
https://github.com/void-linux/void-packages/pull/46424

biber: update to 2.19
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **YES**

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, **x86_64-musl**
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - i686
  - x86_64

A patch file from https://github.com/void-linux/void-packages/pull/46424.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-biber-46424.patch --]
[-- Type: text/x-diff, Size: 3022 bytes --]

From dc33e4af68761a70981779453bad19dce5e0e7bb Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?O=2E=20S=C3=A1nchez?= <o-sanchez@linuxmail.org>
Date: Wed, 4 Oct 2023 03:38:14 -0600
Subject: [PATCH] biber: update to 2.19

---
 .../patches/0001-Adapt_to_Perl_5.36.patch     | 40 -------------------
 srcpkgs/biber/template                        |  7 ++--
 2 files changed, 3 insertions(+), 44 deletions(-)
 delete mode 100644 srcpkgs/biber/patches/0001-Adapt_to_Perl_5.36.patch

diff --git a/srcpkgs/biber/patches/0001-Adapt_to_Perl_5.36.patch b/srcpkgs/biber/patches/0001-Adapt_to_Perl_5.36.patch
deleted file mode 100644
index 895813c1f29cd..0000000000000
--- a/srcpkgs/biber/patches/0001-Adapt_to_Perl_5.36.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From d9e961710074d266ad6bdf395c98868d91952088 Mon Sep 17 00:00:00 2001
-From: =?UTF-8?q?Petr=20P=C3=ADsa=C5=99?= <ppisar@redhat.com>
-Date: Wed, 25 May 2022 12:41:59 +0200
-Subject: [PATCH] Adapt to Perl 5.36
-
-A developmental release of Perl 5.36.0 fails to run tests with:
-
-    $ perl -Ilib t/basic-misc.t
-    1..72
-    Can't modify undef operator in scalar assignment at lib/Biber/Section.pm line 433, near "undef;"
-    Compilation failed in require at lib/Biber.pm line 24.
-    BEGIN failed--compilation aborted at lib/Biber.pm line 24.
-    Compilation failed in require at t/basic-misc.t line 11.
-    BEGIN failed--compilation aborted at t/basic-misc.t line 11.
-    # Looks like your test exited with 255 before it could output anything.
-
-This is because of a missing semicolon between commands in
-del_everykeys(). The new perl is more strict and raises a compile-time
-error:
-
-    $ perl -e '$a = undef $b = undef;'
-    Can't modify undef operator in scalar assignment at -e line 1, near "undef;"
-    Execution of -e aborted due to compilation errors.
----
- lib/Biber/Section.pm | 2 +-
- 1 file changed, 1 insertion(+), 1 deletion(-)
-
-diff --git a/lib/Biber/Section.pm b/lib/Biber/Section.pm
-index 03ed69a51..a78942f57 100644
---- a/lib/Biber/Section.pm
-+++ b/lib/Biber/Section.pm
-@@ -429,7 +429,7 @@ sub add_everykey {
- 
- sub del_everykeys {
-   my $self = shift;
--  $self->{everykey} = undef
-+  $self->{everykey} = undef;
-   $self->{everykey_lc} = undef;
-   return;
- }
diff --git a/srcpkgs/biber/template b/srcpkgs/biber/template
index 4389e0d474c3e..63ba6c98e0d4e 100644
--- a/srcpkgs/biber/template
+++ b/srcpkgs/biber/template
@@ -1,8 +1,7 @@
 # Template file for 'biber'
 pkgname=biber
-reverts="2.18_1"
-version=2.16
-revision=3
+version=2.19
+revision=1
 build_style=perl-ModuleBuild
 hostmakedepends="perl-Module-Build"
 makedepends="perl-ExtUtils-LibBuilder"
@@ -54,4 +53,4 @@ license="Artistic-2.0"
 homepage="http://biblatex-biber.sourceforge.net"
 changelog="https://raw.githubusercontent.com/plk/biber/dev/Changes"
 distfiles="https://github.com/plk/biber/archive/v${version}.tar.gz"
-checksum=57111ebc6d0d1933e55d3fe1a92f8ef57c602388ae83598a8073c8a77fd811e2
+checksum=1c1266bc8adb1637c4c59e23c47d919c5a38da4e53544a3c22c21de4a68fc9fe

       reply	other threads:[~2023-10-04 10:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46424@inbox.vuxu.org>
2023-10-04 10:05 ` tuxliban [this message]
2024-01-03  1:46 ` github-actions
2024-01-17  1:47 ` [PR PATCH] [Closed]: " github-actions

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=20231004100511.d0A2--ruyM-nU244m9yLIlLvUhkBtwiXMEQQE7fcFmA@z \
    --to=tuxliban@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).