From: unspecd <unspecd@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] python3-zstandard: update to 0.22.0.
Date: Sat, 30 Mar 2024 14:20:58 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49606@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1329 bytes --]
There is a new pull request by unspecd against master on the void-packages repository
https://github.com/unspecd/void-packages python3-zstandard
https://github.com/void-linux/void-packages/pull/49606
python3-zstandard: update to 0.22.0.
Also: use bundled libzstd instead of the system one: python3-zstandard requires the specific version of libzstd, 1.5.5.
<!-- Uncomment relevant sections and delete options which are not applicable -->
#### Testing the changes
- I tested the changes in this PR: **briefly**
<!--
#### 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):
A patch file from https://github.com/void-linux/void-packages/pull/49606.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-python3-zstandard-49606.patch --]
[-- Type: text/x-diff, Size: 1581 bytes --]
From ae46e563b9ea906d92f9dc73ce87ab529e135cba Mon Sep 17 00:00:00 2001
From: Evgeny Ermakov <evgeny.v.ermakov@gmail.com>
Date: Sat, 30 Mar 2024 12:10:42 +1100
Subject: [PATCH] python3-zstandard: update to 0.22.0.
Also: use bundled libzstd instead of the system one:
python3-zstandard requires the specific version of libzstd, 1.5.5.
---
srcpkgs/python3-zstandard/template | 9 ++++-----
1 file changed, 4 insertions(+), 5 deletions(-)
diff --git a/srcpkgs/python3-zstandard/template b/srcpkgs/python3-zstandard/template
index d59cbb09b965fc..ff4a8754920d1f 100644
--- a/srcpkgs/python3-zstandard/template
+++ b/srcpkgs/python3-zstandard/template
@@ -1,11 +1,10 @@
# Template file for 'python3-zstandard'
pkgname=python3-zstandard
-version=0.21.0
-revision=3
+version=0.22.0
+revision=1
build_style=python3-module
-make_build_args="--system-zstd"
hostmakedepends="python3-setuptools"
-makedepends="python3-devel libzstd-devel"
+makedepends="python3-devel"
depends="python3"
checkdepends="python3-hypothesis"
short_desc="Python bindings to the Zstandard (zstd) compression library"
@@ -14,7 +13,7 @@ license="BSD-3-Clause"
homepage="https://github.com/indygreg/python-zstandard"
changelog="https://raw.githubusercontent.com/indygreg/python-zstandard/main/docs/news.rst"
distfiles="https://github.com/indygreg/python-zstandard/archive/${version}.tar.gz"
-checksum=15adc6bfa629d48b0bb658e9eae94c484adb66a28738fa780478eebeb41599a5
+checksum=34ce7ef020afca1344c538a778e2a2e30dc43b11509aa4cb5cf076228d959ca7
pre_check() {
# The skipped test ignored due to failure, see:
next reply other threads:[~2024-03-30 13:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 13:20 unspecd [this message]
2024-03-30 13:24 ` unspecd
2024-03-30 22:51 ` tornaria
2024-03-31 21:39 ` tornaria
2024-03-31 23:36 ` leahneukirchen
2024-05-05 7:36 ` [PR PATCH] [Updated] " unspecd
2024-05-05 21:53 ` tornaria
2024-05-06 12:10 ` [PR PATCH] [Merged]: " leahneukirchen
2024-03-31 21:21 [PR PATCH] " r-ricci
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=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-49606@inbox.vuxu.org \
--to=unspecd@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).