Package: postgresql-7.4
Version: 1:7.4.13-1
Severity: important
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
i have a system on which the postgres service is disabled (the Debian
Wæy) for the default runlevel (i use it mainly for testing purposes).
for the past version or two, whenever i try and upgrade postgres i get:
(Reading database ... 133510 files and directories currently installed.)
Preparing to replace postgresql-7.4 1:7.4.13-1 (using
.../postgresql-7.4_1%3a7.4.13-2_amd64.deb) ...
Stopping PostgreSQL 7.4 database server: mainError: cluster is not running
invoke-rc.d: initscript postgresql-7.4, action "stop" failed.
dpkg: warning - old pre-removal script returned error exit status 1
dpkg - trying script from the new package instead ...
Stopping PostgreSQL 7.4 database server: mainError: cluster is not running
invoke-rc.d: initscript postgresql-7.4, action "stop" failed.
dpkg: error processing
/var/cache/apt/archives/postgresql-7.4_1%3a7.4.13-2_amd64.deb (--unpack):
subprocess new pre-removal script returned error exit status 1
Errors were encountered while processing:
/var/cache/apt/archives/postgresql-7.4_1%3a7.4.13-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
this is because the init script exits with a non-zero status code when
told to stop a service that isn't running. i don't believe that policy
dictates how init scripts should act for such a situation, (or if it does,
the severity should be raised), but the LSB and common sense do dictate
that it should return 0 in such cases. i'd provide a patch for the
init script, but the code is tucked away from my conffile in
/usr/share/postgresql-common/init.d-functions and is complicated
enough that it would be better for someone who understands what's going
on to take a stab at it.
sean
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEgZfUynjLPm522B0RAgqiAJ9ym09HbYnhekfSFmBuSd9IxA6T3QCcDcHh
Vv886F2Y1RugLbMyp9nXWgI=
=Zl2x
-----END PGP SIGNATURE-----
