Any issues with EPEL repo?

Is there an update for this now that 72 is out? Is there any way to track it besides watching this forum thread?

 

With cloudlinux+cPanel I disable EPEL because packages can be mixed between them.

 

You could always install the EPEL repo and then disable the various EPEL repo options after it is installed -- so that it is never used for an update. Then, if/when you want to install something that is only in the EPEL repo, you can enable the part of the repo that you want long enough to do a 'yum install packagename'. This should work well -- but be cautious. If a particular package you are installing has dependencies that aren't already installed and it tries to use the EPEL repo to install those dependencies, that could present an issue if other, more important, repos that you use regularly have the same files.

I don't recall if the EPEL and EPEL-Testing repos are two different repos or not. I don't have any installed on my cPanel boxes. But on my billing system I have both installed.

And in /etc/yum.repos.d/epel.repo and /etc/yum.repos.d/epel-testing.repo I have all of the "enabled=" lines set to:

enabled=0

So the nothing will ever update via the EPEL repos without my knowledge. If I want to update/install something from the repo, I have to enable the portion of the repo that has that package or specify the specific repo when updating.

I'll then do something like:

yum install <packagename> --enablerepo=epel or yum update <packagename> --enablerepo=epel

That'll enable it long enough to install/update the specific package(s) that I am trying to update but will leave the repo disabled for any automatic processing (assuming you have all of the enabled= in the repo files set to enabled=0).

Again I caution about anything requiring dependencies to be installed that aren't already installed though, as ideally if you install a package from EPEL that has dependencies, you probably want those dependencies installed from your existing main repos (if they have those dependencies available) rather than from EPEL. You want to avoid at all cost having EPEL packages installed for dependencies when those same packages are already available in the primary repos. And if a dependency package is already installed but a newer version is available [only] in the EPEL repo, think long and hard before installing that dependency.

Mike