On 2018-01-10 09:10, Bas Couwenberg wrote: > On 2018-01-10 08:35, Jürgen Fuchsberger wrote: >> On 2018-01-09 18:18, Sebastiaan Couwenberg wrote: >>> 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). >> >> Sure, but I can't install the old postgis-2.1 because it is not >> available in stretch. > > So temporarily add the sources for jessie and install postgis from > jessie and remove the sources again. > > Or use the symlink hack. > >> I think the problem is that postgis-2.1 was removed on updating which >> should not be the case, should it? > > Removing packages no longer in the distribution your upgrading to is > quite common. > OK, this is all clear - *but*: is this behavior really ok? Isn't it affecting every single Debian user when upgrading from Jessie to Stretch if he is running postgresql + postgis?
Best, Juergen _______________________________________________ Pkg-grass-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-grass-devel
