Latest upstream release: 2.0.1 Current version/release in rawhide: 2.0.0-2.fc36 URL: http://www.breakfastquay.com/rubberband/ 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/4222/
Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['git', 'commit', '-a', '-m', 'Update to 2.0.1 (#2042916)']' 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 rubberband-2.0.0-1.fc34.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=81515911
FEDORA-2022-40da1fac97 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-40da1fac97
FEDORA-2022-07a2d55dc6 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-07a2d55dc6
FEDORA-EPEL-2022-32b2f2926f has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-32b2f2926f
FEDORA-2022-40da1fac97 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-40da1fac97` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-40da1fac97 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2022-32b2f2926f 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-2022-32b2f2926f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-07a2d55dc6 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 --advisory=FEDORA-2022-07a2d55dc6` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-07a2d55dc6 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-07a2d55dc6 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2022-32b2f2926f has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-40da1fac97 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.