VirtualBox

Opened 8 years ago

Closed 7 years ago

Last modified 7 years ago

#15426 closed defect (obsolete)

repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox

Reported by: FP Owned by:
Component: other Version: VirtualBox 5.0.20
Keywords: gpg install centos Cc:
Guest type: other Host type: Linux

Description

Installing VirtualBox through the https://wiki.centos.org/HowTos/Virtualization/VirtualBox howto guide on a fresh CentOS 7.x 64bit install returns the following:

[root@cloudtest yum.repos.d]# yum install VirtualBox
Loaded plugins: fastestmirror
base                                                                                                                                                                       | 3.6 kB  00:00:00
extras                                                                                                                                                                     | 3.4 kB  00:00:00
rpmforge                                                                                                                                                                   | 1.9 kB  00:00:00
updates                                                                                                                                                                    | 3.4 kB  00:00:00
virtualbox/7/x86_64/signature                                                                                                                                              |  198 B  00:00:00
Retrieving key from https://www.virtualbox.org/download/oracle_vbox.asc
virtualbox/7/x86_64/signature                                                                                                                                              |  951 B  00:00:00 !!!
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox
Trying other mirror.


 One of the configured repositories failed (Oracle Linux / RHEL / CentOS-7 / x86_64 - VirtualBox),
 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. Disable the repository, 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 virtualbox

     4. 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=virtualbox.skip_if_unavailable=true

failure: repodata/repomd.xml from virtualbox: [Errno 256] No more mirrors to try.
http://download.virtualbox.org/virtualbox/rpm/el/7/x86_64/repodata/repomd.xml: [Errno -1] Gpg Keys not imported, cannot verify repomd.xml for repo virtualbox

Change History (3)

comment:1 by Frank Mehnert, 7 years ago

Resolution: obsolete
Status: newclosed

comment:2 by David Biesack, 7 years ago

I'm getting this error on a new CentOS 7 host after following https://wiki.centos.org/HowTos/Virtualization/VirtualBox but using

yum --enablerepo=virtualbox install VirtualBox-5.1

This was closed as obsolete - what is the workaround?

comment:3 by David Biesack, 7 years ago

My workaround - I was able to directly install the downloaded .rpm on CentOS 7 rather than install via a repo.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use