> Thanks, I was about to mention this. Normally libgeos_c.so.1 is
expected, not libgeos_c.so.0.
+1 to this issue. This forces a recompilation of PostGIS (and I guess
everything else) to test the new release, so unless the C API has
changed it's an unnecessary pain in the ass.
On Thu, Dec 3, 2020
Hi there,
> It's probably not complete, but it's got the big entries...
I reported a couple of issues on GEOS trac. Is that good or is there a
more convenient place to track OverlayNG issues?
On Thu, Aug 6, 2020 at 10:48 PM Paul Ramsey wrote:
>
> Here's a spreadsheet...
>
>
Great job. Thanks a lot, Paul and Martin.
I expect to have some spare time these following weeks, so with the
compile time switch I could start crashing Postgis and reporting
issues (or even PRs if I can).
On Wed, Jul 29, 2020 at 2:05 AM Regina Obe wrote:
>
> Enough yapping. Put in the
Yes, what Dan said is true.
After updating clang that false positive is gone and the build is
clean, but now a failure is accepted. Depending on useful it turns out
to be I might do some grep-foo to just throw the errors and summary in
the future.
On Tue, Mar 10, 2020 at 2:35 AM Daniel Baston
Hi,
I've run scan-build against the project and it shows ~30 issues,
some minor and some important.
I've created a PR addressing them (https://github.com/libgeos/geos/pull/238)
but there is still 12 more in case someone wants to have a look before
me (I'll try
to finish with them tomorrow).
On
Hi,
a quick heads up: Current GEOS / head breaks postgis topology tests
(https://trac.osgeo.org/geos/ticket/990). You might want to fix that
before releasing the beta.
Regards,
--
Raúl Marín Rodríguez
carto.com
___
geos-devel mailing list