reassign 383063 dbconfig-common
thanks

I am following the design set forth in the dbconfig-common docs and
examples.  You appear to be referencing section 7.2 of policy.

I am reassinging this to dbconfig-common since I can't do anything about
it if dbconfig-common requires packages to act this way (as it appears
to).  I can't really work out what the sane thing to do in postrm might
be since I can understand why dbconfig-common requires things to be
pulled out there. 

If the dbconfig-common maintainers believe that there is already a way
around this, I would ask them to please document it and update the
example files they install in /usr/share/doc/dbconfig-common so as to
not encourage developers to do things the wrong way.

Thanks,
-- John

On Mon, Aug 14, 2006 at 04:07:08PM -0400, Anthony DeRobertis wrote:
> Package: bacula-director-pgsql
> Version: 1.38.11-2
> Severity: serious
> 
> (Also in -1, and no doubt many previous versions)
> 
> The postrm script always uses dbconfig-common. Even if the first
> parameter is 'purge' (policy says you may only use Essential: yes
> packages in that case). Similarly, you can't use it in the abort-*
> targets either (though I don't see anywhere policy explitly says so).
> Try the following to see why (in a chroot, I'd hope):
> 
> # dpkg --purge dbconfig-common
> # dpkg -i bacula-director-pgsql*deb
> # dpkg -i bacula-director-pgsql*deb
> # dpkg --remove bacula-director-pgsql
> 
> dpkg will inform you that bacula-director-pgsql is in a very bad state
> (what it calls half-installed) and to install it again in order remove
> it. Which of course you can't do, because the prerm fails out. Twice.
> And then again when dpkg tries to do an error unwind. Leaving the
> package half-installed.
> 
> (To fix the chroot, install dbconfig common --- using dpkg, apt-get
> won't work anymore --- then install bacula-director-pgsql, then you can
> remove both. You probably already knew this, of course.)
> 
> 


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to