Bug 2360486
| Summary: | selinux-policy-epel: add to EPEL 10.0 | ||
|---|---|---|---|
| Product: | [Fedora] Fedora EPEL | Reporter: | Carl George 🤠<carl> |
| Component: | selinux-policy-epel | Assignee: | Petr Lautrbach <plautrba> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | epel10 | CC: | mmalik, plautrba, vmojzis, zpytela |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | selinux-policy-epel-40.13.28-2.el10_0 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2025-04-25 04:18:00 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
FEDORA-EPEL-2025-4fd099f8a4 (selinux-policy-epel-40.13.28-2.el10_0) has been submitted as an update to Fedora EPEL 10.0. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-4fd099f8a4 FEDORA-EPEL-2025-4fd099f8a4 has been pushed to the Fedora EPEL 10.0 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-4fd099f8a4 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-EPEL-2025-4fd099f8a4 (selinux-policy-epel-40.13.28-2.el10_0) has been pushed to the Fedora EPEL 10.0 stable repository. If problem still persists, please make note of it in this bug report. |
Description of problem: Please add selinux-policy-epel to EPEL 10.0. It is available for 10.1, but it was built after the 10.0 mass branching and thus needs to also be built for 10.0. Additional info: The process for this is similar to building for a Fedora release after the mass branching. First you request the epel10.0 branch, then create a build from that branch, and then submit it as an update in bodhi. If you're busy I can take care of the build+update as a proven packager, I just can't request the epel10.0 branch because only maintainers of package can do that. fedpkg request-branch epel10.0