public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Karolina Surma <ksurma@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-pkginfo] epel10: Port tests to PEP 639 (Resolves: rhbz#2359507)
Date: Tue, 15 Sep 2026 09:38:41 GMT	[thread overview]
Message-ID: <178946512102.1.6080756773361348497.rpms-python-pkginfo-de45f77b4e1b@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/python-pkginfo
            Branch : epel10
            Commit : de45f77b4e1bc95d5a1bc750cb233744c77cba2b
            Author : Karolina Surma <ksurma@redhat.com>
            Date   : 2026-09-15T10:33:25+01:00
            Stats  : +2/-0 in 1 file(s)
            URL    : https://src.fedoraproject.org/rpms/python-pkginfo/c/de45f77b4e1bc95d5a1bc750cb233744c77cba2b?branch=epel10

            Log:
            Port tests to PEP 639 (Resolves: rhbz#2359507)

The test in question checks the metadata of Fedora-installed
python3-wheel.
Fedora already produces this package with PEP 639, and metadata 2.4.
Upstream, that project's metadata is still 2.3, hence only a downstream
patch for now.

---
diff --git a/python-pkginfo.spec b/python-pkginfo.spec
index 5448add..d4285b0 100644
--- a/python-pkginfo.spec
+++ b/python-pkginfo.spec
@@ -46,6 +46,8 @@ This package contains the documentation.
 
 # don't ship internal test subpackage
 sed -i "s/, 'pkginfo.tests'//g" setup.py
+# work around the wheel metadata version (Fedora already produces 2.4 while upstream it's still 2.3)
+sed -i "s/assert(installed.metadata_version == '2.3')/assert(installed.metadata_version == '2.4')/" pkginfo/tests/test_installed.py
 
 # Remove bundled egg-info
 rm -rf %{pypi_name}.egg-info

                 reply	other threads:[~2026-09-15  9:38 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=178946512102.1.6080756773361348497.rpms-python-pkginfo-de45f77b4e1b@fedoraproject.org \
    --to=ksurma@redhat.com \
    --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