Ytre Sandviken, 5045 Bergen, Norway
> roger.biv...@nhh.no
>
>
> From: Paul Ramsey
> Sent: 15 June 2023 21:26
> To: Roger Bivand
> Cc: geos-devel@lists.osgeo.org; Robert Hijmans; Edzer Pebesma
> Subject: Re: [geos-devel] 3.12.0beta1
>
>
>
>> On Jun
...@nhh.no
From: Paul Ramsey
Sent: 15 June 2023 21:26
To: Roger Bivand
Cc: geos-devel@lists.osgeo.org; Robert Hijmans; Edzer Pebesma
Subject: Re: [geos-devel] 3.12.0beta1
> On Jun 15, 2023, at 12:08 PM, Roger Bivand wrote:
>
> Paul, will try tomorrow m
> On Jun 15, 2023, at 12:08 PM, Roger Bivand wrote:
>
> Paul, will try tomorrow morning my time. Does this 3.11 contain the fix for
> gcc 13 - I had to switch to devel on upgrading to Fedora 38 so if that commit
> is also present here, it should be feasible, if not rather harder.
There are
Paul, will try tomorrow morning my time. Does this 3.11 contain the fix for gcc
13 - I had to switch to devel on upgrading to Fedora 38 so if that commit is
also present here, it should be feasible, if not rather harder.
Roger
--
Roger Bivand
Emeritus Professor
Norwegian School of Economics
Roger, if you could check the current 3.11 branch against your tests,
that would be very helpful.
https://github.com/libgeos/geos/tree/3.11
There is a patch in there for an issue that appeared in some very rare
cases in PostGIS that I think might be an issue in your use cases, and
I'd like to
> On Jun 14, 2023, at 1:26 AM, Roger Bivand wrote:
>
> Thanks, Paul, for responding so quickly.
>
> Having built GEOS with
> https://github.com/pramsey/geos/tree/main-collection-overlay, the issues in
> released and development versions of R package terra appear resolved.
Super, thanks
Thanks, Paul, for responding so quickly.
Having built GEOS with
https://github.com/pramsey/geos/tree/main-collection-overlay, the issues in
released and development versions of R package terra appear resolved.
The sf package remains unaffected by 3.12.
Roger
--
Roger Bivand
Emeritus
I have taken a swipe at it here.
https://github.com/libgeos/geos/pull/923
> On Jun 12, 2023, at 6:01 AM, Daniel Baston wrote:
>
> Thanks for raising this. There was some discussion of the issue at
> https://github.com/libgeos/geos/issues/797 and other tickets linked from
> there, but it
Thanks for raising this. There was some discussion of the issue at
https://github.com/libgeos/geos/issues/797 and other tickets linked from
there, but it was never really resolved.
Dan
On Mon, Jun 12, 2023 at 8:52 AM Roger Bivand wrote:
> An R packages built against GEOS is showing new test
An R packages built against GEOS is showing new test failures with 3.12.0beta1.
The important terra package fails first at a union on a buffered object, other
failures may occur later, but testing stops at first error. The error is:
Error: IllegalArgumentException: Overlay input is
> /build/geos-3.12.0~beta1/include/geos/coverage/CoverageRingEdges.h:76:
> warning: found documented return type for
> geos::coverage::CoverageRingEdges::CoverageRingEdges that does not
> return
> anything
Should be good now.
___
test_docs fails:
test 466
Start 466: test_docs
466: Test command: /usr/bin/cmake "-D"
"DOXYGEN_LOGFILE="/build/geos-3.12.0~beta1/build/doxygen/doxygen.log""
"-P" "/build/geos-3.12.0~beta1/build/doxygen/check_doxygen_errors.cmake"
466: Working Directory:
> On Jun 8, 2023, at 9:16 AM, Sebastiaan Couwenberg wrote:
>
> On 6/8/23 18:00, Paul Ramsey wrote:
>> done
> Thanks.
>
> Can src/coverage/CoverageBoundarySegmentFinder.cpp be relicensed to match the
> rest of GEOS instead of JTS? Or should we expect more EPL-2.0 or EDL-1.0
> licensed files
On 6/8/23 18:00, Paul Ramsey wrote:
done
Thanks.
Can src/coverage/CoverageBoundarySegmentFinder.cpp be relicensed to
match the rest of GEOS instead of JTS? Or should we expect more EPL-2.0
or EDL-1.0 licensed files to get incorporated from JTS?
Kind Regards,
Bas
--
GPG Key ID:
done
curl -I https://download.osgeo.org/geos/geos-3.12.0beta1.tar.bz2
HTTP/2 200
server: nginx/1.18.0 (Ubuntu)
date: Thu, 08 Jun 2023 16:00:18 GMT
content-type: application/octet-stream
content-length: 6718651
last-modified: Wed, 07 Jun 2023 19:24:17 GMT
etag: "6480d961-6684bb"
accept-ranges:
If that's required I can do that now...
On Thu, Jun 8, 2023 at 8:58 AM Sebastiaan Couwenberg wrote:
>
> On 6/7/23 22:05, Paul Ramsey wrote:
> > First tagged release auto built and available at
> >
> > https://github.com/libgeos/geos/releases/tag/3.12.0beta1
> When can we expect the tarballs at:
On 6/7/23 22:05, Paul Ramsey wrote:
First tagged release auto built and available at
https://github.com/libgeos/geos/releases/tag/3.12.0beta1
When can we expect the tarballs at:
https://download.osgeo.org/geos/
?
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146
> On Jun 8, 2023, at 8:42 AM, Greg Troxel wrote:
>
> Paul Ramsey writes:
>
>>> On Jun 7, 2023, at 5:26 PM, Greg Troxel wrote:
>>>
>>> If I install the 3.12.0beta1 package, then the tests pass. So there is
>>> a bug, but it is that the tests appaprently refer to installed files,
>>> rather
Paul Ramsey writes:
>> On Jun 7, 2023, at 5:26 PM, Greg Troxel wrote:
>>
>> If I install the 3.12.0beta1 package, then the tests pass. So there is
>> a bug, but it is that the tests appaprently refer to installed files,
>> rather than being controlled to use only files in the build tree.
>
> On Jun 8, 2023, at 8:28 AM, Paul Ramsey wrote:
>
>> My only question then about 3.12.0beta1 is if the comings-and-goings
>> diff of .h files is what the authors intend.
>
> Probably! I’ll look at that diff.
Yep, all changes confirmed. We’re a header-happy project.
> On Jun 7, 2023, at 5:26 PM, Greg Troxel wrote:
>
> If I install the 3.12.0beta1 package, then the tests pass. So there is
> a bug, but it is that the tests appaprently refer to installed files,
> rather than being controlled to use only files in the build tree.
We had this out last
If I install the 3.12.0beta1 package, then the tests pass. So there is
a bug, but it is that the tests appaprently refer to installed files,
rather than being controlled to use only files in the build tree. This
requires alternate rpath processing, etc., and in the autoconf world is
usually
Paul Ramsey writes:
> First tagged release auto built and available at
>
> https://github.com/libgeos/geos/releases/tag/3.12.0beta1
distfile not found at standard release location but I fetched it
manually from github.
With the following changes, the package built. The Makefile is just the
First tagged release auto built and available at
https://github.com/libgeos/geos/releases/tag/3.12.0beta1
P.
> On Jun 7, 2023, at 11:00 AM, Regina Obe wrote:
>
> No objection from me :)
> Cut please
>
>> -Original Message-
>> From: geos-devel
No objection from me :)
Cut please
> -Original Message-
> From: geos-devel [mailto:geos-devel-boun...@lists.osgeo.org] On Behalf Of
> Paul Ramsey
> Sent: Wednesday, June 7, 2023 1:53 PM
> To: GEOS Development List
> Subject: [geos-devel] 3.12.0beta1
>
> Any objections to my cutting a
25 matches
Mail list logo
