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 databas
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 14
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
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
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
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
>
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 w
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 p
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 librar
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.
10 matches
Mail list logo