Dependency failure on Fedora 29

[jonascrescencio]

I installed the new Fedora 29 from zero.

I tried to install Virtualbox from repo. But it is not recognized:

wget ​https://download.virtualbox.org/virtualbox/rpm/fedora/virtualbox.repo dnf update

returns:

failed to synchronize cache for repo 'virtualbox' disabling

So I tried to install the RPM package:

dnf install VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64.rpm Erro:

Problema: conflicting requests

• nothing provides libvpx.so.4()(64bit) needed by VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64

rpm -ivh VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64.rpm erro: Dependências não satisfeitas:

libQt5X11Extras.so.5()(64bit) é requerido por VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64 libQt5X11Extras.so.5(Qt_5)(64bit) é requerido por VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64 libvpx.so.4()(64bit) é requerido por VirtualBox-5.2-5.2.20_125813_fedora26-1.x86_64

rpm -qa | grep libvpx libvpx-1.7.0-7.fc29.x86_64

ll /usr/lib64/libvpx.so* lrwxrwxrwx. 1 root root 15 jul 20 05:55 /usr/lib64/libvpx.so.5 -> libvpx.so.5.0.0 lrwxrwxrwx. 1 root root 15 jul 20 05:55 /usr/lib64/libvpx.so.5.0 -> libvpx.so.5.0.0 -rwxr-xr-x. 1 root root 2382120 jul 20 05:55 /usr/lib64/libvpx.so.5.0.0

It requires libvpx.so.4, but Fedora 29 has the libvpx.so.5

I don't know how to solve this problem.

[Andre Robatino]

To work around the dependency problem, see ​https://forums.virtualbox.org/viewtopic.php?f=7&t=90111 .

[Autotraker]

The repo file is wrong. Actually its not the repo file, its they haven't updated their download server to support Fedora 29 yet. As a workaround, Edit the repo after you wget it and replace the $releasever variable with 28. so the corrected line should now be baseurl=​http://download.virtualbox.org/virtualbox/rpm/fedora/28/$basearch They haven't created a folder yet for Fedora 29 but using the repo for 28 works just fine.

[Andre Robatino]

The F28 version only works in F29 by using the workaround in my previous comment. (That's still true for 5.2.22, even though F29 was already released.) When VBox is finally rebuilt for F29, it will no longer need the workaround, but that version will only appear in the F29 repo which doesn't exist yet. My point is, don't get used to using the F28 repo unless you don't mind leaving the workaround in place even after it's no longer needed.

[jonascrescencio]

Yes. I did not use the F28 repo.

The installation of compat-libvpx4 following ​https://forums.virtualbox.org/viewtopic.php?f=7&t=90111 solved the problem.

Thank You very much!

Replying to robatino:

The F28 version only works in F29 by using the workaround in my previous comment. (That's still true for 5.2.22, even though F29 was already released.) When VBox is finally rebuilt for F29, it will no longer need the workaround, but that version will only appear in the F29 repo which doesn't exist yet. My point is, don't get used to using the F28 repo unless you don't mind leaving the workaround in place even after it's no longer needed.

[Michael Thayer]

I have been trying to rebuild our package for Fedora 29, but have not yet found time to debug it properly. Something is going wrong with debug source extraction. If anyone feels like taking a look, I think that our package build scripts should be usable from the Subversion sources, probably also from the release tarballs. Basically you go into the src/VBox/Installers/linux folder and execute "rpm/rules binary".

[Andre Robatino]

There was a similar change in F25, going from libvpx.so.3 to libvpx.so.4 (see https://www.virtualbox.org/ticket/16038 ). Don't know if that helps.

[Michael Thayer]

No, because the problem with rebuilding the package is not related to libvpx. It is presumably due to some change between Fedora 26 and 29 which causes our scripts to work with the first and not with the second. And that will take time which I don't have just now to analyse.

[Michael Thayer]

Added a Fedora 29 build in 6.0.