Bug 2249294

Summary: mpich-4.2.1 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: mpichAssignee: Zbigniew Jędrzejewski-Szmek <zbyszek>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: zbyszek
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: mpich-4.2.1-1.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-04-19 07:12:26 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 4.2.0b1 (#2249294)
none
Update to 4.2.0b1 (#2249294)
none
Update to 4.2.0b1 (#2249294)
none
Update to 4.2.0b1 (#2249294)
none
Update to 4.2.0b1 (#2249294)
none
Update to 4.2.0b1 (#2249294)
none
Update to 4.2.1 (#2249294) none

Description Upstream Release Monitoring 2023-11-11 23:54:12 UTC
Releases retrieved: 4.2.0b1
Upstream release that is considered latest: 4.2.0b1
Current version/release in rawhide: 4.1.2-7.fc40
URL: http://www.mpich.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/8071/


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

Comment 1 Upstream Release Monitoring 2023-11-11 23:54:26 UTC
Created attachment 1998713 [details]
Update to 4.2.0b1 (#2249294)

Comment 2 Upstream Release Monitoring 2023-11-12 00:15:04 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=108916399

Comment 3 Upstream Release Monitoring 2023-12-14 02:40:36 UTC
Created attachment 2004221 [details]
Update to 4.2.0b1 (#2249294)

Comment 4 Upstream Release Monitoring 2023-12-14 03:03:07 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=110309360

Comment 5 Upstream Release Monitoring 2024-01-18 06:09:48 UTC
Created attachment 2009094 [details]
Update to 4.2.0b1 (#2249294)

Comment 6 Upstream Release Monitoring 2024-01-18 06:26:42 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=111915349

Comment 7 Upstream Release Monitoring 2024-01-31 06:52:37 UTC
Created attachment 2014145 [details]
Update to 4.2.0b1 (#2249294)

Comment 8 Upstream Release Monitoring 2024-01-31 07:14:05 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=112644105

Comment 9 Upstream Release Monitoring 2024-02-10 12:55:45 UTC
Created attachment 2016195 [details]
Update to 4.2.0b1 (#2249294)

Comment 10 Upstream Release Monitoring 2024-02-10 13:10:19 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=113286201

Comment 11 Upstream Release Monitoring 2024-02-27 23:46:34 UTC
Created attachment 2019183 [details]
Update to 4.2.0b1 (#2249294)

Comment 12 Upstream Release Monitoring 2024-02-28 00:06:00 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.0b1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=114155959

Comment 13 Upstream Release Monitoring 2024-04-18 19:35:57 UTC
Releases retrieved: 4.2.1
Upstream release that is considered latest: 4.2.1
Current version/release in rawhide: 4.1.2-14.fc41
URL: http://www.mpich.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/8071/


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

Comment 14 Upstream Release Monitoring 2024-04-18 19:36:03 UTC
Created attachment 2027759 [details]
Update to 4.2.1 (#2249294)

Comment 15 Upstream Release Monitoring 2024-04-18 19:54:37 UTC
the-new-hotness/release-monitoring.org's scratch build of mpich-4.2.1-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=116569708

Comment 16 Fedora Update System 2024-04-19 07:07:47 UTC
FEDORA-2024-f0c9deff7a (mpich-4.2.1-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-f0c9deff7a

Comment 17 Fedora Update System 2024-04-19 07:12:26 UTC
FEDORA-2024-f0c9deff7a (mpich-4.2.1-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.