Comment 136 for bug 115616

So, if apt-get dist-upgrade is no longer considered a "supported" method or "the right way" of upgrading, what are users to do when the update manager chokes on a package that corrupted on download and has to be killed? That happened to me. After a bit of fighting with dpkg, I could get apt-get dist-upgrade to run and get a working (except for this) system again. The command line really really should never break, and having different results from a dist-upgrade than from the update manager, is a bad thing.