Bug#724582: marked as done (Upon ^C say "user interrupted received, will stop at next safe point, please wait...")
Your message dated Sat, 28 Sep 2013 10:30:25 +0800
with message-id <877ge1k79a.fsf@jidanni.org>
and subject line Re: Bug#724582: message should mention other solutions to 'dpkg was interrupted'
has caused the Debian Bug report #724582,
regarding Upon ^C say "user interrupted received, will stop at next safe point, please wait..."
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
724582: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=724582
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: message should mention other solutions to 'dpkg was interrupted'
- From: jidanni@jidanni.org
- Date: Wed, 25 Sep 2013 19:08:11 +0800
- Message-id: <87a9j1p3ac.fsf@jidanni.org>
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.
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.
--- End Message ---
--- Begin Message ---
OK forgetting about the idea.
--- End Message ---
Reply to: