public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/pyproject-rpm-macros] rawhide: CI: Adjust spec files for flit-core 4 and flit-core 3
Date: Tue, 25 Aug 2026 09:22:13 GMT	[thread overview]
Message-ID: <178764973350.1.10233558255084798817.rpms-pyproject-rpm-macros-a67088516a38@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/pyproject-rpm-macros
            Branch : rawhide
            Commit : a67088516a388d2ce5407eb534c9b5af7f96408a
            Author : Miro Hrončok <miro@hroncok.cz>
            Date   : 2026-08-24T20:59:42+02:00
            Stats  : +6/-4 in 2 file(s)
            URL    : https://src.fedoraproject.org/rpms/pyproject-rpm-macros/c/a67088516a388d2ce5407eb534c9b5af7f96408a?branch=rawhide

            Log:
            CI: Adjust spec files for flit-core 4 and flit-core 3

entrypoints now always uses flit-core < 4
(that allows flit to be upgraded to 4 in Fedora).

markdown-it-py allows flit-core 4 as it already has the [project] table.

This way, we can also use the individual specs in the CI of python-flit-core3
and python-flit-core.

---
diff --git a/tests/python-entrypoints.spec b/tests/python-entrypoints.spec
index f4876f6..15431ab 100644
--- a/tests/python-entrypoints.spec
+++ b/tests/python-entrypoints.spec
@@ -26,10 +26,9 @@ Summary:        %{summary}
 
 %prep
 %autosetup -p1 -n %{pypi_name}-%{version}
-%if 0%{?rhel}
-# force the flit-core build backend, as that is available rather than full flit
-sed -i 's/"flit/"flit_core/' pyproject.toml
-%endif
+# force the flit-core build backend, as that is available even in RHEL
+# also, pin to < 4 becasue this project uses [tool.flit.metadata]
+sed -i -e 's/"flit"/"flit_core<4"/' -e 's/"flit.buildapi"/"flit_core.buildapi"/' pyproject.toml
 
 
 %generate_buildrequires

diff --git a/tests/python-markdown-it-py.spec b/tests/python-markdown-it-py.spec
index 2db91ca..733a081 100644
--- a/tests/python-markdown-it-py.spec
+++ b/tests/python-markdown-it-py.spec
@@ -25,6 +25,9 @@ Summary:        %{summary}
 %prep
 %autosetup -p1 -n markdown-it-py-%{version}
 
+# This package builds successfully with flit-core 4
+%pyproject_patch_dependency flit_core:set_upper:5
+
 %generate_buildrequires
 %pyproject_buildrequires --extras testing,linkify --pyproject-dependencies
 

                 reply	other threads:[~2026-08-25  9:22 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=178764973350.1.10233558255084798817.rpms-pyproject-rpm-macros-a67088516a38@fedoraproject.org \
    --to=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