On Mon, Apr 12, 2010 at 6:28 PM, Tom Worley <email address hidden> wrote:
> The above workaround was on a linode virtual server and worked first time.
> There's a slight amendment to the above instructions, the dpkg line should
> read:
> sudo dpkg --force-all -i mountall_2.11_amd64.deb
>
> I used the local copy that I got dist-upgrade to download while doing
> testing
>
> --
> 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.
>
for me your original way worked.
On Mon, Apr 12, 2010 at 6:28 PM, Tom Worley <email address hidden> wrote:
> The above workaround was on a linode virtual server and worked first time. 2.11_amd64. deb /bugs.launchpad .net/bugs/ 559582
> There's a slight amendment to the above instructions, the dpkg line should
> read:
> sudo dpkg --force-all -i mountall_
>
> I used the local copy that I got dist-upgrade to download while doing
> testing
>
> --
> Upgrade from karmic to lucid failes with Internal Error, Could not perform
> immediate configuration (2) on mountall
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Jonathan Aquilina