> 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
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:
> 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 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:
> 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
> 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
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:
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 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
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:
> /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.
___
11 matches
Mail list logo
