Update to proftpd fails when using Webmin update

I’ve had an update for proftpd that I haven’t been able to install for a while now. Here’s the output I get when I try to run it:

Now updating proftpd ..
Installing package(s) with command yum -y install proftpd ..
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: p3plmirror01.prod.phx3.secureserver.net
 * epel: dl.fedoraproject.org
 * extras: p3plmirror01.prod.phx3.secureserver.net
 * updates: p3plmirror01.prod.phx3.secureserver.net
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package proftpd.x86_64 0:1.3.3g-3.el6 will be updated
---> Package proftpd.x86_64 0:1.3.3g-4.el6 will be an update
--> Processing Dependency: libssl.so.10(libssl.so.10)(64bit) for package: proftpd-1.3.3g-4.el6.x86_64
--> Processing Dependency: libcrypto.so.10(libcrypto.so.10)(64bit) for package: proftpd-1.3.3g-4.el6.x86_64
--> Processing Dependency: libcrypto.so.10(OPENSSL_1.0.1)(64bit) for package: proftpd-1.3.3g-4.el6.x86_64
--> Finished Dependency Resolution
Error: Package: proftpd-1.3.3g-4.el6.x86_64 (epel)
           Requires: libcrypto.so.10(libcrypto.so.10)(64bit)
Error: Package: proftpd-1.3.3g-4.el6.x86_64 (epel)
           Requires: libcrypto.so.10(OPENSSL_1.0.1)(64bit)
Error: Package: proftpd-1.3.3g-4.el6.x86_64 (epel)
           Requires: libssl.so.10(libssl.so.10)(64bit)
 You could try using --skip-broken to work around the problem
 You could try running: rpm -Va --nofiles --nodigest
.. install failed!

No packages were installed. Check the messages above for the cause of the error.

I’ve run the commands suggested from the command line connected by ssh and they haven’t fixed anything. I can’t figure out how to fix this dependency issue. Any suggestions would be appreciated. I’ve had other updates that go through normally, so this is sort of a one-off issue as far as I can tell.

Howdy,

Hmm, it appears to be trying to pull in that package from the EPEL repo, which is a third party repo.

My suggestion would be to try disabling that repository, and then attempt performing the updates again and see if they work properly.

-Eric