Bug 2359237 - python-cramjam-2.10.0 is available
Summary: python-cramjam-2.10.0 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: python-cramjam
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ben Beasley
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-04-12 18:17 UTC by Upstream Release Monitoring
Modified: 2025-04-23 02:37 UTC (History)
4 users (show)

Fixed In Version: python-cramjam-2.10.0-1.fc43 python-cramjam-2.10.0-1.fc42 python-cramjam-2.10.0-1.el10_1
Clone Of:
Environment:
Last Closed: 2025-04-13 01:57:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Upstream Release Monitoring 2025-04-12 18:17:34 UTC
Releases retrieved: 2.10.0
Upstream release that is considered latest: 2.10.0
Current version/release in rawhide: 2.10.0~rc1-8.fc43
URL: https://pypi.org/project/cramjam/1.0.0

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/83464/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/python-cramjam

Comment 1 Fedora Update System 2025-04-13 01:54:25 UTC
FEDORA-2025-b8d23f5320 (python-cramjam-2.10.0-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-b8d23f5320

Comment 2 Fedora Update System 2025-04-13 01:57:55 UTC
FEDORA-2025-b8d23f5320 (python-cramjam-2.10.0-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 3 Fedora Update System 2025-04-13 11:00:28 UTC
FEDORA-2025-d486a1fced (python-cramjam-2.10.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-d486a1fced

Comment 4 Fedora Update System 2025-04-13 11:20:39 UTC
FEDORA-EPEL-2025-c819505314 (python-cramjam-2.10.0-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c819505314

Comment 5 Fedora Update System 2025-04-15 20:21:54 UTC
FEDORA-2025-d486a1fced 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-d486a1fced`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d486a1fced

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

Comment 6 Fedora Update System 2025-04-15 20:32:23 UTC
FEDORA-EPEL-2025-c819505314 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-c819505314

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

Comment 7 Fedora Update System 2025-04-23 01:46:15 UTC
FEDORA-2025-d486a1fced (python-cramjam-2.10.0-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2025-04-23 02:37:57 UTC
FEDORA-EPEL-2025-c819505314 (python-cramjam-2.10.0-1.el10_1) has been pushed to the Fedora EPEL 10.1 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.