public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-zstandard] epel9: update to 0.24.0 (resolves rhbz#2389036)
Date: Thu, 13 Aug 2026 08:05:17 GMT	[thread overview]
Message-ID: <178660831709.1.1625413640372696149.rpms-python-zstandard-ae85ab323c48@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-zstandard
            Branch : epel9
            Commit : ae85ab323c480ab0ff60a6788f5dc61e43366674
            Author : Dominik 'Rathann' Mierzejewski <dominik@greysector.net>
            Date   : 2025-09-12T22:13:51+02:00
            Stats  : +10/-42 in 5 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-zstandard/c/ae85ab323c480ab0ff60a6788f5dc61e43366674?branch=epel9

            Log:
            update to 0.24.0 (resolves rhbz#2389036)

- drop obsolete patches

---
diff --git a/.gitignore b/.gitignore
index 90794ea..ab6133d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -8,3 +8,4 @@
 /zstandard-0.21.0.tar.gz
 /zstandard-0.22.0.tar.gz
 /zstandard-0.23.0.tar.gz
+/zstandard-0.24.0.tar.gz

diff --git a/python-zstandard-deps.patch b/python-zstandard-deps.patch
deleted file mode 100644
index a86f4dc..0000000
--- a/python-zstandard-deps.patch
+++ /dev/null
@@ -1,18 +0,0 @@
-diff -up zstandard-0.23.0/pyproject.toml.orig zstandard-0.23.0/pyproject.toml
---- zstandard-0.23.0/pyproject.toml.orig	2024-07-14 23:58:50.000000000 +0200
-+++ zstandard-0.23.0/pyproject.toml	2024-10-03 16:27:20.742934487 +0200
-@@ -1,12 +1,12 @@
- [build-system]
- requires = [
-     "cffi>=1.16.0; python_version <= '3.12'",
--    "cffi==1.17.0rc1; python_version >= '3.13'",
-+    "cffi>=1.17.0; python_version >= '3.13'",
-     # 69.0.0 breaks handling of --config-settings=--build-option, which our CI
-     # relies on. So constrained to an older version until we figure out a
-     # workaround. See comment at
-     # https://github.com/pypa/pip/issues/11859#issuecomment-2132287974.
--    "setuptools<69.0.0",
-+    "setuptools",
- ]
- # Need to use legacy backend because setup_zstd.py breaks build isolation.
- build-backend = "setuptools.build_meta:__legacy__"

diff --git a/python-zstandard-py314.patch b/python-zstandard-py314.patch
deleted file mode 100644
index a2b2d8d..0000000
--- a/python-zstandard-py314.patch
+++ /dev/null
@@ -1,15 +0,0 @@
-diff -up zstandard-0.23.0/zstandard/__init__.py.py314 zstandard-0.23.0/zstandard/__init__.py
---- zstandard-0.23.0/zstandard/__init__.py.py314	2024-07-14 23:58:50.000000000 +0200
-+++ zstandard-0.23.0/zstandard/__init__.py	2025-03-28 17:16:47.339256930 +0100
-@@ -18,7 +18,10 @@ import io
- import os
- import platform
- 
--from typing import ByteString
-+try:
-+    from typing import ByteString
-+except ImportError:
-+    from collections.abc import Buffer as ByteString
- 
- # Some Python implementations don't support C extensions. That's why we have
- # a CFFI implementation in the first place. The code here import one of our

diff --git a/python-zstandard.spec b/python-zstandard.spec
index afde0ad..4b3769d 100644
--- a/python-zstandard.spec
+++ b/python-zstandard.spec
@@ -10,17 +10,13 @@
 compression library. A C extension and CFFI interface are provided.
 
 Name: python-%{pypi_name}
-Version: 0.23.0
-Release: 6%{?dist}
+Version: 0.24.0
+Release: 1%{?dist}
 Summary: Zstandard bindings for Python
 License: (BSD-3-Clause OR GPL-2.0-only) AND MIT
 URL: https://github.com/indygreg/python-zstandard
 Source0: %{pypi_source}
 Patch0: %{name}-py313.patch
-# relax dependencies so that auto BR generation works
-Patch1: %{name}-deps.patch
-# https://github.com/indygreg/python-zstandard/issues/238
-Patch2: %{name}-py314.patch
 
 %description
 %{desc}
@@ -35,7 +31,7 @@ BuildRequires: python3dist(pytest)
 BuildRequires: python3dist(pytest-xdist)
 %endif
 # https://github.com/indygreg/python-zstandard/issues/48
-Provides: bundled(zstd) = 1.5.6
+Provides: bundled(zstd) = 1.5.7
 
 %description -n python3-%{pypi_name}
 %{desc}
@@ -54,7 +50,7 @@ rm -r %{pypi_name}.egg-info
 
 %install
 %pyproject_install
-%pyproject_save_files -l %{pypi_name}
+%pyproject_save_files -L %{pypi_name}
 
 %check
 %pyproject_check_import
@@ -71,6 +67,10 @@ mv zstandard{.src,}
 %doc README.rst
 
 %changelog
+* Fri Sep 12 2025 Dominik Mierzejewski <dominik@greysector.net> - 0.24.0-1
+- update to 0.24.0 (resolves rhbz#2389036)
+- drop obsolete patches
+
 * Fri Aug 15 2025 Python Maint <python-maint@redhat.com> - 0.23.0-6
 - Rebuilt for Python 3.14.0rc2 bytecode
 

diff --git a/sources b/sources
index 6cfc1cb..7c30c08 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (zstandard-0.23.0.tar.gz) = 8b408fe537b783f61451f2024250402e38892d6feb4cfb935664d7a53d6e13d7e7e7b7687256613ea189763f70ef62d513332c879f26e55b524bb5941295840c
+SHA512 (zstandard-0.24.0.tar.gz) = 6590ddf40958a16894c4239811054f50d07451fe9649bb5ea59918f83826498ce2d5a777f84bb68479de30fcb7308e8d579794b6ad0d3412b736638d85d1c0c2

                 reply	other threads:[~2026-08-13  8:05 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=178660831709.1.1625413640372696149.rpms-python-zstandard-ae85ab323c48@fedoraproject.org \
    --to=dominik@greysector.net \
    --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