Description of problem: # yum check-update Loaded plugins: changelog, downloadonly, presto, refresh-packagekit, rhnplugin, : security, tmprepo, verify, versionlock This system is receiving updates from RHN Classic or RHN Satellite. Obsoleting Packages libreswan.x86_64 3.7-1.el6 epel openswan.x86_64 2.6.32-27.el6 @rhel-x86_64-workstation-6 Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: EPEL packages should not remove or obsolete base RHEL packages. Quoting from the EPEL policy: "EPEL packages should only enhance and never disturb the Enterprise Linux distributions they were build for. Thus packages from EPEL should never replace packages from the target base distribution - including those on the base distribution as well as layered products; kernel-modules further are not allowed, as they can disturb the base kernel easily." Additional info:
This is a bit of a special case. A lawsuit required the opensource project to rename itself from openswan to libreswan. The old openswan codebase has more or less been unmaintained for two years as the company that started the lawsuit aliented all developers away with the lawsuit. The only changes upstream has made has been our work at backporting libreswan patches to openswan for RHEL. Red Hat still maintains openswan for RHEL5/6, but for RHEL 7, it has already switched to libreswan instead of openswan. and people upgrading from RHEL6 to RHEL7 will automatically get migrated from openswan to libreswan.
Thanks for the background information Paul. I still don't see what justifies replacing a supported base RHEL package with an unsupported newer version from EPEL. Red Hat should rebase it in RHEL5/6 if that is what it wants to do. But EPEL should not replace supported packages with unsupported packages. That is one of the big selling points of using EPEL.
I will fix it in the next build, scheduled for this friday
https://bugzilla.redhat.com/show_bug.cgi?id=922438#c5
libreswan-3.8-1.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/libreswan-3.8-1.el6
Package libreswan-3.8-1.el6: * should fix your issue, * was pushed to the Fedora EPEL 6 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=epel-testing libreswan-3.8-1.el6' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-EPEL-2014-0233/libreswan-3.8-1.el6 then log in and leave karma (feedback).
libreswan-3.8-1.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.