Hide Forgot
Latest upstream release: 1.1.1 Current version/release in rawhide: 1.0.32-5.fc35 URL: http://www.sane-project.org/ 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/4760/
Scratch build failed. Details bellow: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-628m7jk_/sane-backends.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./sane-backends-1.1.1.tar.gz: No such file or directory 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 188, 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
(In reply to Upstream Release Monitoring from comment #0) > Latest upstream release: 1.1.1 > Current version/release in rawhide: 1.0.32-5.fc35 > URL: http://www.sane-project.org/ > Based on the information from Anitya: https://release-monitoring.org/project/4760/ SANE Backends 1.1.1 released: https://alioth-lists.debian.net/pipermail/sane-devel/2022-January/039340.html Changelog: https://gitlab.com/sane-project/backends/-/releases/1.1.1
FEDORA-2022-8888a6ae8f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-8888a6ae8f
FEDORA-2022-4b7b560c22 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-4b7b560c22
FEDORA-2022-4b7b560c22 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-4b7b560c22` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-4b7b560c22 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-8888a6ae8f 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-8888a6ae8f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-8888a6ae8f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-8888a6ae8f has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2022-2667d76e7f 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-2667d76e7f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-2667d76e7f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-2667d76e7f has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.