Re: Peter Eisentraut 2013-07-03 1372818582.22689.6.ca...@vanquo.pezone.net
Marking only the stable version doesn't sound very reliable. If you
want to guard the data, you have to do it independent of what the
preferred version is. Users of apt.postgresql.org will have even more
complex
Package: postgresql
Version: 9.1+134wheezy3
Severity: wishlist
I've twice seen people on #postgresql who were upgrading from squeeze
to wheezy and ended up with postgresql-8.4 removed and postgresql-9.1
installed, the existing 8.4 cluster being inaccessible. What happened
there is that they have
On 7/2/13 4:26 AM, Christoph Berg wrote:
The question now is which package(s) should be marked as
NeverAutoRemove.
1) The postgresql-x.y package of the (old)stable release 2)
^postgresql-[0-9]+-[0-9]$ 3) ^postgresql-.*
2) is probably equivalent to 1), as there's only one version in
Re: Peter Eisentraut 2013-07-02 51d2bd16.6020...@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
On Tue, 2013-07-02 at 15:42 +0200, Christoph Berg wrote:
Re: Peter Eisentraut 2013-07-02 51d2bd16.6020...@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
5 matches
Mail list logo
