Hello,
Newely i setup my new dedicated server on hetzner.
i installed centos 7 from their installimage system.
then i converted Centos 7 to cloudlinux and finaly Install cPanel.
after i did run "yum update"
now , when i check my enabled repolist i see that EPEL repo is enable by default in OS Installation package, and now some package installed or updated with EPEL repo :
yum list installed | grep @epel
GraphicsMagick.x86_64 1.3.31-2.el7 @epel
atop.x86_64 2.4.0-1.el7 @epel
epel-release.noarch 7-11 @epel
firebird.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-filesystem.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-libfbclient.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-libfbembed.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-superserver.x86_64 2.5.8.27089.0-1.el7 @epel
haveged.x86_64 1.9.1-1.el7 @epel
hdf5.x86_64 1.8.12-10.el7 @epel
libaec.x86_64 1.0.4-1.el7 @epel
libargon2.x86_64 20161029-3.el7 @epel
libc-client.x86_64 2007f-16.el7 @epel
libnghttp2.x86_64 1.31.1-1.el7 @epel
libsodium.x86_64 1.0.17-1.el7 @epel
mhash.x86_64 0.9.9.9-10.el7 @epel
nethogs.x86_64 0.8.5-1.el7 @epel
python2-simplejson.x86_64 3.10.0-2.el7 @epel
above packages installed/updated with EPEL Repo insted of cloudlinux.
is there any problem ?
if i disable EPEL Repo now , this packages can update with cloudlinux /cpanel repo in the future ?
the version of this packages are newer than cloudlinux repo.
is it safe to disable EPEL repo now in attention this packages are installed from EPEL repo now ?
please help me how i can fix this problem and avoid package update conflict
Best Regards
Newely i setup my new dedicated server on hetzner.
i installed centos 7 from their installimage system.
then i converted Centos 7 to cloudlinux and finaly Install cPanel.
after i did run "yum update"
now , when i check my enabled repolist i see that EPEL repo is enable by default in OS Installation package, and now some package installed or updated with EPEL repo :
yum list installed | grep @epel
GraphicsMagick.x86_64 1.3.31-2.el7 @epel
atop.x86_64 2.4.0-1.el7 @epel
epel-release.noarch 7-11 @epel
firebird.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-filesystem.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-libfbclient.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-libfbembed.x86_64 2.5.8.27089.0-1.el7 @epel
firebird-superserver.x86_64 2.5.8.27089.0-1.el7 @epel
haveged.x86_64 1.9.1-1.el7 @epel
hdf5.x86_64 1.8.12-10.el7 @epel
libaec.x86_64 1.0.4-1.el7 @epel
libargon2.x86_64 20161029-3.el7 @epel
libc-client.x86_64 2007f-16.el7 @epel
libnghttp2.x86_64 1.31.1-1.el7 @epel
libsodium.x86_64 1.0.17-1.el7 @epel
mhash.x86_64 0.9.9.9-10.el7 @epel
nethogs.x86_64 0.8.5-1.el7 @epel
python2-simplejson.x86_64 3.10.0-2.el7 @epel
above packages installed/updated with EPEL Repo insted of cloudlinux.
is there any problem ?
if i disable EPEL Repo now , this packages can update with cloudlinux /cpanel repo in the future ?
the version of this packages are newer than cloudlinux repo.
is it safe to disable EPEL repo now in attention this packages are installed from EPEL repo now ?
please help me how i can fix this problem and avoid package update conflict
Best Regards