Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[殷啟聰]

Hi Vincent,

Thanks for the patch, I think breaking libgradle-core-java is enough
as this is the very package that uses libnative-platform-java.

I'm uploading it soon.

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Vincent Danjean]

Package: libnative-platform-java
Followup-For: Bug #844021

  Hi,

  As already explained, as libnative-platform-java changed its ABI, the new
version does not work with (all) programs wrote for the previous version.
  In Debian, gradle is the only one reverse dependency of
libnative-platform-java (i.e. it is the only package that directly uses
libnative-platform-java).

  gradle 2.13 do not work with libnative-platform-java 0.11 (at least, not all
features of gradle can be used when libnative-platform-java 0.11 is intalled)
  But gradle 3.1 (currently in unstable) works with (and even requires)
libnative-platform-java 0.11.

  So, to close this bug, I propose this small patch:
diff --git a/debian/control b/debian/control
index 27cb23f..3b95fdd 100644
--- a/debian/control
+++ b/debian/control
@@ -19,6 +19,7 @@ Package: libnative-platform-java
 Architecture: all
 Depends: libnative-platform-jni (>= ${source:Version}), ${misc:Depends}
 Suggests: libnative-platform-java-doc
+Breaks: gradle (<< 3.1), libgradle-core-java (<< 3.1)
 Description: Java bindings for various native APIs
  A collection of cross-platform Java APIs for various native APIs.
  Supports OS X, Linux, Solaris and Windows.

  Applying it will ensure that, (when gradle and libnative-platform-java will
be migrated to testing) if a user does a partial upgrade from stable to
testing, it will not keep a (old) gradle with a (incompatible) new
libnative-platform-java package.

  Regards,
Vincent


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(200, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libnative-platform-java depends on:
ii  libnative-platform-jni  0.10+dfsg-2

libnative-platform-java recommends no packages.

libnative-platform-java suggests no packages.

-- no debconf information

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[殷啟聰]

Hi Vincent,

FYI, there's been a patch [1] in gradle/3.1-1 which disable the
buildSrc test during the build. It's this test who causes FTBFS

[1]: 
https://anonscm.debian.org/cgit/pkg-java/gradle.git/tree/debian/patches/disable_buildSrc_tests.patch?h=debian/3.1-1

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Vincent Danjean]

Le 14/11/2016 à 16:56, 殷啟聰 a écrit :
> Control: tags -1 moreinfo
> 
> Gradle 3.1 is now uploaded, looks like this bug is fixed?

The bug is not fixed (there is a incompatible change in the interface
without package rename).
However, for Debian, as gradle seems the only reverse dependency of
libnative-platform-java, this bug can probably be closed.

  Regards,
Vincent

-- 
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
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[殷啟聰]

Control: tags -1 moreinfo

Gradle 3.1 is now uploaded, looks like this bug is fixed?

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Emmanuel Bourg]

Le 13/11/2016 à 20:49, Vincent Danjean a écrit :

>   Emmanuel: do you think that gradle 3.1 can be uploaded?

I'll try to upload it today.

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Vincent Danjean]

  Hi,

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 [1].

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
> uninstallable.

  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?

  Regards,
Vincent

> [1]: 
> https://anonscm.debian.org/cgit/pkg-java/libnative-platform-java.git/tree/debian/additionalSrc/PosixFile.java?h=debian/0.11-4
> 


-- 
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
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[殷啟聰]

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 [1].
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
uninstallable.

[1]: 
https://anonscm.debian.org/cgit/pkg-java/libnative-platform-java.git/tree/debian/additionalSrc/PosixFile.java?h=debian/0.11-4

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Vincent Danjean]

Le 11/11/2016 à 22:38, Emmanuel Bourg a écrit :
> Thank you for the report Vincent. libnative-platform-java/0.11 should
> probably declare that it breaks gradle (<< 3.1~).

The rebuild of gradle 2.13 breaks during tests:
[...]
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.
[...]

Is there an easy way to (temporary) disable tests in gradle build?

I would like to try:
- first: rebuild gradle 2.13
  * without tests
  * with libnative-platform-java/0.11 installed
  * using the gradle version in sid
- then: rebuild gradle 2.13
  * with tests
  * with libnative-platform-java/0.11 installed
  * using the previous gradle build

but I do not know how/what to desactivate the (currently failing)
tests in the first build.

  Regards,
Vincent

> Emmanuel Bourg
> 


-- 
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
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Emmanuel Bourg]

Thank you for the report Vincent. libnative-platform-java/0.11 should
probably declare that it breaks gradle (<< 3.1~).

Emmanuel Bourg

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#844021: libnative-platform-java 0.11-4 is not compatible with programs built with 0.10*

[Vincent Danjean]

Package: libnative-platform-java
Version: 0.11-4
Severity: serious
Justification: makes other package FTBFS

  Hi,

  gradle in unstable works with libnative-platform-java 0.10+dfsg-2 but does
not work with libnative-platform-java 0.11-4.

  A detailed explaination for gradle can be seen in #844020.

  This problematic situation leads to several packages FTBFS, at
least htsjdk (#843686) and gradle itself.

  Normaly, if a new version of a library do not works, by design,
with program compiled with the old version, a package rename (and
an SONAME bump for ELF libraries) is required in order to avoid
to silently break reverse dependencies.
  I do not know libnative-platform-java enough to know if this
breakage is known and normal (i.e. a package rename should have
been done) or if this is a plain bug.

  Regards,
Vincent


-- System Information:
Debian Release: stretch/sid
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'unstable'), (500, 'testing'), 
(200, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armel, mipsel

Kernel: Linux 4.8.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages libnative-platform-java depends on:
ii  libnative-platform-jni  0.10+dfsg-2

libnative-platform-java recommends no packages.

libnative-platform-java suggests no packages.

-- no debconf information

__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.