Bug 2276827
Summary: | container-selinux-2.231.0 is available | ||||||
---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
Component: | container-selinux | Assignee: | Daniel Walsh <dwalsh> | ||||
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
Severity: | unspecified | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | rawhide | CC: | amurdaca, dwalsh, dweomer5, jchaloup, lsm5, pehunt | ||||
Target Milestone: | --- | Keywords: | FutureFeature, Triaged | ||||
Target Release: | --- | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | container-selinux-2.231.0-1.fc41 container-selinux-2.231.0-1.fc38 container-selinux-2.231.0-1.fc39 container-selinux-2.231.0-1.fc40 | Doc Type: | --- | ||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2024-04-24 16:33:15 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-04-24 06:29:18 UTC
Scratch build failed. Details below: BuilderException: Build failed: Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-f2p_ytt3/container-selinux.spec']' returned non-zero exit status 1. StdOut: warning: line 46: Possible unexpanded macro in: BuildRequires: selinux-policy >= %_selinux_policy_version warning: line 47: Possible unexpanded macro in: BuildRequires: selinux-policy-devel >= %_selinux_policy_version warning: line 49: Possible unexpanded macro in: Requires: selinux-policy >= %_selinux_policy_version warning: line 50: Possible unexpanded macro in: Requires(post): selinux-policy-base >= %_selinux_policy_version warning: line 51: Possible unexpanded macro in: Requires(post): selinux-policy-targeted >= %_selinux_policy_version setting SOURCE_DATE_EPOCH=1713916800 error: Bad file: ./v2.231.0.tar.gz: No such file or directory RPM build warnings: line 46: Possible unexpanded macro in: BuildRequires: selinux-policy >= %_selinux_policy_version line 47: Possible unexpanded macro in: BuildRequires: selinux-policy-devel >= %_selinux_policy_version line 49: Possible unexpanded macro in: Requires: selinux-policy >= %_selinux_policy_version line 50: Possible unexpanded macro in: Requires(post): selinux-policy-base >= %_selinux_policy_version line 51: Possible unexpanded macro in: Requires(post): selinux-policy-targeted >= %_selinux_policy_version RPM build errors: Bad file: ./v2.231.0.tar.gz: No such file or directory Traceback: File "/usr/local/lib/python3.11/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.11/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 2028725 [details]
Update to 2.231.0 (#2276827)
FEDORA-2024-5d7a15cb60 (container-selinux-2.231.0-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2024-5d7a15cb60 FEDORA-2024-9c7117c946 (container-selinux-2.231.0-1.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-9c7117c946 FEDORA-2024-643acecf77 (container-selinux-2.231.0-1.fc38) has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2024-643acecf77 FEDORA-2024-50122b25a1 (container-selinux-2.231.0-1.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-50122b25a1 FEDORA-2024-5d7a15cb60 (container-selinux-2.231.0-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-9c7117c946 has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-9c7117c946` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-9c7117c946 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-50122b25a1 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-50122b25a1` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-50122b25a1 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-643acecf77 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-643acecf77` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-643acecf77 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-643acecf77 (container-selinux-2.231.0-1.fc38) has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-50122b25a1 (container-selinux-2.231.0-1.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-9c7117c946 (container-selinux-2.231.0-1.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. |