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.
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
Pkg-grass-devel mailing list