Fedora Account System
Red Hat Associate
Red Hat Customer
Releases retrieved: 1.5.2 Upstream release that is considered latest: 1.5.2 Current version/release in rawhide: 1.5.1-2.fc45 URL: https://github.com/opencontainers/runc 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/7462/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/runc
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-032qq18t/runc.spec']' returned non-zero exit status 1. StdOut: setting SOURCE_DATE_EPOCH=1790380800 error: Bad file: runc-1.5.2-vendor.tar.bz2: No such file or directory RPM build errors: Bad file: runc-1.5.2-vendor.tar.bz2: No such file or directory Traceback: File "/usr/local/lib/python3.14/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 55, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.14/site-packages/hotness/builders/koji.py", line 251, in build raise BuilderException( str(exc), value=output, std_out=std_out, std_err=std_err ) If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues
Created attachment 2158671 [details] Update to 1.5.2 (#2541782)
FEDORA-2026-2f2a69df1d (runc-1.5.2-3.fc45) has been submitted as an update to Fedora 45. https://bodhi.fedoraproject.org/updates/FEDORA-2026-2f2a69df1d
FEDORA-2026-359f6b58a4 (runc-1.5.2-3.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-359f6b58a4
FEDORA-2026-1028d3dfed (runc-1.5.2-3.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-1028d3dfed
FEDORA-2026-2f2a69df1d has been pushed to the Fedora 45 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-2f2a69df1d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-2f2a69df1d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-359f6b58a4 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-359f6b58a4` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-359f6b58a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-1028d3dfed has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-1028d3dfed` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-1028d3dfed See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-1028d3dfed (runc-1.5.2-3.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.