Re: Moving JTS 1.13 to unstable, h2database & elasticsearch need changes
On 10-11-15 22:26, Sebastiaan Couwenberg wrote:
> On 10-11-15 17:33, Markus Koschany wrote:
>> Am 07.11.2015 um 16:46 schrieb Sebastiaan Couwenberg:
>>> JTS 1.13 has been available in experimental for some time now,
>>> and I'd like to move it to unstable soon. We have GEOS 3.5.0
>>> in unstable for some time too, but JTS 1.13 it's a port of is
>>> not in unstable yet.
>>>
>>> Because the two libjts-java reverse dependencies are both
>>> maintained by the Java team, I'd like to coordinate the jts
>>> transition with the h2database & elasticsearch maintainers.
>>>
>>> The h2database won't need 04-jts-compatibility.patch any more,
>>> upstream already uses JTS 1.13 for its builds.
>>>
>>> Because jts (1.13+ds-1~exp1) now uses maven-debian-helper,
>>> elasticsearch doesn't need to install the jar manually any
>>> more.
>>>
>>> Patches for both are attached.
>>>
>>> If we can coordinate the transition on this list we can spare
>>> us two RC bugs when JTS 1.13 is uploaded to unstable.
>
>> thanks for the heads-up. I think elasticsearch isn't critical
>> since it won't be part of the next stable release anyway. [1] I
>> can apply the patch for h2database. Just go ahead with your
>> upload.
>
> jts (1.13+ds-1) has just been uploaded to unstable.
>
> I'll file a bug for elasticsearch with the patch too.
I found two more packages that require JTS: spatial4j & spatial4j-0.4.
The latter is required for elasticsearch.
Neither of the spatial4j packages are team maintained, it seems a good
idea to move them to pkg-java like elasticsearch.
I've added usertags to the JTS 1.13 related bugs, they can now easily
be found via:
https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=jts-1.13;users=debian-gis@lists.debian.org
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Reply to: