Bug 2379763 - gambit-c-4.9.7 is available
Summary: gambit-c-4.9.7 is available
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: gambit-c
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Benson Muite
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-07-13 14:41 UTC by Upstream Release Monitoring
Modified: 2025-07-27 01:33 UTC (History)
1 user (show)

Fixed In Version: gambit-c-4.9.7-1.fc42 gambit-c-4.9.7-1.fc41
Clone Of:
Environment:
Last Closed: 2025-07-27 01:21:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Update to 4.9.7 (#2379763) (1014 bytes, patch)
2025-07-13 14:41 UTC, Upstream Release Monitoring
no flags Details | Diff

Description Upstream Release Monitoring 2025-07-13 14:41:08 UTC
Releases retrieved: 4.9.7
Upstream release that is considered latest: 4.9.7
Current version/release in rawhide: 4.9.6-1.fc43
URL: http://gambitscheme.org/

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/872/


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

Comment 1 Upstream Release Monitoring 2025-07-13 14:41:16 UTC
Created attachment 2097130 [details]
Update to 4.9.7 (#2379763)

Comment 2 Upstream Release Monitoring 2025-07-13 14:54:33 UTC
the-new-hotness/release-monitoring.org's scratch build of gambit-c-4.9.7-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=134787114

Comment 3 Fedora Update System 2025-07-18 08:50:46 UTC
FEDORA-2025-7c0ad22b11 (gambit-c-4.9.7-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7c0ad22b11

Comment 4 Fedora Update System 2025-07-18 08:51:14 UTC
FEDORA-2025-676cc58bdf (gambit-c-4.9.7-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-676cc58bdf

Comment 5 Fedora Update System 2025-07-19 21:14:53 UTC
FEDORA-2025-676cc58bdf has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-676cc58bdf \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-676cc58bdf

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

Comment 6 Fedora Update System 2025-07-19 22:01:24 UTC
FEDORA-2025-7c0ad22b11 has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf install --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-7c0ad22b11 \*`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-7c0ad22b11

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

Comment 7 Fedora Update System 2025-07-27 01:21:58 UTC
FEDORA-2025-676cc58bdf (gambit-c-4.9.7-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-07-27 01:33:24 UTC
FEDORA-2025-7c0ad22b11 (gambit-c-4.9.7-1.fc41) has been pushed to the Fedora 41 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.