Your message dated Tue, 9 Jan 2018 18:18:00 +0100
with message-id <8eb9d249-9c74-3bc9-c90b-4b7cb09d7...@xs4all.nl>
and subject line Re: Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch
has caused the Debian Bug report #886742,
regarding postgresql-9.4-postgis-2.1 missing in stretch
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 ow...@bugs.debian.org
immediately.)
--
886742: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886742
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: postgresql-9.4-postgis-2.1
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled
database becomes corrupt when upgrading from jessie to stretch since
the required postgis libraries are missing. This can cause serious data
loss, because once upgraded to stretch, the postgis data can't be
accesed nor dumped (Database gives error "could not access file
"$libdir/postgis-2.1": no such file or directory").
Also upgrading the database to postgresql-9.6 does not work.
-- System Information:
Debian Release: 8.10
APT prefers oldstable-updates
APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/20 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--- End Message ---
--- Begin Message ---
severity 886742 normal
thanks
Hi Juergen,
On 01/09/2018 02:16 PM, Bas Couwenberg wrote:
> On 2018-01-09 14:08, Christoph Berg wrote:
>> Re: Juergen Fuchsberger 2018-01-09
>>> Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled
>>> database becomes corrupt when upgrading from jessie to stretch since
>>> the required postgis libraries are missing. This can cause serious data
>>> loss, because once upgraded to stretch, the postgis data can't be
>>> accesed nor dumped (Database gives error "could not access file
>>> "$libdir/postgis-2.1": no such file or directory").
The database is not corrupt, your old database still works (after
installing the old postgis).
>> Could you append the apt output to this bug? Namely, which packages
>> got removed? (/var/log/apt/term.log)
>>
>>> Also upgrading the database to postgresql-9.6 does not work.
>>
>> What did you try, and what didn't work?
>
> Probably pg_upgradecluster, and that is not supported for databases with
> the postgis extension.
>
> See my reply to #886738 and
> http://lists.alioth.debian.org/pipermail/pkg-grass-devel/2017-November/064317.html
>
>
> For more info, see:
>
> http://blog.cleverelephant.ca/2016/08/postgis-upgrade.html
>
> http://www.bostongis.com/blog/index.php?/archives/268-Using-pg_upgrade-to-upgrade-PostGIS-without-installing-an-older-version-of-PostGIS.html
>
>
> As long as the postgis package is built for a single postgresql version,
> upgrades cannot be supported.
>
> When using postgis on Debian, distribution upgrades involve recreating
> the postgis databases as pg_upgradecluster will fail.
See the 'more info' links for hack you can use to fix your upgrade.
For the time being upgrades of postgis databases using
pg_upgrade{,cluster} are not supported. You need to recreate the
database in the new cluster when not using the hacks.
Kind Regards,
Bas
--- End Message ---
_______________________________________________
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
