Latest upstream release: 1.0.3 Current version/release in rawhide: 1.0.2-1.fc36 URL: https://github.com/containerd/cgroups 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://fedoraproject.org/wiki/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/205145/
Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['git', 'commit', '-a', '-m', 'Update to 1.0.3 (#2049984)']' returned non-zero exit status 1. StdOut: On branch rawhide Your branch is up to date with 'origin/rawhide'. Untracked files: (use "git add <file>..." to include in what will be committed) SRPMS/ nothing added to commit but untracked files present (use "git add" to track) Traceback: File "/usr/local/lib/python3.9/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build result = self.builder.build(request.package, request.opts) File "/usr/local/lib/python3.9/site-packages/hotness/builders/koji.py", line 226, in build raise BuilderException( 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
the-new-hotness/release-monitoring.org's scratch build of golang-github-containerd-cgroups-1.0.2-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=82314266
FEDORA-2022-f47a7a5e14 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2022-f47a7a5e14
FEDORA-2022-f47a7a5e14 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-5af6281318 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5af6281318
FEDORA-2022-5af6281318 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-81fac5ebe2 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-81fac5ebe2
FEDORA-2022-98ac291db8 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-98ac291db8
FEDORA-2022-81fac5ebe2 has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-81fac5ebe2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-81fac5ebe2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-98ac291db8 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2022-98ac291db8` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-98ac291db8 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-81fac5ebe2 has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-98ac291db8 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.