[Pkg-postgresql-public] Bug#703850: postgresql-contrib not upgraded

Daniel Pocock daniel at pocock.com.au
Mon Mar 25 19:02:48 UTC 2013


On 25/03/13 12:45, Christoph Berg wrote:
> Control: retitle -1 pg_upgradecluster should warn if packages are missing
>
> Re: Daniel Pocock 2013-03-24 <514F583C.9070209 at pocock.com.au>
>> This is an upgrade problem
>>
>> Old system has postgresql-8.4 and postgresql-contrib-8.4 on squeeze
>>
>> It is upgraded to wheezy
>>
>> postgressql-9.1 was installed, but postgresql-contrib-9.1 doesn't get
>> installed by the dist-upgrade
> Hi Daniel,
>
> this is (mostly) a user error. You could have avoided it by having the
> "postgresql-contrib" meta package installed.

I'm not sure it is fair to call this user error

a) my application needed the crypto library

b) I used packages.debian.org to search for packages containing that code

c) packages.debian.org showed me the postgresql-contrib-8.4 package

d) that is what I installed

There may be other valid ways that users have put themselves in a
similar position

I tried to check popcon stats to see how many users have
postgresql-contrib (vs postgresql-contrib-X) but it doesn't appear to
report on that package, so it is hard to estimate the potential impact
or urgency of this issue.

> I'll try to think of a way we can make pg_upgradecluster warn the user
> if the set of postgresql-$oldversion packages installed is a superset
> of postgresql-$newversion packages.
>
> Christoph



More information about the Pkg-postgresql-public mailing list