Debian Bug report logs - #441797
postgresql-8.2-postgis: upgrade to 1.3.1 make old databases unusable

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Ingo Klinkmann <ingo@logix-tt.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: postgresql-8.2-postgis: upgrade to 1.3.1 make old databases unusable

Date: Tue, 11 Sep 2007 11:37:18 +0200

Package: postgresql-8.2-postgis
Version: 1.3.1-1
Severity: important

Hi,

the uprade to postgis 1.3.1 makes the old databases unusable, because
the databases are not upgradet to the new liblwgeom.so
The /usr/share/postgresql-8.2-postgis/lwpostgis_upgrade.sql script does
not work:

psql:/usr/share/postgresql-8.2-postgis/lwpostgis_upgrade.sql:38: ERROR: could not access file "/usr/lib/postgresql/8.2/lib/liblwgeom.so.1.2": No such file or directory

ingo

-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (860, 'unstable'), (850, 'testing'), (800, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.22.1 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages postgresql-8.2-postgis depends on:
ii  libc6                         2.6.1-2    GNU C Library: Shared libraries
ii  libgeos-c1                    2.2.3-3    Geometry engine for Geographic Inf
ii  postgis                       1.3.1-1    geographic objects support for Pos
ii  postgresql-8.2                8.2.4-3    object-relational SQL database, ve
ii  proj                          4.5.0-2    Cartographic projection filter and

postgresql-8.2-postgis recommends no packages.

-- no debconf information

Message #12 received at 441797@bugs.debian.org (full text, mbox, reply):

From: Ingo Klinkmann <ingo@logix-tt.com>

To: 441797@bugs.debian.org

Subject: Re: postgresql-8.2-postgis: upgrade to 1.3.1 make old database unusable

Date: Tue, 11 Sep 2007 13:36:15 +0200

a quick solution is to manualy copy
the liblwgeom.so.1.2 from the lenny-package to
/usr/lib/postgresql/8.2/lib/liblwgeom.so.1.2

then run /usr/share/postgresql-8.2-postgis/lwpostgis_upgrade.sql
for every old postgis-database.

After this you can delete liblwgeom.so.1.2

Message #17 received at 441797@bugs.debian.org (full text, mbox, reply):

From: Francesco Paolo Lovergine <frankie@debian.org>

To: Debian Bug Tracking System <441797@bugs.debian.org>

Subject: Note for postgis upgrade improvement

Date: Wed, 21 May 2008 13:25:53 +0200

Package: postgis
Followup-For: Bug #441797

[Summary from a past discussion about the subject with Kobold]

Just for note, Postgis has a soft and an hard upgrading script. It is
required to call one of this script at every upgrade. An explicit note
about that would be adequate.
It does not suffice in general anyway because existent db are intimately linked
to the postgis extension that created that db (both ABI and API).

A proper major upgrade should be performed with a dirty trick,
that is maintaining the past shared lib (eg. /usr/lib/postgresql/8.2/lib/liblwgeom.so.1.2)
in order to allow old db to still work properly. To do that, 
the postinst should install its shared lib starting from a private
copy on-fly and do not remove them at package removing (but for purging).
That would allow old db to still work in case of postgis (not postgres) upgrade.
It is still a partial solution because it does not protect against 
postgres changes, but really better than nothing at all.


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.25-2-686 (SMP w/1 CPU core)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Message #24 received at 441797@bugs.debian.org (full text, mbox, reply):

From: "Francesco P. Lovergine" <frankie@debian.org>

To: Paolo Cavallini <cavallini@faunalia.it>

Cc: DebianGIS <pkg-grass-general@lists.alioth.debian.org>, 441797@bugs.debian.org, 441797-submitter@bugs.debian.org, madcoder@debian.org

Subject: Re: [DebianGIS] [Fwd: [DebianGIS-dev] postgis REMOVED from testing]

Date: Sat, 7 Jun 2008 11:20:50 +0200

severity 441797 important
severity 441794 important
thanks

On Sat, Jun 07, 2008 at 09:41:35AM +0200, Paolo Cavallini wrote:
> Hi all.
> Could someone please update us about the state of PostGIS, and the
> prospects for the near future?
> Thanks a lot.
> pc
> 

Have a look to the main bug 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441797

I have a couple of ideas about that:

1. it's not a true issue for etch->lenny because postgres versions
   are different and users can easily maintain the old version
   and migrate by hard upgrade script, as documented in the
   README file. So this is not a RC bug.

2. 1.3.1 is not more present in the archive, so that does not break
   anything currently.

3. We need to prepare a migration framework that uses the trick
   I shown in the report. 
   Thanks strk for a past discussion about that :-)
   That should allow a more soft migration in some cases, but anyway
   Postgis REQUIRES running soft/hard upgrades scripts for all
   its databases, and that is a MUST and users are warned about
   that in README.Debian since ages. There's not a silver bullet.

On this basis I would reduce the severity of those bugs to important.


> -------- Messaggio Originale  --------
> Oggetto: [DebianGIS-dev] postgis REMOVED from testing
> Data: Fri, 06 Jun 2008 16:39:22 -0600
> Da: Debian testing watch <noreply@henning.makholm.net>
> 
> FYI: The status of the postgis source package
> in Debian's testing distribution has changed.
> 
>   Previous version: 1.3.3-1
>   Current version:  (not in testing)
>   Hint: (no removal hint found)
> 

-- 
Francesco P. Lovergine

Message #32 received at 441797@bugs.debian.org (full text, mbox, reply):

From: Pierre Habouzit <madcoder@debian.org>

To: Paolo Cavallini <cavallini@faunalia.it>, DebianGIS <pkg-grass-general@lists.alioth.debian.org>, 441797@bugs.debian.org, 441797-submitter@bugs.debian.org

Subject: Re: [DebianGIS] [Fwd: [DebianGIS-dev] postgis REMOVED from testing]

Date: Sat, 07 Jun 2008 17:33:54 +0200

[Message part 1 (text/plain, inline)]

On Sat, Jun 07, 2008 at 09:20:50AM +0000, Francesco P. Lovergine wrote:
> severity 441797 important
> severity 441794 important
> thanks
> 
> On Sat, Jun 07, 2008 at 09:41:35AM +0200, Paolo Cavallini wrote:
> > Hi all.
> > Could someone please update us about the state of PostGIS, and the
> > prospects for the near future?
> > Thanks a lot.
> > pc
> > 
> 
> Have a look to the main bug 
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=441797
> 
> I have a couple of ideas about that:
> 
> 1. it's not a true issue for etch->lenny because postgres versions
>    are different and users can easily maintain the old version
>    and migrate by hard upgrade script, as documented in the
>    README file. So this is not a RC bug.
> 
> 2. 1.3.1 is not more present in the archive, so that does not break
>    anything currently.
> 
> 3. We need to prepare a migration framework that uses the trick
>    I shown in the report. 
>    Thanks strk for a past discussion about that :-)
>    That should allow a more soft migration in some cases, but anyway
>    Postgis REQUIRES running soft/hard upgrades scripts for all
>    its databases, and that is a MUST and users are warned about
>    that in README.Debian since ages. There's not a silver bullet.

  Well I was under the impression in the bug log that it also needed to
keep an old version of a library during the upgrade wich is at best
sloppy. If that's not needed, then yes, important works for me.

  Note that you have another RC bug open that is quite trivial to fix on
its own. We try to release, please keep your packages clean.

-- 
·O·  Pierre Habouzit
··O                                                madcoder@debian.org
OOO                                                http://www.madism.org

[Message part 2 (application/pgp-signature, inline)]

Message #44 received at 441797@bugs.debian.org (full text, mbox, reply):

From: "Francesco P. Lovergine" <frankie@debian.org>

To: Paolo Cavallini <cavallini@faunalia.it>, DebianGIS <pkg-grass-general@lists.alioth.debian.org>, 441797@bugs.debian.org, 441797-submitter@bugs.debian.org

Subject: Re: [DebianGIS-dev] Bug#441797: [DebianGIS] [Fwd: postgis REMOVED from testing]

Date: Sun, 8 Jun 2008 11:09:48 +0200

On Sat, Jun 07, 2008 at 05:33:54PM +0200, Pierre Habouzit wrote:
> > 3. We need to prepare a migration framework that uses the trick
> >    I shown in the report. 
> >    Thanks strk for a past discussion about that :-)
> >    That should allow a more soft migration in some cases, but anyway
> >    Postgis REQUIRES running soft/hard upgrades scripts for all
> >    its databases, and that is a MUST and users are warned about
> >    that in README.Debian since ages. There's not a silver bullet.
> 
>   Well I was under the impression in the bug log that it also needed to
> keep an old version of a library during the upgrade wich is at best
> sloppy. If that's not needed, then yes, important works for me.
> 

The resons for that is that the db contains a reference to library
used for building it. If one would maintain the db without running
the upgrade script, keeping the past libraries around is a way
to do that. That would not protect against uncompatible 
changes in the postgis schema anyway. So that trick helps but 
it's a partial solution (and for sure not elegant, a dirty trick as I said).

>   Note that you have another RC bugopen that is quite trivial to fix on
> its own. We try to release, please keep your packages clean.
> 

The other bug is fixed by yesterday upload.

-- 
Francesco P. Lovergine

Message #54 received at 441797-close@bugs.debian.org (full text, mbox, reply):

From: Francesco Paolo Lovergine <frankie@debian.org>

To: 441797-close@bugs.debian.org

Subject: Bug#441797: fixed in postgis 1.3.3-3

Date: Wed, 25 Jun 2008 12:02:11 +0000

Source: postgis
Source-Version: 1.3.3-3

We believe that the bug you reported is fixed in the latest version of
postgis, which is due to be installed in the Debian FTP archive:

libpostgis-java_1.3.3-3_all.deb
  to pool/main/p/postgis/libpostgis-java_1.3.3-3_all.deb
postgis_1.3.3-3.diff.gz
  to pool/main/p/postgis/postgis_1.3.3-3.diff.gz
postgis_1.3.3-3.dsc
  to pool/main/p/postgis/postgis_1.3.3-3.dsc
postgis_1.3.3-3_i386.deb
  to pool/main/p/postgis/postgis_1.3.3-3_i386.deb
postgresql-8.3-postgis_1.3.3-3_i386.deb
  to pool/main/p/postgis/postgresql-8.3-postgis_1.3.3-3_i386.deb



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 441797@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Francesco Paolo Lovergine <frankie@debian.org> (supplier of updated postgis package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.8
Date: Mon, 09 Jun 2008 13:03:04 +0200
Source: postgis
Binary: postgresql-8.3-postgis postgis libpostgis-java
Architecture: source i386 all
Version: 1.3.3-3
Distribution: unstable
Urgency: low
Maintainer: Francesco Paolo Lovergine <frankie@debian.org>
Changed-By: Francesco Paolo Lovergine <frankie@debian.org>
Description: 
 libpostgis-java - geographic objects support for PostgreSQL -- JDBC support
 postgis    - geographic objects support for PostgreSQL -- common files
 postgresql-8.3-postgis - geographic objects support for PostgreSQL 8.3
Closes: 441794 441797
Changes: 
 postgis (1.3.3-3) unstable; urgency=low
 .
   * Added Vcs-* fields in debian/control.
   * Fixed download URL in debian/copyright.
   * Now it installs the shared lib in a private postgis path and makes a
     hard link in the postgres library path at configure time. That would
     allow coexistence of different flavors of the library which could be
     used by different DBs at run-time and allowing soft/hard-upgrade scripts
     working. (closes: #441794, #441797)
Checksums-Sha1: 
 dccc477e39938db7a0f861072e440ac7e93de616 1495 postgis_1.3.3-3.dsc
 d8ac42e3b5935c067e9e82b408a02fcbe5f8a5cd 9921 postgis_1.3.3-3.diff.gz
 1aac36f9567d0ff84c029656462d6eb7a449e172 442788 postgresql-8.3-postgis_1.3.3-3_i386.deb
 c711de0ebbe6567b7473093a77b3b01fc9c5f1dc 210444 postgis_1.3.3-3_i386.deb
 83c0bf63a514580b0dd32a8d5b63f6bed90a1633 317936 libpostgis-java_1.3.3-3_all.deb
Checksums-Sha256: 
 adf0f2fa86e9877bc4559a8bec2bff74b88738001cdfae8e71fa9f162a64543a 1495 postgis_1.3.3-3.dsc
 3ee9069b3e3e26e0173597c474afbacb996b907cc3b04c0e3797e0f49809e025 9921 postgis_1.3.3-3.diff.gz
 d88808d695fdf211683ff9d92b5208a949d3485d1ff9dbda0377dbf4a9e0e14e 442788 postgresql-8.3-postgis_1.3.3-3_i386.deb
 568ca5b04500c128daf14bd2b7116ed901d764cede9059c7747c503ec78c4ccf 210444 postgis_1.3.3-3_i386.deb
 2dbab7a77d9331c23f64f79a9fb2b9d0b5a5cf7093e30bf3ea04c2feefda5681 317936 libpostgis-java_1.3.3-3_all.deb
Files: 
 54eef8f9b2731e6357d10b4d28a05767 1495 misc optional postgis_1.3.3-3.dsc
 eecf363ddd513baa2695f6c7b2bc8b45 9921 misc optional postgis_1.3.3-3.diff.gz
 69f70e41ebfc78c1271fb06d387bf1c0 442788 misc optional postgresql-8.3-postgis_1.3.3-3_i386.deb
 f40af243e7f8d9420734d12f9eafc998 210444 misc optional postgis_1.3.3-3_i386.deb
 1c5842fda9ba52e5a8f7bea6febd992d 317936 science optional libpostgis-java_1.3.3-3_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkhiMlMACgkQpFNRmenyx0fGqQCfWhSlAwzomDn7GEGn1NdC7+3H
O5cAmweDdmdZQyy4hN6SSdniSBvFBsfJ
=WohA
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.