Bug 2368288

Summary: mg-20250523 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: mgAssignee: Mark McKinstry <mmckinst>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: davide, epel-packagers-sig, mmckinst
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mg-20250523-1.fc42 mg-20250523-1.el10_1 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-06-04 02:10:48 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Update to 20250523 (#2368288) none

Description Upstream Release Monitoring 2025-05-23 17:09:22 UTC 
Releases retrieved: 20250523
Upstream release that is considered latest: 20250523
Current version/release in rawhide: 20240709-4.fc42
URL: https://github.com/hboetes/mg/

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


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/mg
Comment 1 Upstream Release Monitoring 2025-05-23 17:09:38 UTC 
Created attachment 2091304 [details]
Update to 20250523 (#2368288)
Comment 2 Upstream Release Monitoring 2025-05-23 17:14:45 UTC 
the-new-hotness/release-monitoring.org's scratch build of mg-20250523-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=133124937
Comment 3 Fedora Update System 2025-05-26 18:29:00 UTC 
FEDORA-2025-91d66580a3 (mg-20250523-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-91d66580a3
Comment 4 Fedora Update System 2025-05-26 18:29:01 UTC 
FEDORA-EPEL-2025-6e13a06e3d (mg-20250523-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-6e13a06e3d
Comment 5 Fedora Update System 2025-05-27 01:08:59 UTC 
FEDORA-2025-91d66580a3 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-91d66580a3`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-91d66580a3

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 6 Fedora Update System 2025-05-27 02:07:20 UTC 
FEDORA-EPEL-2025-6e13a06e3d 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-6e13a06e3d

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 7 Fedora Update System 2025-06-04 02:10:48 UTC 
FEDORA-2025-91d66580a3 (mg-20250523-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-06-04 03:54:06 UTC 
FEDORA-EPEL-2025-6e13a06e3d (mg-20250523-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.