[postgis-devel] Odd behavior in an upgrade

[Sebastiaan Couwenberg]

On 12-10-15 23:17, Michael Brannigan wrote:
> liblwgeom-2.1.7:amd64 (2.1.7+dfsg-3~94.git954a8d0.pgdg12.4+1,
> 2.1.8+dfsg-1~95.git18216c0.pgdg12.4+1),
> postgresql-9.3-postgis-scripts:amd64
> (2.1.7+dfsg-3~94.git954a8d0.pgdg12.4+1,
> 2.1.8+dfsg-5~97.git43a09cc.pgdg12.4+1),
> 
> ​After upgrading, the following error messages were in my application logs:
> django.db.utils.OperationalError: could not load library
> "/usr/lib/postgresql/9.3/lib/postgis-2.1.so": liblwgeom-2.1.7.so: cannot
> open shared object file: No such file or directory

There was bug in the pgApt postgis package that Markus fixed in -5.

> ​It is almost as if the dependency of postgresql-9.3-postgis-2.1 was
> incorrect with liblwgeom-2.1.7 or that postgresql-9.3-postgis-2.1 needed to
> b​e upgraded, but apt-get upgrade didn't upgrade it in the first place.

The dependency was most likely incorrect because in pgApt
liblwgeom-2.1.7 included the 2.1.8 library, it should have been fixed
with this change (only required for the messed up pgApt packages):

 postgis (2.1.8+dfsg-5) UNRELEASED; urgency=medium

   * Add a Breaks+Replaces against liblwgeom-2.1.7 (>> 2.1.8) which
     erroneously shipped a 2.1.8 file.

  -- Markus Wanner <markus at bluegap.ch>  Fri, 18 Sep 2015 14:02:41 +0200

This kind of upgrade issues are the price to pay for using 3rd party
repositories that aren't as well integrated into the distribution as the
official archives.

Kind Regards,

Bas

-- 
 GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146  50D1 6750 F10A E88D 4AF1