Bug#651380: marked as done (unexpected restart of (half-configured) service)
Your message dated Mon, 12 Dec 2011 18:53:56 +0100
with message-id <CAAZ6_fDU5W-khm7K5zCXs-kpSFdcCeOte1Q+ZksLgz8o4e9NsQ@mail.gmail.com>
and subject line Re: Bug#651380: unexpected restart of (half-configured) service
has caused the Debian Bug report #651380,
regarding unexpected restart of (half-configured) service
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.)
--
651380: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651380
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: apt
Version: 0.7.20.2+lenny2
Severity: wishlist
If a package is in a half-configured state, apt tries to finish setting
it up, it would be a nice improvement this was warned about.
That would be okay, apt does in fact mention it, however it's easy to
miss it in the output ("1 not fully installed or removed"). A nice
improvement would be to list the package in question and also to mention
that the service will be configured.
A real-life example might explain a scenario where this would have been
useful (note that I don't normally administer the box in question - I
wouldn't have left it like this!) Notice my "OMG! ^C" :-)
~# apt-get install bacula-fd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
bacula-common
Suggested packages:
bacula-doc bacula-traymonitor
The following NEW packages will be installed
bacula-common bacula-fd
0 upgraded, 2 newly installed, 0 to remove and 35 not upgraded.
1 not fully installed or removed.
Need to get 608kB of archives.
After this operation, 1352kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Get: 1 http://ftp.uk.debian.org lenny/main bacula-common 2.4.4-1 [403kB]
Get: 2 http://ftp.uk.debian.org lenny/main bacula-fd 2.4.4-1 [205kB]
Fetched 608kB in 4s (139kB/s)
Selecting previously deselected package bacula-common.
(Reading database ... 28394 files and directories currently installed.)
Unpacking bacula-common (from .../bacula-common_2.4.4-1_amd64.deb) ...
Adding user 'bacula'... Ok.
Selecting previously deselected package bacula-fd.
Unpacking bacula-fd (from .../bacula-fd_2.4.4-1_amd64.deb) ...
Processing triggers for man-db ...
Setting up mysql-server-5.0 (5.0.51a-24+lenny4) ...
Stopping MySQL database server: mysqld^Cdpkg: error processing
mysql-server-5.0 (--configure):
subprocess post-installation script killed by signal (Interrupt)
Setting up bacula-common (2.4.4-1) ...
Setting up bacula-fd (2.4.4-1) ...
Starting Bacula File daemon: bacula-fd.
Errors were encountered while processing:
mysql-server-5.0
--- End Message ---
--- Begin Message ---
On Thu, Dec 8, 2011 at 09:41, Adrian Bridgett <adrian@smop.co.uk> wrote:
> A real-life example might explain a scenario where this would have been
> useful (note that I don't normally administer the box in question - I
> wouldn't have left it like this!) Notice my "OMG! ^C" :-)
A package in half-configured state is in an inconsistent state.
This only happens if an error occurred while configuring it - e.g.
you killed it with ^C. The behavior of an application included in a not
configured package is undefined. In your case, mysql might or might
not work - regardless of what it says. It might start and provide a
mysql instance - but might be not in in a way you would expect it /
you have configured it. In effect, you are playing russian roulette
and at some point the *click* will be a bit louder than normal…
So APT is completely right to move the system to a consistent state
and it can't be disabled as it is a hard requirement for APT to move
from one consistent state to another consistent. This is complicated
enough, trying to keep a system broken would make it even complexer…
Therefore closing as too complex/not really needed/not a good idea.
Best regards
David Kalnischkies
--- End Message ---
Reply to: