Control: reassign -1 apt Hi!
On Wed, 2013-09-25 at 19:08:11 +0800, jida...@jidanni.org wrote: > Package: dpkg > Version: 1.17.1 > Severity: wishlist > This message assumes the user wants to continue the operation: > E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to > correct the problem. This is not a dpkg message, that's coming from (lib)apt. > But there is also a good chance the reason dpkg was interrupted was due > to the user purposely interrupting it in order to back out of what he > was doing. > > Therefore the message should also mention what to do in that case. > > Here's a scenario: > User does > aptitude safe-upgrade > says Yes > then realizes that what is about to happen is not what he wants. > He hits ^C, but that is ignored (by design. OK.) > He goes to another window and does killall aptitude. > Now when he does aptitude safe-upgrade again he gets > E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to > correct the problem. > W: Could not lock the cache file; this usually means that dpkg or another apt > tool is already installing packages. Opening in read-only mode; any changes > you make to the states of packages will NOT be preserved! > E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to > correct the problem. > > So perhaps add "Or try dpkg -i Current.deb on any half installed packages > (found by dpkg -l) that you don't want to upgrade to New.deb" or > something like that. I'll let the apt maintainers decide if that's appropriate, by reassigning the bug report to them. Thanks, Guillem -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
