public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
To: git-commits@fedoraproject.org
Subject: [rpms/python3.13] epel10: Fixup: BuildRequire ca-certificates when built --without rpmwheels
Date: Thu, 19 Nov 2026 11:12:10 GMT [thread overview]
Message-ID: <179508673070.1.2714106628839998866.rpms-python3.13-1c8e2a07ec12@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python3.13
Branch : epel10
Commit : 1c8e2a07ec122657e9af1907815b76674bc9a09d
Author : Miro Hrončok <miro@hroncok.cz>
Date : 2026-11-05T11:08:55+01:00
Stats : +2/-1 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python3.13/c/1c8e2a07ec122657e9af1907815b76674bc9a09d?branch=epel10
Log:
Fixup: BuildRequire ca-certificates when built --without rpmwheels
That is when we use bundled pip.whl patched to use ca-certificates.
When building --with rpmwheels, ca-certificates is brought by python-pip-wheel.
This is a shameful fixup for the pip-dummy-certifi.patch addition
(after it was already backported to all Pythons with this small bug),
but it makes no real difference (ca-certificates is pulled in anyway).
[skip changelog]
(cherry picked from python3.16 commit b36a3d47eb448f564ef8f87502beb25246c2f4d1)
---
diff --git a/python3.13.spec b/python3.13.spec
index d8dfbd1..d4017d6 100644
--- a/python3.13.spec
+++ b/python3.13.spec
@@ -314,8 +314,9 @@ BuildRequires: libappstream-glib
BuildRequires: %{python_wheel_pkg_prefix}-pip-wheel >= 23.1.2
%if %{with tests}
BuildRequires: %{python_wheel_pkg_prefix}-setuptools-wheel >= 71
-BuildRequires: ca-certificates
%endif
+%else
+BuildRequires: ca-certificates
%endif
%if %{without bootstrap}
reply other threads:[~2026-11-19 11:12 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=179508673070.1.2714106628839998866.rpms-python3.13-1c8e2a07ec12@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