Your message dated Mon, 7 Mar 2016 22:45:15 +0000
with message-id <[email protected]>
and subject line Bug#691370: W: Operation was interrupted before it could finish
has caused the Debian Bug report #691370,
regarding W: Operation was interrupted before it could finish
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 [email protected]
immediately.)
--
691370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691370
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: aptitude
If one hits ^C during an upgrade, the upgrade does not stop
(probably to protect us from damage, OK) but near the end, we see
"W: Operation was interrupted before it could finish"
Please
1) add an indication of what program (aptitude?) is giving the message.
2) say what operation.
# aptitude full-upgrade
...
Installing new version of config file
/etc/java-7-openjdk/security/java.security ...
Setting up openjdk-7-jre-lib (7u3-2.1.3-1) ...
Setting up openjdk-7-jre:i386 (7u3-2.1.3-1) ...
W: Operation was interrupted before it could finish
Current status: 0 updates [-71].
--- End Message ---
--- Begin Message ---
Hi,
2012-10-27 14:58 Daniel Hartwig:
On 25 October 2012 04:44, <[email protected]> wrote:
Package: aptitude
If one hits ^C during an upgrade, the upgrade does not stop
(probably to protect us from damage, OK) but near the end, we see
"W: Operation was interrupted before it could finish"
Please
1) add an indication of what program (aptitude?) is giving the message.
2) say what operation.
# aptitude full-upgrade
...
Installing new version of config file
/etc/java-7-openjdk/security/java.security ...
Setting up openjdk-7-jre-lib (7u3-2.1.3-1) ...
Setting up openjdk-7-jre:i386 (7u3-2.1.3-1) ...
W: Operation was interrupted before it could finish
Current status: 0 updates [-71].
Hello
The warning is from libapt-pkg, so aptitude is the program reporting
it. The only indication of this is the familiar “W:” mark. While it
may be useful to change APT to display GNU-style errors (“PROGRAM:
MESSAGE”) there is a lot of inertia behind the current style.
The operation is the entirety of what you asked aptitude to do, in
this case full-upgrade. When APT receives SIGINT it will allow the
current dpkg run to complete and abort before the next. There may be
multiple dpkg runs for an operation to allow for package relationships
such as Pre-Depends and Conflicts. This warning thus indicates that
the operation requested on the command line was left incomplete. The
APT and dpkg databases should be consistent, though some packages may
be half-installed or missing dependencies, while others are not
installed (or removed) at all.
The term “operation” here seems to be quite useful as a general
reference to any of the complex actions which may be requested of APT.
I can not immediately think of any more useful replacement for the
warning as a whole, however suggestions are welcome.
I agree with the above.
2012-10-28 02:46 [email protected]:
Well all I know is when I finally got back to the shell prommpt,
further aptitiude full-upgrade or dpke --configure -a all said there was
nothing left to do,
so some of the details you mention should get printed on the screen,
so the user knows exactly what kind of state he will now be left in,
and what steps he should take to make his system then back to normal.
This is something internal of apt, about we cannot do much. We have to
print the warnings that it emits, otherwise there might be important
information missing, or we cannot detect error conditions.
The "dpkg --configure -a" is done by aptitude to take some (mostly
blind) remedial action in cases where there is some breakage in dpkg,
which might also be because of a post-install script failing or some
other severe error. In this case, it is hoped that the further step
that aptitude takes will help to configure other pending packages, even
if one or some remain broken.
In the cases where "there was nothing left to do", it's better to not
have anything left to do and print a harmless message than having a
broken system where we could have avoided it by running this command.
So:
a) We should not ignore or hide the message
b) We cannot know what messages from libapt will come, or control how it
manages things internally once control is passed to it to run dpkg
(e.g. libapt can decide to inhibit Control-C entirely while dpkg runs
in the next version)
c) Trying to take the remedial action is the better that we can do in
these cases
d) aptitude doesn't know what went wrong, so there's nothing to base the
explanations on.
The user, having pressed Control-C, is in a much better position than
aptitude to guess that it was the keypress/request the one which
caused the operation to be finished early, or let's say...
"interrupted", which is exactly what the message says, and indeed
that's what the user would come to expect when Control-C was issued
in the first place (either that, or pressing it by mistake). So no
surprises there.
So I don't think that there's much else that /can/ or that /should/ be
done regarding this, same as the previous developer, so closing this bug
after a few years out in the rain.
Cheers.
--
Manuel A. Fernandez Montecelo <[email protected]>
--- End Message ---
_______________________________________________
Aptitude-devel mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/aptitude-devel
