Description of problem:
Version of xl2tpd from epel-testing for EPEL7 will not install.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. yum --enablerepo=epel-testing update
---> Package xl2tpd.x86_64 0:1.3.6-8.el7 will be updated
---> Package xl2tpd.x86_64 0:1.3.8-1.el7 will be an update
--> Processing Dependency: kmod(l2tp_ppp.ko) for package: xl2tpd-1.3.8-1.el7.x86_64
--> Finished Dependency Resolution
Error: Package: xl2tpd-1.3.8-1.el7.x86_64 (epel-testing)
Should install cleanly
Paul: you fixed this before by removing that kmod requirement.
Note that the broken package is in the release "epel" repo, not just in "epel-testing", so production systems are seeing this as well.
FWIW, here's the changelog line Tuomo is referring to:
* Fri Oct 31 2014 Paul Wouters <email@example.com> - 1.3.6-7
- Remove kmod require, not recognised and l2tp_ppp.ko is in core kernel package now
Yes. This needs priority fixing without 2 weeks waiting time.
I am seeing this problem when trying to set up MATE on CentOS 7.
1. Install CentOS 7.3.1611 (Minimal)
2. Yum -y groupinstall “Development Tools”
3. Yum -y install epel-release
4. Yum -Y groupinstall “X Windows system”
5. Yum -Y groupinstall “MATE Desktop”
Getting this upgrading from CentOS 7.2 to 7.3. Same scenerio as Daniel above.
Steps to reproduce: yum upgrade
This breaks patching of boxes, and auto-patching, and as such the Severity should be at least Medium.
I tested the update and provided karma. It looks like more karma is required before it is pushed to the updates tree.
(In reply to Daniel Needles from comment #4)
> I am seeing this problem when trying to set up MATE on CentOS 7.
> To reproduce:
> 1. Install CentOS 7.3.1611 (Minimal)
> 2. Yum -y groupinstall “Development Tools”
> 3. Yum -y install epel-release
> 4. Yum -Y groupinstall “X Windows system”
> 5. Yum -Y groupinstall “MATE Desktop”
Changing my Epel repo to the testing branch let me install MATE.
Turn on :
yum-config-manager --enable epel-testing
Turn off :
yum-config-manager --disable epel-testing
Jim great workaround! I skipped the module but that was not ideal. In another note I think the "low" severity isn't warranted given the nature of the issue on EPEL production. In most environments I've been in they would have rolled back the original change immediately rather than wait over a week for a patch.
The build mentioned in comment 8 has fixed the problem so please consider closing this bug report.
Fixed version has been available for some time.