The releases of RHEL and CentOS 7.5 (and likely earlier versions) brought with them new packages that were previously provided by EPEL7. Some of these are still present in EPEL, potentially causing conflicts. Particularly problematic are various packages that are provided in EPEL as python2-* and provided in upstream as python-*. While fully-overlapping names are suboptimal, these partially-overlapping names that provide the same actual package leads to issues like certbot issue 6314 and RHBZ #1578071. These packages should be replaced with dummy packages that have requirements on python-*.
I have attached 4 files containing lists of problematic packages:
Note that some of the packages listed in these files may have been removed from EPEL since I generated the lists.
No specific date, but sooner is better.
N/A
EPEL-provided packages with full name overlap may potentially override upstream packages. EPEL-provided packages with partial name overlap may cause issues like certbot issue 6314 and RHBZ #1578071.
Metadata Update from @mohanboddu: - Issue tagged with: meeting
base-and-updates-partial.txt doesn't seem to load?
Some of these are definitely not for removal... ansible was dropped from extras, the pidgin packages I think we added because RHEL dropped an api other packages needed, and some are likely limited arch packages. We just have to sort out which of these matter...
Perhaps we could look at the ones causing issues first?
That's frustrating. I appear to have deleted it from my local system. I'll regenerate it and post it shortly.
The ones causing issues are primarily the ones in base-and-updates-partial.txt and extras-partial.txt.
Expanded into a comment, the package conflicts from base/updates that are most likely to cause issues are:
The conflicts from extras that are most likely to cause issues are:
The issues I linked in the description indicate that the following packages in particular are known to cause issues:
Overlap of libdnet packages is in accordance with https://fedoraproject.org/wiki/EPEL:Packaging#Limited_Arch_Packages
libdnet
@elyscape , is this still an issue?
@elyscape What are the exact packages in EPEL7 that are causing problems?
Closing ticket since nothing heard. Please reopen if this remains an issue.
Metadata Update from @syeghiay: - Issue close_status updated to: Insufficient data - Issue status updated to: Closed (was: Open)