Bug#839182: postgresql-9.4-postgis-2.2 and postgresql-9.4-postgis-2.1 cannot be installed simultaneously

[Markus Wanner]

Control: tags -1 +pending

On 09/30/2016 08:00 PM, Greg Burek wrote:
> Ah ok I understand now.

A transition is pending (pgroute), so we're postponing the next upload
to Sunday or Monday.

However, pgapt got updated already and from what you're reporting you
seem to use that repository.

> This is great, as we frequently work with base backups that require
> older postgis binaries, but want all new extensions to use the latest
> available versions. Having the latest scripts package satisfy
> dependencies for all previous versions gives us the ability to do this. 

This should be possible with at least PostGIS 2.2 and 2.3, now (assuming
pgapt).

> This sounds right. 
> 
> Ideally, all postgis packages should require `postgis-scripts` dummy
> package, which then depends on the latest available, in this case
> `postgis-2.3-scripts`.

We don't use a virtual or dummy package, but reduced the dependency from
the extension package (postgresql-X.Y-postgis-M.N) to its -scripts
package to a recommendation.

That way, the extensions are co-installable. You even get the option to
remove all -scripts packages, but keep the extension.

I'll have to check the situation with postgis-2.1. First tests indicated
that version was co-installable as well, but I'm not sure about the
situation with the -scripts package, there.

Kind Regards

Markus Wanner


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1513 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-grass-devel/attachments/20160930/67830963/attachment-0001.sig>