From: Arun Isaac <arunisaac@systemreboot.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: 39204@debbugs.gnu.org
Subject: bug#39204: r-rgdal: Reading of vector GIS data causes segfault
Date: Fri, 21 Feb 2020 17:42:37 +0530 [thread overview]
Message-ID: <cu7k14grvey.fsf@systemreboot.net> (raw)
In-Reply-To: <CAJ3okZ3h_3HZ79T3WKmC68BzXeK6oBE8N9erxwG2gkycDVhbbg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 899 bytes --]
>> > 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
No, upstream says that both proj (aka proj6) and proj.4 are
supported. Quoting [1],
"From 'rgdal' 1.4.1, provision is made for 'PROJ6' accommodation, ..."
> The question is: why proj instead of proj.4 in libgeotiff?
> The bug [1] cannot be solved using proj.4, why?
proj and proj.4 are different versions of the same software, with proj
being the newer version. See
https://proj.org/faq.html#what-happend-to-proj-4 . I say we completely
deprecate our proj.4 package and replace all occurrences of proj.4 with
proj.
WDYT?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next prev parent reply other threads:[~2020-02-21 12:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 15:43 bug#39204: r-rgdal: Reading of vector GIS data causes segfault Wiktor Żelazny
2020-01-20 19:50 ` zimoun
2020-02-20 10:35 ` zimoun
2020-02-20 17:10 ` Arun Isaac
2020-02-21 11:19 ` zimoun
2020-02-21 12:12 ` Arun Isaac [this message]
2020-02-21 12:30 ` zimoun
2020-02-21 18:54 ` zimoun
2020-02-21 21:35 ` Arun Isaac
2020-02-21 22:14 ` zimoun
2020-02-21 18:53 ` zimoun
2020-02-21 21:40 ` Arun Isaac
2020-02-21 22:19 ` zimoun
2020-02-22 19:42 ` Arun Isaac
2020-02-24 11:33 ` zimoun
2020-02-24 19:09 ` Arun Isaac
2020-02-25 15:49 ` zimoun
2020-10-12 10:22 ` Arun Isaac
2020-10-12 16:23 ` Wiktor Żelazny
2020-10-13 4:21 ` Arun Isaac
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cu7k14grvey.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=39204@debbugs.gnu.org \
--cc=zimon.toutoune@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).