<div dir="ltr"><div dir="ltr">As a CentOS user and running into the problem a couple of times... I have resorted to doing either one of the following:<div><br></div><div>* No longer doing yum-cron or automated updates while having elrepo in play.</div><div><br></div><div>This makes it so I have to do it manually or have the GUI desktop nag me to look at what updates are available and only apply what I think are necessary at the time.</div><div><br></div><div>* Make use of yum versionlock.</div><div><br></div><div>Yum has a version lock plugin. See: <a href="https://www.cyberciti.biz/faq/centos-redhat-fedora-yum-lock-package-version-command/">https://www.cyberciti.biz/faq/centos-redhat-fedora-yum-lock-package-version-command/</a></div><div><br></div><div>Where I work, which is a University, our labs sometimes have some services that are only at a certain level due to manpower not being able to reconfigure or port over older stuff to the newer standards. CFEngine being an example.</div><div><br></div><div>Versionlock had to be in place to prevent the installing of CFEngine 3.0 over the CFEngine 2.0 that was in place on some of the newer systems. So you can make use of versionlock for those situations and unlock it when you feel you can use a newer version.<br><br><div class="gmail_quote"><div dir="ltr"><br></div></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><span><font color="#888888">Scott Kasai<br>
College of Engineering<br>
Engineering Computing Infrastructure<br>
University of California Santa Barbara<br>
Email: <a href="mailto:kasai@engineering.ucsb.edu" target="_blank">kasai@engineering.ucsb.edu</a><br>
</font></span></div></div></div></div></div></div></div>