Your message dated Mon, 15 May 2006 08:30:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#367070: bacula-director-pgsql - postinst called with
unknown argument `upgrade'
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bacula-director-pgsql
Version: 1.38.9-3
Severity: grace
bacula-common fails to upgrade:
| Preparing to replace bacula-director-pgsql 1.36.3-2 (using
.../bacula-director-pgsql_1.38.9-3_amd64.deb) ...
| /var/lib/dpkg/tmp.ci/config: line 10:
/usr/share/dbconfig-common/dpkg/config.pgsql: No such file or directory
| dpkg: error processing
/var/cache/apt/archives/bacula-director-pgsql_1.38.9-3_amd64.deb (--unpack):
| subprocess pre-installation script returned error exit status 1
| /var/lib/dpkg/tmp.ci/postrm: line 13:
/usr/share/dbconfig-common/dpkg/postrm.pgsql: No such file or directory
| dpkg: error while cleaning up:
| subprocess post-removal script returned error exit status 1
It seems that it uses dbconfig-common from its preinstall.
Bastian
--
Lots of people drink from the wrong bottle sometimes.
-- Edith Keeler, "The City on the Edge of Forever",
stardate unknown
signature.asc
Description: Digital signature
--- End Message ---
--- Begin Message ---
Version: 1.38.9-7
> I'm pretty sure that "upgrade" is not one of the arguments that policy
> requires postinsts to support :)
I'm pretty sure it is for preinst. But it is fixed anyway.
Bastian
--
The man on tops walks a lonely street; the "chain" of command is often a noose.
signature.asc
Description: Digital signature
--- End Message ---
