update rpm package

solidsnake

Member
Joined
Oct 6, 2021
Messages
44
Reaction score
2
Credits
592
I need to update the packages for security reasons. When I do yum update I get these as the latest packages but I can see more recent ones in the link.

[root@ol79_testserver yum.repos.d]# rpm -qa |grep qemu
qemu-img-1.5.3-175.el7_9.6.x86_64
qemu-kvm-1.5.3-175.el7_9.6.x86_64
libvirt-daemon-driver-qemu-4.5.0-36.el7_9.5.x86_64
ipxe-roms-qemu-20180825-3.git133f4c.el7.noarch
qemu-kvm-common-1.5.3-175.el7_9.6.x86_64
qemu-guest-agent-2.12.0-3.el7.x86_64

I added this but it still hasn't updated the packages

[ol7_latest]
name=Oracle Linux $releasever Latest ($basearch)
##baseurl=https://yum$ociregion.$ocidomain/repo/OracleLinux/OL7/latest/$basearch/
baseurl=https://yum.oracle.com/repo/OracleLinux/OL7/developer/kvm/utils/x86_64
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-oracle
gpgcheck=1
enabled=1
 


I need to update the packages for security reasons.
For security reason you need to also update to a supported version of RHEL/OL, RHEL7/OL7 is EOL. It doesn't sound anymore secure to be updating packages from a "developer" repo.

Clean your yum cache.
Code:
yum clean all
Then when you try and update it should refresh your yum cache before it starts updating the packages.
 
For security reason you need to also update to a supported version of RHEL/OL, RHEL7/OL7 is EOL. It doesn't sound anymore secure to be updating packages from a "developer" repo.

Clean your yum cache.
Code:
yum clean all
Then when you try and update it should refresh your yum cache before it starts updating the packages.
but this time I started getting this error

Loaded plugins: langpacks, ulninfo
https://yum.oracle.com/repo/OracleLinux/OL7/UEKR6/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: yum.oracle.com; Unknown error"
Trying other mirror.


One of the configured repositories failed (Latest Unbreakable Enterprise Kernel Release 6 for Oracle Linux 7Server (x86_64)),
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:

1. Contact the upstream for the repository and get them to fix the problem.

2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).

3. Run the command with the repository temporarily disabled
yum --disablerepo=ol7_UEKR6 ...

4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:

yum-config-manager --disable ol7_UEKR6
or
subscription-manager repos --disable=ol7_UEKR6

5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:

yum-config-manager --save --setopt=ol7_UEKR6.skip_if_unavailable=true

failure: repodata/repomd.xml from ol7_UEKR6: [Errno 256] No more mirrors to try.
https://yum.oracle.com/repo/OracleLinux/OL7/UEKR6/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: yum.oracle.com; Unknown error"


EDIT: delete resolv.conf , problem solved
 
Last edited:
@f33dm3bits is right. It's out of support. No more updates. It's done.

failure: repodata/repomd.xml from ol7_UEKR6: [Errno 256] No more mirrors to try.
https://yum.oracle.com/repo/OracleLinux/OL7/UEKR6/x86_64/repodata/repomd.xml: [Errno 14] curl#6 - "Could not resolve host: yum.oracle.com; Unknown error"

The reason it's unresolvable is that almost all of these have been shut down and taken offline.
Unless you're paying for a very expensive custom extended support program, which only has a few private
repo's ( not accessible by the general public, nor by "standard subscription" ) available.

You need to update to Oracle 8, or better yet, Oracle 9.

 
I was able to get this to work, on an old system I had to restart.
I would find that odd that you have to restart to refresh the cache.
 

Staff online


Top