Bug 2371279 - Update to python-certifi 2025.4.26
Summary: Update to python-certifi 2025.4.26
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-certifi
Version: 42
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Miro Hrončok
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-09 20:13 UTC by Peter Robinson
Modified: 2025-08-08 00:53 UTC (History)
3 users (show)

Fixed In Version: python-certifi-2025.07.09-1.fc43 python-certifi-2025.07.09-1.fc42
Clone Of:
Environment:
Last Closed: 2025-07-30 13:58:19 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Fedora Package Sources python-certifi pull-request 18 0 None None None 2025-07-09 12:58:14 UTC

Description Peter Robinson 2025-06-09 20:13:03 UTC
The current release is 2024.08.30, there's some libraries that need newer versions.

Reproducible: Always

Comment 1 Miro Hrončok 2025-06-10 13:01:10 UTC
> there's some libraries that need newer versions

Could you be a tad more specific? Nothing should actually "need" a never version of this package, but some packages tend to needlessly pin a newer version.

Feel free to send a pull request, if you need this fast. If not, I will eventually get to it.

(Note that the Fedora package removes the bundled certificates and the version number is just a number with no real meaning here.)

Comment 2 Miro Hrončok 2025-06-10 13:02:29 UTC
s/never/newer/

Comment 3 Peter Robinson 2025-06-10 13:44:54 UTC
I am packaging up a GNSS stack (https://github.com/semuconsulting/) and a few of the require newer revs, not sure if there's something specific around GNSS that needs it, a copr build with a 's/2025/2024/' seems OK for build but I am still not at a point I can do full e2e tests.

Comment 4 Miro Hrončok 2025-06-10 14:28:45 UTC
I see commits like https://github.com/semuconsulting/pygnssutils/commit/5a414527ab37dd1f83c0c8e443bef0a7a0c42633

This is to "ensure latest fixes and enhancements are included" -- but our cerifi is a proxy for ca-certificates, so certainly should not be required. 's/2025/2024/' is certainly OK.

That said, I realize it is tedious and an update is in order.

Comment 5 Peter Robinson 2025-06-10 14:30:30 UTC
Thanks for the clarification

Comment 7 Fedora Update System 2025-07-30 13:36:14 UTC
FEDORA-2025-f2fae552b0 (python-certifi-2025.07.09-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-f2fae552b0

Comment 8 Fedora Update System 2025-07-30 13:38:54 UTC
FEDORA-2025-b74ae32177 (python-certifi-2025.07.09-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b74ae32177

Comment 9 Fedora Update System 2025-07-30 13:58:19 UTC
FEDORA-2025-f2fae552b0 (python-certifi-2025.07.09-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-07-31 01:32:51 UTC
FEDORA-2025-b74ae32177 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-b74ae32177`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-b74ae32177

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-08-08 00:53:35 UTC
FEDORA-2025-b74ae32177 (python-certifi-2025.07.09-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.