[Pkg-postgresql-public] Bug#714725: Bug#714725: Consider setting APT::NeverAutoRemove::"postgresql-*" in apt.conf

Christoph Berg myon at debian.org
Tue Jul 2 13:42:09 UTC 2013


Re: Peter Eisentraut 2013-07-02 <51D2BD16.6020100 at debian.org>
> > 3) would be needed if we decide that we also need to care about 
> > extension modules that should not be removed on dist-upgrade.
> > (Though I tend to think these would usually be manually installed.
> > But we might have the same metapackage-with-changing-dependency
> > problem there as well.)
> 
> It should be 3), because otherwise the postgresql-contrib-x.y package
> will be removed and you won't be able to dump your database if it uses
> any data type provided in a contrib module.  The same goes for things
> like postgresql-x.y-ip4r.

My thinking was that if you have any -contrib package installed, it
will be marked as manually installed and won't be removed
automatically anyway. Same for -ip4r and friends.

Marking all postgresql-* packages for NeverAutoRemove might also be a
bit overzealous, do we want to restrict this to
postgresql-*$laststableversion*? Do we want to drop the
NeverAutoRemove for $laststableversion once the cluster got upgraded?

(This sounds like the solution could get way too complex, I want a
simple thing.)

Christoph
-- 
cb at df7cb.de | http://www.df7cb.de/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-postgresql-public/attachments/20130702/43ede271/attachment.sig>


More information about the Pkg-postgresql-public mailing list