Subject: bug#39204: r-rgdal: Reading of vector GIS data causes segfault

From: zimoun <[email-masked]>
Date: Fri, 21 Feb 2020 12:19:11 +0100

Hi Arun,

On Thu, 20 Feb 2020 at 18:11, Arun Isaac <[email-masked]> wrote:

> >  2. a regression of r-rgdal introduced by your commit
> > f9d328833fc1f5d0fb76b61b12d1a3cb013932e6
>
> Replacing proj.4 with proj in the r-rgdal package seems to fix this
> regression. Can you confirm?

Maybe, but it is not what the user expects. Upstream explicitly
mentions proj.4, see [1].

[1] https://cloud.r-project.org/web/packages/rgdal/index.html

which is reflected by:

--8<---------------cut here---------------start------------->8---
$ guix show r-rgdal
name: r-rgdal
version: 1.4-8
outputs: out
systems: x86_64-linux i686-linux
dependencies: [email-masked] [email-masked] [email-masked] [email-masked] [email-masked]
location: gnu/packages/cran.scm:15897:2
homepage: http://rgdal.r-forge.r-project.org
license: GPL 2+
synopsis: Bindings for the Geospatial Data Abstraction Library
description: This package provides bindings to the Geospatial Data
+ Abstraction Library (GDAL) and access to projection/transformation
+ operations from the PROJ.4 library.
--8<---------------cut here---------------end--------------->8---

The question is: why proj instead of proj.4 in libgeotiff?
The bug [1] cannot be solved using proj.4, why?

[2] https://github.com/OSGeo/libgeotiff/issues/22

All the best,
simon