Bug 2309626
| Summary: | sudo-1_9_16p2 is available | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||||||
| Component: | sudo | Assignee: | Radovan Sroka <rsroka> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | unspecified | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | rawhide | CC: | alakatos, kzak, mattdm, rsroka, zfridric | ||||||||
| Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | sudo-1.9.17-2.p1.fc43 sudo-1.9.17-2.p1.fc42 sudo-1.9.17-2.p1.fc41 | Doc Type: | --- | ||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2025-07-05 11:17:32 UTC | Type: | --- | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Upstream Release Monitoring
2024-09-04 06:02:27 UTC
Scratch build failed. Details below:
BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-2orzdgq7/sudo.spec']' returned non-zero exit status 1.
StdOut:
setting SOURCE_DATE_EPOCH=1725408000
error: Bad file: ./sudo-1_9_16p5.tar.gz: No such file or directory
RPM build errors:
Bad file: ./sudo-1_9_16p5.tar.gz: No such file or directory
Traceback:
File "/usr/local/lib/python3.12/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.12/site-packages/hotness/builders/koji.py", line 229, 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
Created attachment 2045382 [details]
Update to 1_9_16 (#2309626)
Releases retrieved: 1_9_16p1 Upstream release that is considered latest: 1_9_16p1 Current version/release in rawhide: 1.9.15-5.p5.fc41 URL: https://www.sudo.ws 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/4906/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/sudo Scratch build failed. Details below:
BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-uyh6ydv2/sudo.spec']' returned non-zero exit status 1.
StdOut:
setting SOURCE_DATE_EPOCH=1731456000
error: Bad file: ./sudo-1_9_16p1p5.tar.gz: No such file or directory
RPM build errors:
Bad file: ./sudo-1_9_16p1p5.tar.gz: No such file or directory
Traceback:
File "/usr/local/lib/python3.12/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.12/site-packages/hotness/builders/koji.py", line 229, 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
Created attachment 2057421 [details]
Update to 1_9_16p1 (#2309626)
Releases retrieved: 1_9_16p2 Upstream release that is considered latest: 1_9_16p2 Current version/release in rawhide: 1.9.15-5.p5.fc41 URL: https://www.sudo.ws 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/4906/ To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/sudo Scratch build failed. Details below:
BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-lxb39zq4/sudo.spec']' returned non-zero exit status 1.
StdOut:
setting SOURCE_DATE_EPOCH=1732492800
error: Bad file: ./sudo-1_9_16p2p5.tar.gz: No such file or directory
RPM build errors:
Bad file: ./sudo-1_9_16p2p5.tar.gz: No such file or directory
Traceback:
File "/usr/local/lib/python3.12/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.12/site-packages/hotness/builders/koji.py", line 229, 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
Created attachment 2059777 [details]
Update to 1_9_16p2 (#2309626)
FEDORA-2025-85dcd8206f (sudo-1.9.17-2.p1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2025-85dcd8206f FEDORA-2025-44c3b13554 (sudo-1.9.17-2.p1.fc42) has been submitted as an update to Fedora 42. https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c3b13554 FEDORA-2025-29c6186ffb (sudo-1.9.17-2.p1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-29c6186ffb FEDORA-2025-85dcd8206f (sudo-1.9.17-2.p1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-44c3b13554 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-44c3b13554` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-44c3b13554 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-29c6186ffb has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-29c6186ffb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-29c6186ffb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2025-44c3b13554 (sudo-1.9.17-2.p1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2025-29c6186ffb (sudo-1.9.17-2.p1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. |