> It kept spitting the error during the check phase, but I was
> time-machined some months into the past. Maybe with current Guix version
> the issue does not occur. I will check it out this or the next week.
Sure, check it out and let me know.
> Thank you for your work on this issue.
My pleasu
On Mon, Oct 12, 2020 at 03:52:30PM +0530, Arun Isaac wrote:
> I pushed to master, my commit replacing proj.4 with proj.
Hi Arun,
Believe it or not, but on Friday I tried the same thing. First,
replacing proj with proj.4 in GDAL, which declined to compile, demanding
version 6, then replacing proj
Hi,
I pushed to master, my commit replacing proj.4 with proj. This fixes the
segfault issue. I also updated the package. If the issue with the check
phase still persists, please open a separate issue.
Cheers!
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 u
> First, your patch does not apply. Because it should be line 21 and not
> 18 for the addition of your Copyright.
Sorry, I should have rebased with master.
> 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...
Hi Arun,
First, your patch does not apply. Because it should be line 21 and not
18 for the addition of your Copyright.
On Sat, 22 Feb 2020 at 20:42, Arun Isaac wrote:
> $ ./pre-inst-env guix build r-rgdal
I get the same message than I previously sent:
https://debbugs.gnu.org/cgi/bugreport.cg
Let's try to debug the problem you are facing. After applying the
attached patch, please provide the complete outputs of the following
commands. If the output is too long, feel free to send it as an email
attachment.
$ ./pre-inst-env guix build r-gdal
$ ./pre-inst-env guix environment --containe
On Fri, 21 Feb 2020 at 22:40, Arun Isaac wrote:
> > You mean:
> >
> > guix build --with-input=proj.4=proj r-rgdal
> >
> > then it compiles a lot... and I do not understand why gdal is
> > recompiled. Anyway!
>
> Your command recursively replaces proj.4 with proj. So, some dependency
> of gdal m
On Fri, 21 Feb 2020 at 22:36, Arun Isaac wrote:
> > For other packages than r-rgdal depending on proj.4:
> > - ok with proj instead of proj.4: osm2pgsql, xygrib and libgaiagraphics.
> > - not ok: libspatialite and libosmium
>
> Indeed, all packages don't yet support proj. We'll have to keep pro
> You mean:
>
> guix build --with-input=proj.4=proj r-rgdal
>
> then it compiles a lot... and I do not understand why gdal is
> recompiled. Anyway!
Your command recursively replaces proj.4 with proj. So, some dependency
of gdal might have been modified resulting in a rebuild of gdal.
> So afte
> For other packages than r-rgdal depending on proj.4:
> - ok with proj instead of proj.4: osm2pgsql, xygrib and libgaiagraphics.
> - not ok: libspatialite and libosmium
Indeed, all packages don't yet support proj. We'll have to keep proj.4
around until their upstreams adds support for proj.
>
Hi Arun,
On Fri, 21 Feb 2020 at 13:13, Arun Isaac wrote:
> 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
Hi Arun,
On Thu, 20 Feb 2020 at 18:11, Arun Isaac 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?
You mean:
guix build --with-i
On Fri, 21 Feb 2020 at 13:13, Arun Isaac 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
>> > 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,
Hi Arun,
On Thu, 20 Feb 2020 at 18:11, Arun Isaac 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 us
> There is 2 issues in this bug report:
>
> 1. the `check' phase is failing but the build ends with "success".
I haven't investigated why this is happening.
> 2. a regression of r-rgdal introduced by your commit
> f9d328833fc1f5d0fb76b61b12d1a3cb013932e6
Replacing proj.4 with proj in the r-rg
Hi Arun,
There is 2 issues in this bug report:
1. the `check' phase is failing but the build ends with "success".
2. a regression of r-rgdal introduced by your commit
f9d328833fc1f5d0fb76b61b12d1a3cb013932e6
About the point 1., here is what happens:
> --8<---cut here-
Hi,
Thank you for reporting.
The issue is that the error is not catched at build time. It is not
expected. This package should fail and not say "successfully built".
Well, this needs more investigation.
--8<---cut here---start->8---
$ guix build r-rgdal --c
Hi list,
The same behaviour on two machines.
To reproduce:
guix environment --container --ad-hoc r r-rgdal
Rscript -e 'library(rgdal); dsn <- system.file("vectors", package =
"rgdal")[1]; ogrInfo(dsn=dsn, layer="cities")'
Loading required package: sp
rgdal: version: 1.4-8, (SVN revision
20 matches
Mail list logo
