Page 1 of 1

install Virtualbox 4.0.8 in Ubuntu 11.04 using repository

Posted: 23. May 2011, 21:41
by edmund.laugasson
Trying to install VirtualBox 4.0.8 in Ubuntu 11.04 using repository will fail. I tried it yesterday (22.05.2011). Currently I'm sitting behind the Ubuntu 10.04 machine but already after adding repository it cannot download package list or was it broken file and therefore will fail. I had to comment out virtualbox repository in order to have possibility update and install other software.

I tried to report it yesterday, when that PC was available for me but activation link came so long time, that only now I am able to post it.

Re: install Virtualbox 4.0.8 in Ubuntu 11.04 using repository

Posted: 24. May 2011, 21:56
by Sasquatch
What do you have in your sources file (sources.list or separate .list file in sources.list.d)? What was the exact error you got? We need more information.

Re: install Virtualbox 4.0.8 in Ubuntu 11.04 using repository

Posted: 26. May 2011, 22:29
by myd0j0
I'm having the same problem installing. I followed the instructions on the Downloads page: http://www.virtualbox.org/wiki/Linux_Downloads

command line and synaptic (after clicking reload) both show this error:

W: Failed to fetch http://download.virtualbox.org/virtualb ... ty/Release Unable to find expected entry 'contrib/source/Sources' in Release file (Wrong sources.list entry or malformed file)

I ran "sudo apt-get install virtualbox-4.0" anyway and Software Center no longer shows VirtualBox in my list of installed software, even though it is installed and updated to 4.0.8 r71778 as well. Don't know if that will help, but there it is.

Re: install Virtualbox 4.0.8 in Ubuntu 11.04 using repository

Posted: 28. May 2011, 18:07
by Sasquatch
Disable the source-code repo option. That should get rid of the error.

Re: install Virtualbox 4.0.8 in Ubuntu 11.04 using repository

Posted: 1. Jul 2011, 09:28
by CeltaWeb
Sasquatch wrote:Disable the source-code repo option. That should get rid of the error.
Hi
I was getting the exact same error so I uncommented the source-code repo and the upgrade went smoothly
Thanks