Page 1 of 1
Use Virtualbox on Debian Bullseye
Posted: 21. Sep 2020, 09:58
by nolddor
Hi guys,
I've been using Virtualbox on my Debian testing (Debian 11) for a while using the official Debian 10 package. Since last OS update, dependencies are not meet any more. Using GDebi, output says that virtual box deb package is unable to find libvpx5 dependency on my system. libvpx5 is not present on Debian testing, but I've been able to install it using stable backports, now Virtualbox package is looking for (python <= ) package: I've already installed python2 package on my system and now im able to use python 2.8 by running the command python2
Code: Select all
nolddor@computer:~$ sudo gdebi '~/Downloads/virtualbox-6.1_6.1.14-140239~Debian~buster_amd64.deb'
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading state information... Done
Unable to install this package
Dependency is not satisfiable: python (< 2.8)
nolddor@computer:~$ python2 --version
Python 2.7.18
nolddor@computer:~$ apt list python2
Listing... Done
python2/testing,now 2.7.18-2 amd64 [installed, automatic]
python2/testing 2.7.18-2 i386
nolddor@computer:~$ apt list python
Listing... Done
However, since package name isn't the same how can I force Virtualbox to look for python2 package instead?
Thanks in advance
Re: Use Virtualbox on Debian Bullseye
Posted: 22. Sep 2020, 00:20
by Smackey's dad
I can offer a suggestion, but it's a long shot. Can you try creating soft-links to old and new application/library? For e.g. soft-link python2 to python. I have done this as a workaround in other situations and gotten away with it.
Re: Use Virtualbox on Debian Bullseye
Posted: 22. Sep 2020, 08:23
by nolddor
Smackey's dad wrote:I can offer a suggestion, but it's a long shot. Can you try creating soft-links to old and new application/library? For e.g. soft-link python2 to python. I have done this as a workaround in other situations and gotten away with it.
But how to trick the *.deb package to force search for python2 dependency instead? Binary on filesystem are easily to modify with syslinks as you pointed out but no idea how to trick packages/dependencies. Any idea?
Re: Use Virtualbox on Debian Bullseye
Posted: 22. Sep 2020, 14:11
by Smackey's dad
Sorry I did not fully understand the issue. Again due to my lack of familiarity with Debian packages, this second suggestion may also be off. Can you download and manually install a stand-alone python Deb package? Hopefully that will satisfy the dependency.
Re: Use Virtualbox on Debian Bullseye
Posted: 22. Sep 2020, 20:24
by scottgus1
One thing to consider is that there is no Debian 11 download from official Virtualbox at
https://www.virtualbox.org/wiki/Linux_Downloads. Debian's website
https://www.debian.org/releases/bullseye/ says Debian 11 is in "testing".
So Debian 11 is a pre-release and is not supported by Virtualbox yet.
Re: Use Virtualbox on Debian Bullseye
Posted: 25. Sep 2020, 00:29
by rochaj
i'm having the same issue here, i'm on debian bullseye and my virtualbox stoped after a upgrade, now in debian testing there is no python package in apt.
Re: Use Virtualbox on Debian Bullseye
Posted: 25. Sep 2020, 13:37
by GRL
Same here - have to use Bullseye for other reasons.
Installed the python2 and VirtualBox 6.1 deb with ignore-depends - so it works for now.
But its a pain in the ass to manually take care of that on every update. So a bullseye-Version (which should be just a change of dependencies from python to python2 afaik) would be highly appreciated.
Lukas
Re: Use Virtualbox on Debian Bullseye
Posted: 25. Sep 2020, 18:18
by Keeshah
Just wanted to drop my MeToo in here.
Re: Use Virtualbox on Debian Bullseye
Posted: 27. Sep 2020, 17:57
by Keeshah
Hi guys,
okay, I figured a soution for me out. I just used the genereric 64BitLinux Version, which doesn't have all the flaws of the packed version. I even could remove python2, and it still works. Still got a problem with the installation, since it won't offer the Do you want to disable secure boot? Which I obviously don't, kicked it, called config after the install, it compiled the drivers and after signing the drivers with the mok, it runs like before.
Cheers,
Dirk.