The difference is that on Debian, I can always resume an upgrade done
with apt-get (or aptitude) dist-upgrade. Even though the dpkg process
had gotten wedged in state D, the (first) reboot was a normal one; after
I rebooted, I fully expected 'dpkg --configure -a' to resume where it
left off, as it
The difference is that on Debian, I can always resume an upgrade done
with apt-get (or aptitude) dist-upgrade. Even though the dpkg process
had gotten wedged in state D, the (first) reboot was a normal one; after
I rebooted, I fully expected 'dpkg --configure -a' to resume where it
left off, as it
The difference is that on Debian, I can always resume an upgrade done
with apt-get (or aptitude) dist-upgrade. Even though the dpkg process
had gotten wedged in state D, the (first) reboot was a normal one; after
I rebooted, I fully expected 'dpkg --configure -a' to resume where it
left off, as it
Hello Sam, sorry for the trouble you experienced during the upgrade. I
agree with you that the lack of documentation is a problem. However I
would like to point out that we use the same underlaying technology
/apt/dpkg) as debian to perform the upgrade. A kernel oops in the middle
of the upgrade (w
I understand your frustration, another observation:
* existence of a mysterious '/usr/shareFeisty' directory;
That looks like file system corruption (a result of the oops?) more than
anything else. Could you please run a filesystem check please?
--
Aborted upgrade process left laptop in total
Martin-Éric: your comment is completely out of order. It's a mistake
very easy to make.
I'm sure I don't need to remind you of
http://www.ubuntu.com/community/conduct
--
Aborted upgrade process left laptop in totally fucked state
https://bugs.launchpad.net/bugs/365485
You received this bug notif
Jesus, I'm sorry I don't have a magical built-in knowledge of which
package to file bugs such as this against. I'm sorry for naively typing
in 'upgrade' into the unhelpful package search box and picking a package
that sounded relevant to the problem at hand!
--
Aborted upgrade process left laptop
Some particularly amusing leftovers from the upgrade script were:
* existence of a mysterious '/usr/shareFeisty' directory;
* the permissions of /dev/null were reset such that only root may write to it
* screwed up ttf-uralic package that complained it could not be removed
because its fonts h
It's really frustrating to see Debian users come here and display a
complete lack of basic English reading skills by reporting a bug against
the entirely wrong package (upgrade-system), despite mentioning in their
bug report that they really mean to complain about another package
(update-manager).
