You are not logged in.
When installing virtualbox via .deb file retrieved from the site, an error appeared because a dependency was not satisfactory for the installation. (libvpx6)
For this we will download the missing dependency and install it using the devuan Package View site:
wget http://deb.devuan.org/merged/pool/DEBIAN/main/libv/libvpx/libvpx6_1.9.0-1_amd64.deb
Once downloaded, just open an terminal window:
sudo gdebi libvpx6_1.9.0-1_amd64.deb
After installing the missing dependency you can continue installing virtualbox.
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
If gdebi is used to install the VirtualBox .deb it will pull in libvpx6 from the repositories automatically. No need to do it yourself like some hair-shirted Slackware user.
This works for me:
apt install -s ./virtualbox-6.1_6.1.36-152435~Debian~bullseye_amd64.deb
Remove the -s option if you actually do want to install the world's worst virtualisation solution.
Last edited by Head_on_a_Stick (2022-08-30 16:34:47)
“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.
Offline
If gdebi is used to install the VirtualBox .deb it will pull in libvpx6 from the repositories automatically. No need to do it yourself like some hair-shirted Slackware user.
This works for me:
apt install -s ./virtualbox-6.1_6.1.36-152435~Debian~bullseye_amd64.deb
Remove the -s option if you actually do want to install the world's worst virtualisation solution.
And then it can also happen that the right libssl dependency is missing:
wget http://deb.devuan.org/merged/pool/DEBIAN/main/o/openssl/libssl1.1_1.1.1o-1_amd64.deb
sudo gdebi libssl1.1_1.1.1o-1_amd64.deb
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
Or you could add the unstable repositories and pin them to 100 so packages from there are treated like backports:
https://www.debian.org/doc/manuals/debi … le_literal
That would certainly be easier than adding a new thread every time a package is blocked from testing.
“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.
Offline
Or you could add the unstable repositories and pin them to 100 so packages from there are treated like backports:
https://www.debian.org/doc/manuals/debi … le_literal
That would certainly be easier than adding a new thread every time a package is blocked from testing.
Thanks for the tip, I didn't know about this manipulation.
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
Don't try it with the stable release though. It is only appropriate for testing.
“Et ignotas animum dimittit in artes.” — Ovid, Metamorphoses, VIII, 18.
Offline
Why use this product of dubious quality when there is good quality and open source alternative-QEMU / kvm?
What economists call over-production is but a production that is above the purchasing power of the worker, who is reduced to poverty by capital and state.
----+- Peter Kropotkin -+----
Offline
Why use this product of dubious quality when there is good quality and open source alternative-QEMU / kvm?
All my virtual machines are under virtualbox, when I was under mac I used vmware fusion.
But the idea of using qemu/kvm in the future is not distasteful.
AMD Ryzen 7 3700X - Gigabyte B550 AORUS ELITE V2 - 4x8GB DDR4 - SSD 1,5TO - GTX1660TI 6GB - PSU Gigabyte 750W Gold - Zalman X3 White
Devuan / W11
Offline
I used to use vBox, I thought it was really good. Generally I used to use it for one game "DiD's F22".
Once that game was irreversibly tanked remotely, I gave up on vBox.
But I remember struggling to get vBox configured and eventaually having a system that was reliable and flexible.
I was still using Mandriva in those days.
:-)
Offline