Error downloading wheezy 4.1.12 and 4.1.12 extension pack

It's looking for 77218 when 77245 is the current version
Back to top

amazing, I installed vbox 2 days ago, 4.1.12 using the first version number, and oracle changed it in the mean time, I have literally never seen anything that sloppy come from vbox/oracle.

Obviously, the version number 4.1.12 should have been changed when the 77218 was changed, but they just decided to change one of them.

I'll have to change the backend version number detection to handle checking both numbers, which of course should not be necessary.

Thank you for the notification however.
Back to top

Thanks h2, 4.1.12 installed OK
Back to top

backend is updated now to check for both numbers.
Back to top

hi

redid partimage and smxi now detects correct version

thanks heaps

2) trivia below

smxi for some reason did not like the oracle site and wanted to take 1 day to do the download so I stopped smxi and ran the command from the console

apt-get install virtualbox-4.1 .....which on my slow aussie net took about 7 minutes

b) when I started vbox to test it.....it detected I had an older extension pack and offered to download a newer one from

dlc.sun.com.edgesuite.net/virtualbox/4.1.12/Oracle_VM_VirtualBox_Extension_Pack-4.1.12.vbox-extpack

and downloaded it and asked for root pw to install it

its a shame that oracle don't have this as a deb?

regards

no need to reply its just a rant
Back to top

I don't use apt for handling vbox, because I need it for work, has to work.

So I always use vbox non ose labeled install, which downloads the deb from vbox/oracle, and installs it, then it does the steps to add the guest extenions, which requires some cleanup prior.

Technically now there is only one deb, ose, and the non ose stuff has been moved to the extension pack, so svmi is not really using the right terms, but I left it that way ose/non-ose because that's how it was.

With ose, I believe svmi uses apt to install it if you have the sources present, otherwise it uses the direct download, but I never use the apt method.

I could see an option to install the actual vbox deb via download for the ose now as well, though usually it's best to go via apt I think. With apt-get some dependency issues can fail to get handled, with aptitude, those are handled post deb install, one of the positive features of aptitude is that it will fix dependencies on packages installed from deb via dpkg --install
Back to top

Just a hint,
my vbox claimed today that vBox 4.1.14 should be available.

regards

Reiner
Back to top

been in svmi since april 26th. I updated the backend version detection so I get alerted when a new version come up now. Then I can update svmi if it's all fine.
Back to top

ok, thanks for the info !

regards

Reiner
Back to top

Just a hind.
My VBox claims for some days that Vbox 4.2.18 should be available now.
svmi currently only seems to know 4.2.16.

regards

Reiner
Back to top