From mboxrd@z Thu Jan 1 00:00:00 1970 From: zimoun Subject: bug#39204: r-rgdal: Reading of vector GIS data causes segfault Date: Tue, 25 Feb 2020 16:49:34 +0100 Message-ID: References: <20200120154302.ijni47ou4fk4wd77@wzguix> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:35436) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j6cTD-0004Yc-4u for bug-guix@gnu.org; Tue, 25 Feb 2020 10:50:04 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j6cTB-00050W-UU for bug-guix@gnu.org; Tue, 25 Feb 2020 10:50:03 -0500 Received: from debbugs.gnu.org ([209.51.188.43]:50041) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j6cTB-00050Q-Qj for bug-guix@gnu.org; Tue, 25 Feb 2020 10:50:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1j6cTB-00056V-KH for bug-guix@gnu.org; Tue, 25 Feb 2020 10:50:01 -0500 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane-mx.org@gnu.org Sender: "bug-Guix" To: Arun Isaac Cc: 39204@debbugs.gnu.org Hi Arun, On Mon, 24 Feb 2020 at 20:10, Arun Isaac wrote: > > But as we have talked before, there is an issue about the upstream > > test suite of the package (point 1. of [1]). So I am investigating... > > Ah, I understand our miscommunication now. You have been talking about > point 1 (bug in upstream test suite) and I've been talking about point 2 > (segmentation fault when loading vector data). Yes, replacing proj.4 > with proj only addresses point 2, not point 1. It is not segfaulting anymore, I agree. But is it enough to know that everything is ok and the package is not broken? I am mean looking at the output of the 'check' phase (see [1]), it displays a diff and I am not confident if it is good or not. That's why I did not confirm that changing from proj.4 to proj works. Maybe I mispelled "error" in my previous answer and the correct words seem "I get an lengthy message and I do not know if it is ok." :-) [1] https://debbugs.gnu.org/cgi/bugreport.cgi?bug=39204#26 Cheers, simon