Comment 18 for bug 559582

tom can confirm that this method works :) on a physical machine if someone
would confirm for those having an issue with upgrading virtual machines.

On Mon, Apr 12, 2010 at 5:17 PM, Jonathan Aquilina
<email address hidden>wrote:

> will try this out to confirm
>
>
> On Mon, Apr 12, 2010 at 5:04 PM, Tom Worley <email address hidden> wrote:
>
>> I've managed to around this by doing the following:
>>
>> sudo sed -i 's/karmic/lucid/g' /etc/apt/sources.list
>> sudo apt-get update
>> wget
>> http://mirrors.kernel.org/ubuntu/pool/main/m/mountall/mountall_2.11_amd64.deb
>> sudo dpkg --force-all -i /var/cache/apt/archives/mountall_2.11_amd64.deb
>> sudo apt-get -f install
>> sudo apt-get dist-upgrade
>>
>> Which manually changes to lucid, gets the 64bit version of the latest
>> lucid mountall (change to the i386 if not running 64 bit), forces
>> mountall to install without the dependancies, then fixes the
>> dependancies and does a dist-upgrade to upgrade everything else.
>>
>> On a bare-metal karmic install this worked fine, and the server has
>> returned after remote reboot.
>>
>> --
>> Upgrade from karmic to lucid failes with Internal Error, Could not perform
>> immediate configuration (2) on mountall
>> https://bugs.launchpad.net/bugs/559582
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>
>
>
> --
> Jonathan Aquilina
>

--
Jonathan Aquilina