Bug 2269341
Summary: | package violates EPEL policy | ||
---|---|---|---|
Product: | [Fedora] Fedora EPEL | Reporter: | bernhard.furtmueller |
Component: | librdkafka | Assignee: | Attila Lakatos <alakatos> |
Status: | MODIFIED --- | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | epel7 | CC: | alakatos, rsroka, zfridric |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 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: |
Description
bernhard.furtmueller
2024-03-13 08:54:53 UTC
I am not sure what the ideal solution would look like. Do we need to retire the package from EPEL repo? I know complex, especially at this point of the RHEL7 lifecycle. From a EPEL policy point it is pretty clear (at least from my naive point of view) -> retire. But I guess the requester didn't roll the package just for fun and likely he (and we?) would like to see the .5 changes/enhancement in RHEL7 anyway (not likely to happen - and I didn't look into details what actually changed). Is providing the complete consistent set librdkafka{,-devel}.{x86_64,i686} from EPEL an option? The mixture is actually why we noticed it at all - and yes we're currently on i686 and x86_64 (working towards 64bit only on RHEL8) I followed the Fedora/EPEL package removal guide and retired librdkafka from EPEL7 with the following steps [1]: - executed fedpkg retire "Remove librdkafka from EPEL 7, as it is available in RHEL-7, otherwise package violates EPEL policy." - check if the package is listed in the comps. it's not listed there. - check if the package is part of the spin kickstart file. it's not listed there. - to keep retired packages from being pushed to the mirrors, they need to be blocked in Koji. This is not done yet. Will need to wait for automation to kick in. [1] https://docs.fedoraproject.org/en-US/package-maintainers/Package_Retirement_Process/#epel::epel-policy-retirement.adoc/ [2] https://src.fedoraproject.org/rpms/librdkafka/tree/epel7 |