[gdal-dev] upgrading to gdal-2.4.2 on debian:buster

[Jon Seymour]

Hello all,

I have been using gdal-2.4.0 on debian buster for some time now. I ran
across an issue with the vsis3 driver and its interplay with the vrt driver
(AWS container credentials were expiring after 6 hours). This issue is
fixed in 2.4.2 so I wanted to upgrade my system to gdal-2.4.2 so I could
take advantage of the fix.

What I am looking for is a sketch of the most correct and efficient way for
me to do this.

What I have tried is the following:

I downloaded 2.4.2 from source and rebuilt it with the
--with-python=/usr/bin/python3 configuration option

This resulted in an installation in /usr/local. I noticed that another
dependency (the .deb package python-opencv) installs gdal-2.4.0 in
/usr/lib. I updated the symbolic link in /usr/lib to refer to the version
of libgdal.so.20 in /usr/local/lib and this worked for gdalinfo, it didn't
work for my larger program:

ERROR 6: Unable to load PROJ.4 library (libproj.so), creation of
OGRCoordinateTransformation failed.

Presumably this resulted from having a mix of 2.4.0 and 2.4.2 artefacts in
the same path.

I am now in the process of rebuilding the source with a prefix of /usr so
that I can at least replace the /usr version of the binary with my locally
built versions, but I don't know yet if that will work better.

I also experimented with rebuilding the 2.4.2 .deb package from the 2.4.2
tag of  https://salsa.debian.org/debian-gis-team/gdal but ran into problems
with an unresolved dependency (libodgi) which I wasn't able to resolve
trivially so I abandoned that attempt.

What is the best way for me to upgrade gdal from 2.4.0 to 2.4.2 on a debian
buster system?

jon.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20200206/ae7baa98/attachment.html>