Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-10 Thread Christoph Berg
Re: Bas Couwenberg 2018-01-10 <393ec00aaa425fd76e604a85221c2...@xs4all.nl> > > 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? > > Upgrades of postgis

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-10 Thread Bas Couwenberg
On 2018-01-10 10:22, Jürgen Fuchsberger wrote: 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

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-10 Thread Jürgen Fuchsberger
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

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-10 Thread Bas Couwenberg
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

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Jürgen Fuchsberger
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,

Bug#886742: [INFO] Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Francesco P. Lovergine
On Tue, Jan 09, 2018 at 02:37:44PM +0100, Jürgen Fuchsberger wrote: > >> What did you try, and what didn't work? > > > > Probably pg_upgradecluster, and that is not supported for databases with > > the postgis extension. > > > Exactly. Just wanted to point out that upgrading was no possibility >

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Jürgen Fuchsberger
On 2018-01-09 14:16, Bas Couwenberg wrote: > On 2018-01-09 14:08, Christoph Berg wrote: >> Re: Juergen Fuchsberger 2018-01-09 >> <20180109130149.17725.10545.report...@wegc203058.uni-graz.at> >>> Due to missing postgresql-9.4-postgis-2.1 in stretch, a postgis enabled >>> database becomes corrupt

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Bas Couwenberg
On 2018-01-09 14:08, Christoph Berg wrote: Re: Juergen Fuchsberger 2018-01-09 <20180109130149.17725.10545.report...@wegc203058.uni-graz.at> 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

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Christoph Berg
Control: tags -1 moreinfo Re: Juergen Fuchsberger 2018-01-09 <20180109130149.17725.10545.report...@wegc203058.uni-graz.at> > 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

Bug#886742: postgresql-9.4-postgis-2.1 missing in stretch

2018-01-09 Thread Juergen Fuchsberger
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.