Bug 2310544

Summary: binaryen-120_b is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: binaryenAssignee: Dominik 'Rathann' Mierzejewski <dominik>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: dominik
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: binaryen-120-1.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-11 02:20:06 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 119 (#2310544)
none
Update to 120 (#2310544)
none
Update to 120_b (#2310544) none

Description Upstream Release Monitoring 2024-09-07 00:47:52 UTC
Releases retrieved: 119
Upstream release that is considered latest: 119
Current version/release in rawhide: 118-1.fc41
URL: https://github.com/WebAssembly/binaryen

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


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

Comment 1 Upstream Release Monitoring 2024-09-07 00:47:57 UTC
Created attachment 2045649 [details]
Update to 119 (#2310544)

Comment 2 Upstream Release Monitoring 2024-09-07 01:10:04 UTC
the-new-hotness/release-monitoring.org's scratch build of binaryen-119-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=123040619

Comment 3 Upstream Release Monitoring 2024-10-27 04:43:24 UTC
Releases retrieved: 120
Upstream release that is considered latest: 120
Current version/release in rawhide: 118-1.fc41
URL: https://github.com/WebAssembly/binaryen

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


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

Comment 4 Upstream Release Monitoring 2024-10-27 04:43:30 UTC
Created attachment 2053925 [details]
Update to 120 (#2310544)

Comment 5 Upstream Release Monitoring 2024-10-27 05:09:15 UTC
the-new-hotness/release-monitoring.org's scratch build of binaryen-120-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=125244824

Comment 6 Upstream Release Monitoring 2024-10-29 00:47:35 UTC
Releases retrieved: 120_b
Upstream release that is considered latest: 120_b
Current version/release in rawhide: 118-1.fc41
URL: https://github.com/WebAssembly/binaryen

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


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

Comment 7 Upstream Release Monitoring 2024-10-29 00:47:39 UTC
Created attachment 2054148 [details]
Update to 120_b (#2310544)

Comment 8 Upstream Release Monitoring 2024-10-29 01:11:29 UTC
the-new-hotness/release-monitoring.org's scratch build of binaryen-120_b-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=125304994

Comment 9 Fedora Update System 2024-11-02 22:49:18 UTC
FEDORA-2024-9d2f5f40fe (binaryen-120-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-9d2f5f40fe

Comment 10 Fedora Update System 2024-11-03 03:31:57 UTC
FEDORA-2024-9d2f5f40fe has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9d2f5f40fe`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9d2f5f40fe

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

Comment 11 Fedora Update System 2024-11-11 02:20:06 UTC
FEDORA-2024-9d2f5f40fe (binaryen-120-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.