Bug 2316285

Summary: rust-run_script-0.11.0 is available
Product: [Fedora] Fedora Reporter: Upstream Release Monitoring <upstream-release-monitoring>
Component: rust-run_scriptAssignee: Michel Lind <michel>
Status: CLOSED ERRATA QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: michel, rust-sig
Target Milestone: ---Keywords: FutureFeature, Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rust-run_script-0.11.0-1.fc42 rust-run_script-0.11.0-1.fc39 rust-run_script-0.11.0-1.el9 rust-run_script-0.11.0-1.fc40 rust-run_script-0.11.0-1.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-11-13 23:29: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:

Description Upstream Release Monitoring 2024-10-03 13:44:21 UTC
Releases retrieved: 0.11.0
Upstream release that is considered latest: 0.11.0
Current version/release in rawhide: 0.10.1-3.fc41
URL: https://crates.io/crates/run_script

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


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

Comment 1 Fedora Update System 2024-11-13 21:32:26 UTC
FEDORA-2024-2019dd2571 (rust-run_script-0.11.0-1.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2019dd2571

Comment 2 Fedora Update System 2024-11-13 23:28:20 UTC
FEDORA-2024-e91dc35e00 (rust-run_script-0.11.0-1.fc39) has been submitted as an update to Fedora 39.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-e91dc35e00

Comment 3 Fedora Update System 2024-11-13 23:28:21 UTC
FEDORA-2024-b96d5b8e1e (rust-run_script-0.11.0-1.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-b96d5b8e1e

Comment 4 Fedora Update System 2024-11-13 23:28:21 UTC
FEDORA-2024-2e681ee5a8 (rust-run_script-0.11.0-1.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-2e681ee5a8

Comment 5 Fedora Update System 2024-11-13 23:28:22 UTC
FEDORA-EPEL-2024-808c13e4e3 (rust-run_script-0.11.0-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-808c13e4e3

Comment 6 Fedora Update System 2024-11-13 23:29:26 UTC
FEDORA-2024-2019dd2571 (rust-run_script-0.11.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 7 Fedora Update System 2024-11-14 02:14:16 UTC
FEDORA-2024-b96d5b8e1e 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-b96d5b8e1e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-b96d5b8e1e

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

Comment 8 Fedora Update System 2024-11-14 03:08:35 UTC
FEDORA-EPEL-2024-808c13e4e3 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-808c13e4e3

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

Comment 9 Fedora Update System 2024-11-14 03:32:28 UTC
FEDORA-2024-2e681ee5a8 has been pushed to the Fedora 40 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-2e681ee5a8`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-2e681ee5a8

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

Comment 10 Fedora Update System 2024-11-14 06:06:04 UTC
FEDORA-2024-e91dc35e00 has been pushed to the Fedora 39 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-e91dc35e00`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-e91dc35e00

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

Comment 11 Fedora Update System 2024-11-22 02:09:45 UTC
FEDORA-2024-e91dc35e00 (rust-run_script-0.11.0-1.fc39) has been pushed to the Fedora 39 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2024-11-22 02:39:45 UTC
FEDORA-EPEL-2024-808c13e4e3 (rust-run_script-0.11.0-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2024-11-22 03:21:11 UTC
FEDORA-2024-2e681ee5a8 (rust-run_script-0.11.0-1.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2024-11-22 03:21:18 UTC
FEDORA-2024-b96d5b8e1e (rust-run_script-0.11.0-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.