After I got blocked, I was able to get around this bug by going to a tty
command prompt (ctrl-alt-fn) and running
sudo dpkg -r -a
then running
dpkg --configure -a
The configure step appeared to pick up at the failing local installation
and the rest of the upgrade continued.
You could try that too. It's very low risk and from what I understand of the bug, likely to help.
Ian.
oedstero wrote:
> I'm in a rather hozed state, after deciding to start upgrading a -server
> installation from Feisty -> Gutsy -> Hardy due to Feisty going EOL in a
> couple months...
>
> Th
After I got blocked, I was able to get around this bug by going to a tty
command prompt (ctrl-alt-fn) and running
sudo dpkg -r -a
then running
dpkg --configure -a
The configure step appeared to pick up at the failing local installation
and the rest of the upgrade continued.
You could try that too. It's very low risk and from what I understand of the bug, likely to help.
Ian.
oedstero wrote:
> I'm in a rather hozed state, after deciding to start upgrading a -server
> installation from Feisty -> Gutsy -> Hardy due to Feisty going EOL in a
> couple months...
>
> Th