Your message dated Fri, 14 Jun 2019 06:54:59 +0200
with message-id <[email protected]>
and subject line Re: Bug#930495: My bad
has caused the Debian Bug report #930495,
regarding Recommends should be Depends
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
930495: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=930495
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: postgis
Version: 2.5.1+dfsg-1
The PostGIS extension for postgresql has apparently been moved out of
the PostGIS package. One must now install postgresql-11-postgis-2.5
and postgresql-11-postgis-2.5-scripts to get the needed functionality.
These packages are only Recommends though, so someone upgrading from
stretch with postgis package to buster will not actually get the
postgis extension, causing the pg_upgradecluster to fail spectacularly.
It seems like postgis should depend on both postgresql-11-postgis-2.5
and postgresql-11-postgis-2.5-scripts.
--- End Message ---
--- Begin Message ---
tags 930495 wontfix
thanks
On 6/14/19 12:06 AM, Michael Reed wrote:
> Perhaps what is needed is a meta package (like postgresql) so someone
> can install the extension once and have it upgraded across releases.
> The stuff currently in the postgis package should be moved to an
> optional postgis-utilities package (recommended by, but not a dependant
> of the meta package).
Upgrading is tricky, because the old extension is usually not compatible
with the new extension. You cannot use pg_upgradecluster to migrate
postgis databases for example. Starting with postgis 3.0 this should get
better.
After a distribution upgrade you currently need to ensure you have the
postgis packages for the new postgresql version installed, you can use
the virtual packages for that:
apt-get install postgresql-11-postgis
Then you need to recreate all databases that use the postgis extension
(or use the symlink hack and pg_upgrade).
We're not going to rename the postgis binary package, the extended
description is quite clear about what the package contains. All
postgresql extensions also follow the same package naming convention,
and we're not going to diverge from that.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
--- End Message ---
