Page 1 of 1

Can't Install 5.0.18 on OpenSuse 13.2

Posted: 22. Apr 2016, 09:25
by DrRog
Hello,

Everytime I try and install it this message appears:

Error: INVALID:VirtualBox-5.0-5.0.18_106667_openSUSE132-1.x86_64 (file-2593451d): Signature verification failed [4-Signatures public key is not available]
Header V4 DSA/SHA1 Signature, key ID 98ab5139: NOKEY
Header SHA1 digest: OK (5c5c546f6312e391e2b7877f64fa1dc53fa89bd0)
MD5 digest: OK (cc3eeef96ca942e33bd49bfa41d2cd15)
V4 DSA/SHA1 Signature, key ID 98ab5139: NOKEY


There seems to be no way to fix this, I tried this from the internet:

zypper remove virtualbox-5.0
zypper install dkms kernel-devel

Which produced this message:

Loading repository data...
Reading installed packages...
'kernel-devel' is already installed.
No update candidate for 'kernel-devel-4.1.20-11.1.noarch'. The highest available version is already installed.
'dkms' not found in package names. Trying capabilities.
No provider of 'dkms' found.

zypper addrepo http://download.virtualbox.org/virtualb ... albox.repo
zypper install virtualbox-5.0

Which produced this message:

Retrieving repository 'VirtualBox for openSUSE 13.2 / Leap 42.1' metadata ---[\]
File 'repomd.xml' from repository 'VirtualBox for openSUSE 13.2 / Leap 42.1' is signed with an unknown key '54422A4B98AB5139'. Continue? [yes/no] (no): y
Retrieving repository 'VirtualBox for openSUSE 13.2 / Leap 42.1' metadata [done]
Building repository 'VirtualBox for openSUSE 13.2 / Leap 42.1' cache .....[done]
Loading repository data...
Reading installed packages...
Package 'virtualbox-5.0' not found.
Resolving package dependencies...

Then I tried installing it from the RPM as a test and just got the first message again. I was using 5.0.14 and that was fine, why have they knackered 5.0.18 and how do I get it too work?? This is spectacularly frustration as my job is based around virtual machines and I am left staring impotent at the screen :x

Re: Can't Install 5.0.18 on OpenSuse 13.2

Posted: 22. Apr 2016, 09:44
by DrRog
Fixed (or fudged!!)

This is useful for anyone else caught unawares by this sudden inexplicable error. As a scientific experiment when trying to install the RPM in YAST when the message box appears with the error there are three buttons:

Abort
Retry
Ignore

For science I clicked "ignore" and it installed and ran fine - phew!

As for how that mysterious package error came into existence only Oracle knows hopefully they will fix it so people without degrees in computer science can install the software without having a panic attack at an ambiguous error message, surely in the 21st century only Microsoft does that? :)