Le 12/11/2016 à 09:05, 殷啟聰 a écrit :
> Hi Vincent,
> Thank you for the report. In fact I have patched
> libnative-platform-java/0.11-4 to work with gradle/2.13, see .
The fact is that this patch does not seem to be enough. Currently,
gradle/2.13 in testing/unstable do *not* work with
libnative-platform-java/0.11-4 (also in testing/unstable).
> Turns out the upstream developer suddenly renamed the class without
> any transition.
> I do not make sure this patch works for gradle/2.13 building all
> packages, but I can make sure that it works when building gradle/3.1-1
> using gradle/2.13.
> Now that everything is ready, we will upload gradle/3.1-1 soon, but
> I'm still waiting for Emmanuel's sponsor. Let's not flag
> libnative-platform-java/0.11-4 Breaks gradle (<< 3.1) for the time
> being, as it will render gradle and libnative-platform-java
The current situation generates FTBFS from other packages (including
gradle 2.13 itself). And it blocks development on other java software.
Do you know when gradle 3.1 will be uploaded? If it is longer that
one week, some other workarounds should be put in place in order to
get a working gradle in the archive in between (a libnative-plateform-java/
0.11-4+really0.10 for example)
Emmanuel: do you think that gradle 3.1 can be uploaded?
Vincent Danjean GPG key ID 0xD17897FA vdanj...@debian.org
GPG key fingerprint: 621E 3509 654D D77C 43F5 CA4A F6AE F2AF D178 97FA
Unofficial pkgs: http://moais.imag.fr/membres/vincent.danjean/deb.html
APT repo: deb http://people.debian.org/~vdanjean/debian unstable main
This is the maintainer address of Debian's Java team
debian-j...@lists.debian.org for discussions and questions.