![]() ![]() If versionlock is the only option, is there an easy way to generate a versionlock list for 7.3 and 7. update runs the yum update command, which, in this case, downloads the updated RPMs from the repositories as configured. Is there a way to "yum update" 7.3 and 7.4 servers from the above repositories without ending up with 7.5? Yum -releasever=7.3 and distroverpkg=redhat-release in /etc/yum.conf do not appear to work without subscribtion-manager. ![]() If you exclude the bad architecture yum will tell you what the root cause is (which package requires what). Yum is trying to solve this by installing an older version of nss-softokn-freebl of the different architecture. Servers have to be running specific releases for application compatibility. You have an upgrade for nss-softokn-freebl which is missing some dependency that another package requires. On CentOS 7: sudo yum clean all & sudo yum. ![]() The repositories were created (from a machine with Internet access) using commands similar to these: reposync -downloadcomps -download-metadata -arch=x86_64 -repoid=rhel-7-server-rpms -delete -download_path=/var/repos/7/Ĭreaterepo -s sha256 -checkts -update -workers=2 -g /var/repos/7/rhel-7-server-rpms/comps.xml /var/repos/7/rhel-7-server-rpmsĭid not pass newest-only to reposync because I want to use the repository for servers running RHEL 7.3 and 7.4. Install other dependencies required to build and run Asterisk 18 LTS on CentOS 7. For some reason it sends commands early, during the yum update. We maintain local RHEL repositories because there is no Internet access in the data center. It performs a variety of tasks, all of which it completes fine except for the yum updates.
0 Comments
Leave a Reply. |