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

2016-11-21 Thread 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*

2016-11-14 Thread 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
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
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*

2016-11-13 Thread 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
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
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*

2016-11-11 Thread 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
<http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers>. 
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*

2016-11-11 Thread 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.

Bug#844020: gradle 2.13 in unstable do not work with libnative-platform-java 0.11

2016-11-11 Thread Vincent Danjean 
Package: gradle
Version: 2.13-4
Severity: serious
Justification: Generate FTBFS in other packages (and in gradle itself)

  Hi,

I'm not an expert of java/gradle but I package several java programs (mainly
within the debian-med team).

I'm working on #843686. It took me time to understand that
net.rubygrapefruit.platform.PosixFiles.stat comes from the
libnative-platform-java package that is pulled by gradle itself.

I suspected that gradle was built with libnative-platform-java 0.10 and
does not work with libnative-platform-java 0.11.

So, I tried to do a local rebuild of gradle itself, so that it "links"
correctly with the new libnative-platform-java version.

=> it fails. So, currently, gradle FTBFS (as htsjdk), and for the same
reason (see the gradle build log in my up-to-date sid chroot at the
end of this report)

On my system, I downgraded libnative-platform-java to 0.10 (thanks to
snapshots.debian.org). With this, htsjdk can be built.


  So, I think that, with the current (2.13-4) gradle version:
- currently gradle FTBFS
- some gradle features do not work (I do not know gradle enought to
  be able to say which ones exactly) 
  that leads to FTBFS of different packages (at least htsjdk #843686
  and gradle itself)
- gradle should have been more strict wrt to libnative-platform-java
  dependency. I.e, instead of
  Depends: libnative-platform-java (>= 0.10)
  it should have had
  Depends: libnative-platform-java (>= 0.10), libnative-platform-java (<< 0.11)
  (or libnative-platform-java should have done a library transition rename
  as the new version is not compatible with the previous one
  => I will also open a bug for libnative-platform-java )


  I saw in the git that you are working to package the 3.1 version
of gradle. However, as this bug has annoying side effects, it would
be great if you can try to upload a new version of gradle compiled
with libnative-platform-java 0.11.
  The difficulty will be that you will need that, as gradle use itself
to compile, you will need libnative-platform-java 0.10 installed
in your environment... :-( I do not know enought of gradle and
libnative-platform-java to know how to workaround this.

  Of course, if gradle 3.1 is to be uploaded very soon, you can
ignore this bug.

  Regards,
Vincent


Part of gradle 2.13-4 build log in current unstable:

[...]
gradle assemble startScripts javadocAll groovydocAll dslHtml samplesDocs -x 
:docs:releaseNotes -x :distributions:assemble --project-prop finalRelease=true 
--offline --stacktrace --gradle-user-home debian/.gradlehome --parallel 
--max-workers=1
Parallel execution is an incubating feature.
:buildSrc:clean UP-TO-DATE
:buildSrc:compileJava UP-TO-DATE
:buildSrc:compileGroovySLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in 
[jar:file:/usr/share/java/gradle-core.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in 
[jar:file:/usr/share/gradle/lib/gradle-core-2.13.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual binding is of type 
[org.gradle.logging.internal.slf4j.OutputEventListenerBackedLoggerContext]
warning: Implicitly compiled files were not subject to annotation processing.
  Use -proc:none to disable annotation processing or -implicit to specify a 
policy for implicit compilation.
1 warning

:buildSrc:processResources
:buildSrc:classes
:buildSrc:jar
:buildSrc:assemble
:buildSrc:compileTestJava UP-TO-DATE
:buildSrc:compileTestGroovy
:buildSrc:processTestResources
:buildSrc:testClasses
:buildSrc:test FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':test'.
> net.rubygrapefruit.platform.PosixFiles.stat(Ljava/io/File;)Lnet/rubygrapefruit/platform/PosixFile;

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':test'.
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:69)
at 
org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:46)
at 
org.gradle.api.internal.tasks.execution.PostExecutionAnalysisTaskExecuter.execute(PostExecutionAnalysisTaskExecuter.java:35)
at 
org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:68)
at 
org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:58)
at 
org.gradle.api.internal.tasks.execution.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:52)
at 
org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:53)
at

Bug#740955: maven: Maven 3.0.5 is not recognized as maven 3 (with pom.xml prerequisites)

2014-03-06 Thread Vincent Danjean 
Package: maven
Version: 3.0.5-1
Severity: important

  When a pom.xml project have the following lines:
prerequisites
maven3.0/maven
/prerequisites
then, maven from unstable fails with the following error:
vdanjean@eyak:~/debian/mainteneur/openhab/upstream/openhab$ mvn -e
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] 
[ERROR] BUILD FAILURE
[INFO] 
[INFO] Unable to build project 
'/home/vdanjean/debian/mainteneur/openhab/upstream/openhab/pom.xml; it requires 
Maven version 3.0
[INFO] 
[INFO] Trace
org.apache.maven.BuildFailureException: Unable to build project 
'/home/vdanjean/debian/mainteneur/openhab/upstream/openhab/pom.xml; it requires 
Maven version 3.0
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:499)
at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:391)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:272)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at 
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] 
[INFO] Total time:  1 second
[INFO] Finished at: Thu Mar 06 16:32:10 CET 2014
[INFO] Final Memory: 4M/118M
[INFO] 


  I do not have any problems to compile this maven project (openhab) with maven
from stable (maven 3.0.4-3)

  Regards,
Vincent


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

Kernel: Linux 3.12-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

Versions of packages maven depends on:
ii  default-jre [java5-runtime]  2:1.7-51
ii  default-jre-headless [java5-runtime-headless]2:1.7-51
ii  gcj-4.6-jre [java5-runtime]  4.6.4-2
ii  gcj-4.6-jre-headless [java5-runtime-headless]4.6.4-2
ii  gcj-4.7-jre [java5-runtime]  4.7.3-2
ii  gcj-4.7-jre-headless [java5-runtime-headless]4.7.3-2
ii  gcj-4.8-jre [java5-runtime]  4.8.2-15
ii  gcj-4.8-jre-headless [java5-runtime-headless]4.8.2-15
ii  gcj-jre [java5-runtime]  4:4.8.2-2
ii  gcj-jre-headless [java5-runtime-headless]4:4.8.2-2
ii  libaether-java   1.13.1-2
ii  libcommons-cli-java  1.2-3
ii  libcommons-codec-java1.9-1
ii  libcommons-httpclient-java   3.1-10.2
ii  libcommons-logging-java  1.1.3-1
ii  libguava-java15.0-2
ii  libplexus-cipher-java1.5-4
ii  libplexus-classworlds2-java  2.5.1-2
ii  libplexus-containers1.5-java 1.5.5-6
ii  libplexus-interpolation-java 1.19-1
ii  libplexus-sec-dispatcher-java1.3.1-6
ii  libplexus-utils2-java2.0.5-1
ii  libsisu-guice-java   3.1.9+dfsg-3
ii  libsisu-ioc-java 2.3.0-5
ii  libwagon2-java   2.5-1
ii  openjdk-6-jre [java5-runtime]6b30-1.13.1-1
ii  openjdk-6-jre-headless [java5-runtime-headless]  6b30-1.13.1-1
ii  openjdk-7-jre [java5-runtime]7u51-2.4.5-2
ii  openjdk-7-jre-headless [java5-runtime-headless]  7u51-2.4.5-2
ii  sun-java6-jre [java5-runtime-headless]   6.26-0squeeze1

maven recommends no packages.

maven suggests no packages.

-- no debconf information

__
This is the maintainer address of Debian's Java team
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-java-maintainers. 
Please use
debian-j...@lists.debian.org for