You are not logged in.
Attempted to upgrade VirtualBox today from v5.0.20 to v5.1.2 by using the v5.1.2 deb installer and got an error message about v5.1.2 breaking v5.0.20. So, I had to remove v5.0.20 and then install v5.1.2. Usually, just running the deb with gdebi upgrades the app. Also, to remove VirtualBox:
sudo apt-get remove virtualbox-5.0
-- or --
sudo aptitude remove virtualbox-5.0
I was trying to uninstall by just using virtualbox and then discovered the actual name by searching Synaptic.
Last edited by KrunchTime (2016-08-01 23:17:32)
Offline
Usually, just running the deb with gdebi upgrades the app.
The "5.0" is part of the package name, not the version, so virtualbox-5.0 and virtualbox-5.1 are treated as two different packages.
This happens elsewhere, for example python2.7 and python3.4 can coexist on the same system. The virtualbox packages can not.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
https://packages.debian.org/sid/virtualbox Wow, is that from experimental? EDIT Oh, I see directly from Virtualbox.
Also over in kvm land for some is the
https://release.debian.org/transitions/ … e-gtk.html
which I saw from elsewhere. Gotta look up the dependencies with that one also for myself. My virtualbox is in testing - thanks for the heads up.
Last edited by paxmark1 (2016-08-02 04:05:35)
Offline
@paxmark1: I only run VirtualBox under Stable due to issues with kernel changes that sometimes occur under Testing and Unstable.
Offline