[buildd-tools-devel] Bug#857770: src:postgresql-debversion: please provide a unversioned binary package

[Antonio Terceiro]

On Sat, Mar 25, 2017 at 07:58:54PM +0100, Christoph Berg wrote:
> Control: tags -1 moreinfo
> 
> Re: Antonio Terceiro 2017-03-14 <20170314200003.xupt5eddlfw5idux at debian.org>
> > At the moment I am automating the installation of postgresql and and the
> > debversion extension. The fact that there is no "unversioned" binary
> > package makes that harder than necessary: I will have to hardcode
> > postgresql-X.Y-debversion, and as soon as that deployment recipe need to
> > be applied to a different Debian version, that will break.
> > 
> > So, please provide an unversioned binary package called
> > 'postgresql-debversion' which depends on the actual package for the
> > current PostgreSQL version.
> 
> Hi,
> 
> we can't simply put .so files for an arbitrary PostgreSQL version into
> a postgresql-debversion.deb because that will break existing
> installations on dist upgrade.

Yes, of course. That was not what I suggested.

> What we can do is to "Provides: postgresql-debversion" from each of
> the postgresql-X.Y-debversion packages. That should fix your
> deployment problem. (However, it won't make upgrades work, because
> it doesn't keep the PostgreSQL and extension versions in sync.)
> 
> Does that help for your case?

I don't exactly get why having a package postgresql-debversion that
depends on the postgresql-X.Y-debversion corresponding to the current
X.Y would not work. server and client themselves are already managed
like this for ages.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/buildd-tools-devel/attachments/20170326/3004cafe/attachment.sig>