Latest upstream release: 1.2.1 Current version/release in rawhide: 1.2.0-3.fc36 URL: https://developers.yubico.com/pam-u2f/ 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/8511/
Scratch build failed. Details below: BuilderException: Build started, but failure happened during post build operations: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-9nozzv21/pam-u2f.spec']' returned non-zero exit status 1. StdOut: error: Bad source: ./pam_u2f-1.2.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
I'll take this ticket and work on getting 1.2.1 into rawhide as soon as yubico adds the sources (and the signature) to the yubico developers site (adding the sources/sigs to the developer site typically takes a few days).
FEDORA-2022-06b5b9b3be has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-06b5b9b3be
FEDORA-2022-06b5b9b3be has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report.