Bug#852640: apache-mime4j: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:apache-mime4j
Version: 0.7.2-4
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibapache-mime4j-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   jh_linkjars -i -O--buildsystem=maven
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install javadoc:aggregate
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install javadoc:aggregate 
-DskipTests -Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

Running org.apache.james.mime4j.dom.MessageServiceFactoryTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.009 sec - in 
org.apache.james.mime4j.dom.MessageServiceFactoryTest
Running org.apache.james.mime4j.dom.ExampleMessagesRoundtripTest
Tests run: 79, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.301 sec - in 
org.apache.james.mime4j.dom.ExampleMessagesRoundtripTest
Running org.apache.james.mime4j.dom.MessageCompleteMailTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.006 sec - in 
org.apache.james.mime4j.dom.MessageCompleteMailTest

Results :

Failed tests: 
  org.apache.james.mime4j.message.StringInputStreamTest#testBufferedRead 
AssertionFailedError

Tests run: 405, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache JAMES Mime4j Project  SUCCESS [  0.175 s]
[INFO] Apache JAMES Mime4j (Core) . SUCCESS [  6.578 s]
[INFO] Apache JAMES Mime4j (DOM) .. FAILURE [  5.005 s]
[INFO] Apache JAMES Mime4j (Storage) .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 14.299 s
[INFO] Finished at: 2017-01-24T00:47:16+00:00
[INFO] Final Memory: 10M/27M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project apache-mime4j-dom: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/dom/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :apache-mime4j-dom
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/build-logs/apache-mime4j/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough 

Bug#852255: projectreactor: FTBFS (No cached version of com.esotericsoftware.minlog:minlog:debian)

[Santiago Vila]

Package: src:projectreactor
Version: 2.0.8-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with maven_repo_helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- :reactor-core:install :reactor-net:install 
:reactor-bus:install :reactor-stream:install -x javadoc
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian -Ddebian.package=projectreactor :reactor-core:install 
:reactor-net:install :reactor-bus:install :reactor-stream:install -x javadoc
Initialized native services in: /<>/.gradle/native
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Loading the Maven rules...
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'reactor', project ':reactor-alloc', project 
':reactor-bus', project ':reactor-core', project ':reactor-groovy', project 
':reactor-groovy-extensions', project ':reactor-logback', project 
':reactor-net', project ':reactor-stream']
Keep-alive timer started
Adding Debian repository to project 'reactor'
Adding Debian repository to project 'reactor-alloc'
Adding Debian repository to project 'reactor-bus'
Adding Debian repository to project 'reactor-core'
Adding Debian repository to project 'reactor-groovy'
Adding Debian repository to project 'reactor-groovy-extensions'
Adding Debian repository to project 'reactor-logback'
Adding Debian repository to project 'reactor-net'
Adding Debian repository to project 'reactor-stream'
Evaluating root project 'reactor' using build file 
'/<>/build.gradle'.
Compiling build file '/<>/build.gradle' using 
SubsetScriptTransformer.
Replacing org.springframework.build.gradle:propdeps-plugin:jar:0.0.7  
->  org.springframework.build.gradle:propdeps-plugin:jar:debian
Ignoring io.spring.gradle:spring-io-plugin:jar:0.0.4.RELEASE
Ignoring com.github.jengelman.gradle.plugins:shadow:jar:1.2.0
Compiling build file '/<>/build.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/setup.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/setup.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/ide.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/ide.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'reactor'
Configuring javadoc links
Evaluating project ':reactor-alloc' using build file 
'/<>/reactor-alloc/build.gradle'.
Adding task debianMavenPom to project 'reactor-alloc'
Configuring javadoc links
Evaluating project ':reactor-bus' using build file 
'/<>/reactor-bus/build.gradle'.
Adding task debianMavenPom to project 'reactor-bus'
Configuring javadoc links
Evaluating project ':reactor-core' using build file 
'/<>/reactor-core/build.gradle'.
Adding task debianMavenPom to project 'reactor-core'
Configuring javadoc links
Evaluating project ':reactor-groovy' using build file 
'/<>/reactor-groovy/build.gradle'.
Adding task debianMavenPom to project 'reactor-groovy'
Configuring javadoc links
Evaluating project ':reactor-groovy-extensions' using build file 
'/<>/reactor-groovy-extensions/build.gradle'.
Adding task debianMavenPom to project 'reactor-groovy-extensions'
Configuring javadoc links
Evaluating project ':reactor-logback' using build file 
'/<>/reactor-logback/build.gradle'.
Adding task debianMavenPom to project 'reactor-logback'
Configuring javadoc links
Evaluating project ':reactor-net' using build file 
'/<>/reactor-net/build.gradle'.
Adding task debianMavenPom to project 'reactor-net'
Configuring javadoc links
Evaluating project ':reactor-stream' using build file 
'/<>/reactor-stream/build.gradle'.
Adding task debianMavenPom to project 'reactor-stream'
Configuring javadoc links
All projects evaluated.
Selected primary task ':reactor-core:install' from project :reactor-core
Selected primary task 

Bug#852253: kryo-serializers: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode)

[Santiago Vila]

Package: src:kryo-serializers
Version: 0.22-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibkryo-serializers-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building kryo serializers 0.22
[INFO] 
[WARNING] The POM for com.esotericsoftware.minlog:minlog:jar:debian is missing, 
no dependency information available
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 2.737 s
[INFO] Finished at: 2017-01-22T20:50:34+00:00
[INFO] Final Memory: 7M/19M
[INFO] 
[ERROR] Failed to execute goal on project kryo-serializers: Could not resolve 
dependencies for project de.javakaffee:kryo-serializers:bundle:0.22: Cannot 
access central (https://repo.maven.apache.org/maven2) in offline mode and the 
artifact com.esotericsoftware.minlog:minlog:jar:debian has not been downloaded 
from it before. -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


It also fails here, where you can get a full build log if you need it:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/kryo-serializers.html

In case it helps: My build history (for stretch) shows that something
happened between 2017-01-16 and 2017-01-21:

[...]
Status: successful  kryo-serializers_0.22-3_amd64-20170116T195523Z
Status: failed  kryo-serializers_0.22-3_amd64-20170121T150952Z
[...]

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

Thanks.

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

Bug#852254: openjpa: FTBFS (Cannot access central (https://repo.maven.apache.org/maven2) in offline mode)

[Santiago Vila]

Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-kernel:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-jar-plugin is missing. @ line 134, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-persistence-jdbc:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 896, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-xmlstore:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 77, column 12
[WARNING] 
[WARNING] Some problems were encountered while building the effective model for 
org.apache.openjpa:openjpa-slice:jar:2.4.0
[WARNING] 'build.plugins.plugin.version' for 
org.apache.maven.plugins:maven-surefire-plugin is missing. @ line 125, column 12
[WARNING] 
[WARNING] It is highly recommended to fix these problems because they threaten 
the stability of your build.
[WARNING] 
[WARNING] For this reason, future Maven versions might no longer support 
building such malformed projects.
[WARNING] 
[INFO] 
[INFO] Reactor Build Order:
[INFO] 
[INFO] OpenJPA Utilities Library
[INFO] OpenJPA Kernel
[INFO] OpenJPA JDBC
[INFO] OpenJPA Persistence
[INFO] OpenJPA Persistence JDBC
[INFO] OpenJPA XML Store
[INFO] OpenJPA Slice
[INFO] OpenJPA JEST
[INFO] OpenJPA Aggregate Jar
[INFO] OpenJPA Parent POM
[INFO] 
[INFO] 
[INFO] Building OpenJPA Utilities Library 2.4.0
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ 
openjpa-lib ---
[WARNING] Using platform encoding (ANSI_X3.4-1968 actually) to copy filtered 
resources, i.e. build is platform dependent!
[INFO] Copying 9 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ openjpa-lib ---
[INFO] Changes detected - recompiling the module!
[WARNING] File encoding has not been set, using platform encoding 
ANSI_X3.4-1968, i.e. build is platform dependent!
[INFO] Compiling 161 source files to /<>/openjpa-lib/target/classes
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java:
 Some input files use or override a deprecated API.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/rop/SoftRandomAccessResultList.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/util/concurrent/NullSafeConcurrentHashMap.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/<>/openjpa-lib/src/main/java/org/apache/openjpa/lib/util/concurrent/NullSafeConcurrentHashMap.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-antrun-plugin:1.7:run (set subversion revision) @ openjpa-lib 
---
[WARNING] Parameter tasks is deprecated, use target instead
[INFO] Executing tasks

main:
 [exec] Execute failed: java.io.IOException: Cannot run program 
"svnversion" (in directory 

Bug#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Santiago Vila]

On Fri, Jan 13, 2017 at 10:12:06AM +0100, Emmanuel Bourg wrote:
> Le 13/01/2017 à 09:55, Santiago Vila a écrit :
> 
> > My autobuilders do not work that way (with arbitrary build-dependencies).
> > 
> > Please tell me if those versions are in testing, in unstable, or
> > something else (I hope it's not experimental, I don't have a chroot
> > setup for it).
> 
> They are both in testing/unstable.

Ok, easybind now builds fine in both testing and unstable, but since
this is not a new version, then either there was a missing versioned
build-depends or the bug is somewhere else.

If the bug is somewhere else, please use reassign and affects. I don't
like reporting bugs against packages which are not to blame.

Thanks.

__
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#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Santiago Vila]

On Fri, Jan 13, 2017 at 09:52:36AM +0100, Emmanuel Bourg wrote:

> Could you please try again with the latest version of gradle (3.2.1-1
> instead of 3.1-2) and gradle-debian-helper (1.5.1 instead of 1.4.4) ?

My autobuilders do not work that way (with arbitrary build-dependencies).

Please tell me if those versions are in testing, in unstable, or
something else (I hope it's not experimental, I don't have a chroot
setup for it).

Thanks.

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

Bug#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Santiago Vila]

On Tue, Jan 10, 2017 at 10:02:12AM +0100, Emmanuel Bourg wrote:
> I'm unable to reproduce this issue. The pom file
> build/debian/easybind.pom should be generated automatically, this
> feature was added to gradle-debian-helper 1.4.
> 
> Santiago could you post the full build log please?

Sure. There was already a build failure here:

https://tests.reproducible-builds.org/debian/rbuild/testing/amd64/easybind_1.0.3-1.rbuild.log

I've also put my build logs here:

https://people.debian.org/~sanvila/build-logs/easybind/

> I'd like to check the versions of gradle and gradle-debian-helper
> used.

If this is not a bug in easybind, please use "reassign" and "affects".

Thanks.

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

Bug#850233: mavibot: FTBFS randomly (sbuild hangs)

[Santiago Vila]

I said:
> I have at least one *successful* build
> containing an error like that (see attach)

Well, I forgot the attach.

I'll report that in a separate bug.

Thanks.

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

Bug#850233: mavibot: FTBFS randomly (sbuild hangs)

[Santiago Vila]

On Fri, Jan 06, 2017 at 12:22:36PM +0100, Emmanuel Bourg wrote:
> Le 5/01/2017 à 11:05, Santiago Vila a écrit :
> > Running org.apache.directory.mavibot.btree.MultiThreadedBtreeTest
> >  Time to create 1M entries : 4 seconds
> > Written 0 elements
> > Written 10 elements
> > Written 20 elements
> > Written 30 elements
> > Exception: java.lang.OutOfMemoryError thrown from the 
> > UncaughtExceptionHandler in thread "Thread-102"
> 
> 
> > I don't know how to reproduce this, sorry, but it happened at least twice 
> > to me.
> 
> Hi Santiago,
> 
> The tests ran out of memory. How much memory was assigned to the builder?

Ooops! They were actually the smallest size I use: 768 MB of RAM plus 1 GB of 
swap.
(I'm closing this bug with this message).

I have a list of regexps to check for things like this.
So I'll add another one for java.lang.OutOfMemoryError.


But I still don't understand why it should fail. I measure the
allocated memory by looking at Committed_AS in /proc/meminfo, and this
package has never required more than 900 MB (less than 768MB + 1GB).

Maybe it's the stack (not the heap, measured by Committed_AS) what
my autobuilders had not enough?

How could I ensure that this does not happen again in the general case?

(Sorry if this is a stupid question, I don't know a lot about this
low-level things).


There is also another problem: I have at least one *successful* build
containing an error like that (see attach).

Is this not a violation of Policy 4.6? (That's the rule saying that
whenever there is an error, the build should stop).

Thanks a lot.

__
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#850233: mavibot: FTBFS randomly (sbuild hangs)

[Santiago Vila]

Package: src:mavibot
Version: 1.0.0~M1-2
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibmavibot-java --debian-build --keep-pom-version 
--maven-repo=/<>/mavibot-1.0.0\~M1/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<>/mavibot-1.0.0\~M1 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/mavibot-1.0.0\~M1/debian/maven.properties
 org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/mavibot-1.0.0\~M1/debian 
-Dmaven.repo.local=/<>/mavibot-1.0.0\~M1/debian/maven-repo package 
-DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...

[... snipped ...]

Written 6 elements in : 1018ms
Written 7 elements in : 1057ms
Written 8 elements in : 1068ms
Written 9 elements in : ms
Delta : 11530, nbError = 0, Nb insertion per second : 8000
6MB
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 11.88 sec - in 
org.apache.directory.mavibot.btree.RecordManagerFreePageTest
Running org.apache.directory.mavibot.btree.BTreeConfigurationTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.048 sec - in 
org.apache.directory.mavibot.btree.BTreeConfigurationTest
Running org.apache.directory.mavibot.btree.comparator.ByteArrayComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.directory.mavibot.btree.comparator.ByteArrayComparatorTest
Running org.apache.directory.mavibot.btree.comparator.ShortArrayComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec - in 
org.apache.directory.mavibot.btree.comparator.ShortArrayComparatorTest
Running org.apache.directory.mavibot.btree.comparator.BooleanComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in 
org.apache.directory.mavibot.btree.comparator.BooleanComparatorTest
Running org.apache.directory.mavibot.btree.comparator.CharArrayComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.012 sec - in 
org.apache.directory.mavibot.btree.comparator.CharArrayComparatorTest
Running org.apache.directory.mavibot.btree.comparator.ShortComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.005 sec - in 
org.apache.directory.mavibot.btree.comparator.ShortComparatorTest
Running org.apache.directory.mavibot.btree.comparator.LongComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.directory.mavibot.btree.comparator.LongComparatorTest
Running org.apache.directory.mavibot.btree.comparator.BooleanArrayComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.directory.mavibot.btree.comparator.BooleanArrayComparatorTest
Running org.apache.directory.mavibot.btree.comparator.ByteComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.011 sec - in 
org.apache.directory.mavibot.btree.comparator.ByteComparatorTest
Running org.apache.directory.mavibot.btree.comparator.RevisionNameComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in 
org.apache.directory.mavibot.btree.comparator.RevisionNameComparatorTest
Running org.apache.directory.mavibot.btree.comparator.LongArrayComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.01 sec - in 
org.apache.directory.mavibot.btree.comparator.LongArrayComparatorTest
Running org.apache.directory.mavibot.btree.comparator.StringComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.003 sec - in 
org.apache.directory.mavibot.btree.comparator.StringComparatorTest
Running org.apache.directory.mavibot.btree.comparator.CharComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.directory.mavibot.btree.comparator.CharComparatorTest
Running org.apache.directory.mavibot.btree.comparator.IntComparatorTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 

Bug#850204: java-gnome: FTBFS randomly (Fatal IO error 0 (Success) on X server)

[Santiago Vila]

Package: src:java-gnome
Version: 4.1.3-4
Severity: important

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
test -x debian/rules
mkdir -p "."
touch debian/stamp-autotools-files
chmod a+x /<>/./configure
mkdir -p .
cd . && CFLAGS="-g -O2 -fdebug-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security" CXXFLAGS="-g -O2 
-fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat 
-Werror=format-security" CPPFLAGS="-Wdate-time -D_FORTIFY_SOURCE=2" 
LDFLAGS="-Wl,-z,relro" /<>/./configure --build=x86_64-linux-gnu 
--prefix=/usr --includedir="\${prefix}/include" --mandir="\${prefix}/share/man" 
--infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var 
--libexecdir="\${prefix}/lib/java-gnome" --srcdir=. --disable-maintainer-mode 
--disable-dependency-tracking --disable-silent-rules --libdir=/usr/lib/jni 
jdk=/usr/lib/jvm/default-java

equivalence, v0.2
...configuring Java projects to build and run on Linux & Unix

Identify operating system: Debian


[... snipped ...]

SNAPdoc/api/org/gnome/gtk/RadioButton.png
SNAPdoc/api/org/gnome/gtk/ComboBox.png
SNAPdoc/api/org/gnome/gtk/Arrow.png
SNAPdoc/api/org/gnome/gtk/Notebook.png
SNAPdoc/api/org/gnome/gtk/Calendar.png
SNAPdoc/api/org/gnome/gtk/ComboBoxText.png
SNAPdoc/api/org/gnome/gtk/ComboBoxText--Entry.png
SNAPdoc/api/org/freedesktop/cairo/Context-line.png
SNAPdoc/api/org/gnome/gtk/TextView.png
SNAPdoc/api/org/gnome/gtk/TextView-BorderWindows.png
SNAPdoc/api/org/freedesktop/cairo/Context-arc.png
SNAPdoc/api/org/freedesktop/cairo/Context-arcNegative.png
SNAPdoc/api/org/freedesktop/cairo/Matrix-rotate.png
SNAPdoc/api/org/freedesktop/cairo/Matrix-scale.png
SNAPdoc/api/org/freedesktop/cairo/Matrix-translate.png
SNAPdoc/api/org/freedesktop/cairo/Context-rectangle.png
SNAPdoc/api/org/gnome/gtk/EntryCompletion.png
SNAPdoc/api/org/gnome/gtk/Entry.png
SNAPdoc/api/org/gnome/gtk/LinkButton.png
SNAPdoc/api/org/gnome/gtk/InfoBar.png
SNAPdoc/api/org/gnome/gtk/Switch.png
WRITE   doc/api/org/freedesktop/cairo/Operator-in.png
WRITE   doc/api/org/freedesktop/cairo/Operator-clear.png
WRITE   doc/api/org/freedesktop/cairo/Operator-source.png
WRITE   doc/api/org/freedesktop/cairo/Operator-over.png
WRITE   doc/api/org/freedesktop/cairo/Operator-out.png
WRITE   doc/api/org/freedesktop/cairo/Operator-atop.png
WRITE   doc/api/org/freedesktop/cairo/Operator-dest.png
WRITE   doc/api/org/freedesktop/cairo/Operator-dest_over.png
WRITE   doc/api/org/freedesktop/cairo/Operator-dest_in.png
WRITE   doc/api/org/freedesktop/cairo/Operator-dest_out.png
WRITE   doc/api/org/freedesktop/cairo/Operator-dest_atop.png
WRITE   doc/api/org/freedesktop/cairo/Operator-xor.png
WRITE   doc/api/org/freedesktop/cairo/Operator-add.png
WRITE   doc/api/org/freedesktop/cairo/Operator-saturate.png
KILLXvfb

(.:12544): Gdk-WARNING **: .: Fatal IO error 0 (Success) on X server :99.

Makefile:87: recipe for target 'doc' failed
make[1]: *** [doc] Error 1
make[1]: Leaving directory '/<>'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 
'debian/stamp-makefile-build' failed
make: *** [debian/stamp-makefile-build] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


This is just how the build ends, not necessarily the relevant part.

I've put several build logs here:

https://people.debian.org/~sanvila/java-gnome/

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

The bug should be reproducible with sbuild on a single CPU virtual machine,
provided you try enough times (as the failure happens randomly).


Note 1: It seems that the build is creating snapshots for the documentation,
and there is another bug (#836100) requesting a slightly different way to
take snapshots. Would fixing #836100 help to fix this one?

(X-Debbugs-Cc for Simon in case he knows the answer).

Note 2: The failure rate is very small, I have not tried to measure it.
I guess it is well below 10%, so if you try to reproduce it, please
try really really a *lot* of times.

Note 3: I would not really recommend trying a lot of times to reproduce it.
Instead, it could be more productive to look at the build logs and
try to guess *how* it may happen, but I don't really know the internals
of this package, so this is really up to you.

Thanks.

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

Bug#844083: (no subject)

[Santiago Vila]

severity 846116 important
severity 680038 important
severity 828929 important
severity 834686 important
severity 834962 important
severity 842836 important
severity 844083 important
severity 844088 important
severity 844571 important
severity 845164 important
severity 846021 important
severity 846115 important
severity 846300 important
severity 846318 important
severity 848054 important
severity 848055 important
severity 848403 important
severity 849775 important
severity 849217 important
severity 832865 important
severity 837067 important
severity 848063 important
severity 849363 important
severity 846026 important
severity 841904 important
severity 847288 important
severity 848859 important
severity 841098 important
severity 843038 important
severity 848409 important
severity 710696 important
thanks

Hello.

I'm setting the severity of this bug to "important" not because
I don't think it is not RC (as Release Policy still says that
packages must autobuild *without* failure), but because the
Release Managers are considering to decide about RC-ness
of this kind of bugs based on the probability of failure.

We don't know what kind of threshold there will be for stretch, so I
strongly recommend that you act as if this bug was serious and RC,
especially if the failures happen very often on any kind of
autobuilder which is not misconfigured.

Thanks.

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

Bug#849931: jackson-module-afterburner: FTBFS (Missing dependency)

[Santiago Vila]

Package: src:jackson-module-afterburner
Version: 2.7.1-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven --with javahelper
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>'
sh debian/replace-generate.sh 
src/main/java/com/fasterxml/jackson/module/afterburner/PackageVersion.java
dh_auto_configure
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibjackson2-module-afterburner-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
make[1]: Leaving directory '/<>'
   jh_linkjars -i -O--buildsystem=maven
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] 'dependencies.dependency.version' for 
com.fasterxml.jackson.core:jackson-annotations:jar is missing. @ line 62, 
column 15
 @ 
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]   
[ERROR]   The project 
com.fasterxml.jackson.module:jackson-module-afterburner:2.7.1 
(/<>/pom.xml) has 1 error
[ERROR] 'dependencies.dependency.version' for 
com.fasterxml.jackson.core:jackson-annotations:jar is missing. @ line 62, 
column 15
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US returned exit 
code 1
debian/rules:9: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

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

Bug#849930: easybind: FTBFS (Cannot find pom file easybind.pom)

[Santiago Vila]

Package: src:easybind
Version: 1.0.3-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_autoreconf -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   dh_auto_build -i -O--buildsystem=gradle
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian jar
Initialized native services in: /<>/.gradle/native
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.

[... snipped ...]

Total time: 7.476 secs
Stopped 0 compiler daemon(s).
   dh_auto_test -i -O--buildsystem=gradle
 fakeroot debian/rules binary-indep
dh binary-indep --buildsystem=gradle --with=maven-repo-helper
   dh_testroot -i -O--buildsystem=gradle
   dh_prep -i -O--buildsystem=gradle
rm -f debian/libeasybind-java.substvars
rm -f debian/libeasybind-java.*.debhelper
rm -rf debian/libeasybind-java/
   dh_auto_install -i -O--buildsystem=gradle
install -d debian/libeasybind-java
   mh_install -i -O--buildsystem=gradle
mh_installpom --java-lib--package=libeasybind-java   
build/debian/easybind.pom
mh_cleanpom   --package=libeasybind-java 
build/debian/easybind.pom debian/.mh/pom.xml debian/.mh/pom.properties
Cannot find pom file /<>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.debian.maven.util.Readers.read(Readers.java:50)
at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

Cannot find pom file /<>/build/debian/easybind.pom
Dec 29, 2016 6:32:03 AM org.debian.maven.repo.POMCleaner cleanPom
SEVERE: null
java.io.FileNotFoundException: build/debian/easybind.pom (No such file or 
directory)
at java.io.FileInputStream.open0(Native Method)
at java.io.FileInputStream.open(FileInputStream.java:195)
at java.io.FileInputStream.(FileInputStream.java:138)
at org.debian.maven.util.Readers.read(Readers.java:50)
at org.debian.maven.repo.POMReader.readPom(POMReader.java:57)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:226)
at 
org.debian.maven.repo.POMTransformer.transformPom(POMTransformer.java:211)
at org.debian.maven.repo.POMCleaner.cleanPom(POMCleaner.java:75)
at org.debian.maven.repo.POMCleaner.main(POMCleaner.java:372)

/usr/bin/mh_installpom: line 148: debian/.mh/pom.properties: No such file or 
directory
debian/rules:7: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


The relevant part of the build log is included above.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still visible in the page for this package.

If you could not reproduce this using sbuild on a single CPU virtual machine 
(as I did),
please do not downgrade or mark as unreproducible, I would then consider giving 
you access
to a virtual machine on which I can reproduce it so that you can as well.
(In such case, please contact me off-list for details).

Thanks.

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

Bug#849217: jruby: FTBFS (sbuild hangs)

[Santiago Vila]

On Fri, Dec 30, 2016 at 01:46:57AM +, Miguel Landaeta wrote:

> Can you provide the full log of the failed build attempt?
>
> I can't reproduce this issue, although I don't use sbuild to build my
> packages but cowbuilder.
> 
> Since I couldn't reproduce the issue with my builder tool of choice,
> I'll setup sbuild later to try again. In the meantine, the full build
> log could be handy.

Some failed build logs here:

https://people.debian.org/~sanvila/jruby/

Note: The first one was made with eatmydata, but after I disabled it
the failure (randomly) keeps happening.

Thanks.

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

Bug#844088: conversant-disruptor: FTBFS randomly (failing tests)

[Santiago Vila]

Package: src:conversant-disruptor
Version: 1.2.8-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_autoreconf -i
   dh_auto_configure -i
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibconversant-disruptor-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building com.conversantmedia:disruptor 1.2.8
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ disruptor 
---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 2 resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:compile (default-compile) @ disruptor ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 23 source files to /<>/target/classes
[INFO] 
/<>/src/main/java/com/conversantmedia/util/concurrent/PushPullConcurrentQueue.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/<>/src/main/java/com/conversantmedia/util/concurrent/PushPullConcurrentQueue.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-resources-plugin:2.6:testResources (default-testResources) @ 
disruptor ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory /<>/src/test/resources
[INFO] 
[INFO] --- maven-compiler-plugin:3.2:testCompile (default-testCompile) @ 
disruptor ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 21 source files to /<>/target/test-classes
[INFO] 
/<>/src/test/java/com/conversantmedia/util/estimation/PercentileTest.java:
 
/<>/src/test/java/com/conversantmedia/util/estimation/PercentileTest.java
 uses or overrides a deprecated API.
[INFO] 
/<>/src/test/java/com/conversantmedia/util/estimation/PercentileTest.java:
 Recompile with -Xlint:deprecation for details.
[INFO] 
/<>/src/test/java/com/conversantmedia/util/concurrent/PushPullBlockingQueueTest.java:
 Some input files use unchecked or unsafe operations.
[INFO] 
/<>/src/test/java/com/conversantmedia/util/concurrent/PushPullBlockingQueueTest.java:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.17:test (default-test) @ disruptor ---
[INFO] Tests are skipped.
[INFO] 
[INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ disruptor ---
[INFO] Building jar: /<>/target/disruptor-1.2.8.jar
[INFO] 
[INFO] BUILD SUCCESS
[INFO] 
[INFO] Total time: 5.554 s
[INFO] Finished at: 2016-11-12T05:43:34+01:00
[INFO] Final Memory: 14M/46M
[INFO] 
   dh_auto_test -i
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test
[INFO] Scanning for projects...
[INFO] 
[INFO] 
[INFO] Building com.conversantmedia:disruptor 1.2.8
[INFO] 
[INFO] 
[INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ disruptor 
---
[INFO] Using 'UTF-8' encoding 

Bug#844083: openhft-lang: FTBFS randomly (DataValueGeneratorTest.testGenerateInterfaceWithDateNativeInstace fails)

[Santiago Vila]

Package: src:openhft-lang
Version: 6.7.6-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenhft-lang-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 

[... snipped ...]

net.openhft.lang.values.DoubleValue$$Heap 
net.openhft.lang.values.DoubleValue$$Native
net.openhft.lang.values.LongValue$$Heap 
net.openhft.lang.values.LongValue$$Native
net.openhft.lang.values.StringValue$$Heap 
net.openhft.lang.values.StringValue$$Native
net.openhft.lang.values.BooleanValue$$Heap 
net.openhft.lang.values.BooleanValue$$Native
net.openhft.lang.values.UnsignedByteValue$$Heap 
net.openhft.lang.values.UnsignedByteValue$$Native
net.openhft.lang.values.UnsignedIntValue$$Heap 
net.openhft.lang.values.UnsignedIntValue$$Native
net.openhft.lang.values.UnsignedShortValue$$Heap 
net.openhft.lang.values.UnsignedShortValue$$Native
net.openhft.lang.values.NestAll$$Heap net.openhft.lang.values.NestAll$$Native
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 6.064 sec - in 
net.openhft.lang.values.CheckValuesBuildTest
Running net.openhft.lang.values.StringValueTest
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0 sec - in 
net.openhft.lang.values.StringValueTest
Running net.openhft.lang.locks.LockingStrategyTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 10, Time elapsed: 0.087 sec - 
in net.openhft.lang.locks.LockingStrategyTest

Results :

Failed tests: 
  DataValueGeneratorTest.testGenerateInterfaceWithDateNativeInstace:237 
expected: java.util.Date but was: 
java.util.Date

Tests run: 571, Failures: 1, Errors: 0, Skipped: 16

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] OpenHFT/Java-Lang/lang . FAILURE [ 30.931 s]
[INFO] Java Lang Parent ... SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 31.869 s
[INFO] Finished at: 2016-11-12T05:06:02+01:00
[INFO] Final Memory: 16M/90M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project lang: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/lang/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2

Bug#842838: freeplane: FTBFS (Execution failed for task ':freeplane:debianMavenPom')

[Santiago Vila]

Package: src:freeplane
Version: 1.5.16-1
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- build -x test -x check_translation
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian build -x test -x check_translation
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Loading the Maven rules...
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'freeplane-1.5.16', project 
':JOrtho_0.4_freeplane', project ':freeplane', project ':freeplane_ant', 
project ':freeplane_framework', project ':freeplane_mac', project 
':freeplane_plugin_bugreport', project ':freeplane_plugin_formula', project 
':freeplane_plugin_jsyntaxpane', project ':freeplane_plugin_latex', project 
':freeplane_plugin_openmaps', project ':freeplane_plugin_script', project 
':freeplane_plugin_svg']
Keep-alive timer started
Adding Debian repository to project 'freeplane-1.5.16'
Adding Debian repository to project 'JOrtho_0.4_freeplane'
Adding Debian repository to project 'freeplane'
Adding Debian repository to project 'freeplane_ant'
Adding Debian repository to project 'freeplane_framework'
Adding Debian repository to project 'freeplane_mac'
Adding Debian repository to project 'freeplane_plugin_bugreport'
Adding Debian repository to project 'freeplane_plugin_formula'
Adding Debian repository to project 'freeplane_plugin_jsyntaxpane'
Adding Debian repository to project 'freeplane_plugin_latex'
Adding Debian repository to project 'freeplane_plugin_openmaps'
Adding Debian repository to project 'freeplane_plugin_script'
Adding Debian repository to project 'freeplane_plugin_svg'
Evaluating root project 'freeplane-1.5.16' using build file 
'/<>/build.gradle'.
Compiling build file '/<>/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/build.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/dist.gradle' using SubsetScriptTransformer.
Compiling script '/<>/dist.gradle' using BuildScriptTransformer.
Compiling script '/<>/mac.dist.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/mac.dist.gradle' using 
BuildScriptTransformer.
[ant:taskdef] : Warning: taskdef class com.oracle.appbundler.AppBundlerTask 
cannot be found
 using the classloader AntClassLoader[]
Compiling script '/<>/win.dist.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/win.dist.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/bin.dist.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/bin.dist.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/src.dist.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/src.dist.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/jdt-config.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/jdt-config.gradle' using 
BuildScriptTransformer.
Evaluating project ':JOrtho_0.4_freeplane' using build file 
'/<>/JOrtho_0.4_freeplane/build.gradle'.
Compiling build file '/<>/JOrtho_0.4_freeplane/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/JOrtho_0.4_freeplane/build.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'JOrtho_0.4_freeplane'
Configuring javadoc links
Evaluating project ':freeplane' using build file 
'/<>/freeplane/build.gradle'.
Compiling build file '/<>/freeplane/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/freeplane/build.gradle' using 
BuildScriptTransformer.
Replacing :knopflerfish-framework:jar:  ->  :knopflerfish-framework:jar:
Replacing org.dpolivaev.mnemonicsetter:mnemonicsetter:jar:0.5  ->  
org.dpolivaev.mnemonicsetter:mnemonicsetter:jar:debian
Evaluating project ':freeplane_ant' using build file 
'/<>/freeplane_ant/build.gradle'.
Compiling build file 

Bug#842721: jayway-jsonpath: FTBFS (Could not resolve all dependencies)

[Santiago Vila]

Package: src:jayway-jsonpath
Version: 2.0.0-2
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=gradle --with maven-repo-helper
   dh_testdir -i -O--buildsystem=gradle
   dh_update_autotools_config -i -O--buildsystem=gradle
   dh_auto_configure -i -O--buildsystem=gradle
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- jar install -x :json-path-web-test:jar -x :json-path:javadoc
mkdir -p .gradle/init.d
cp /usr/share/gradle-debian-helper/init.gradle .gradle/init.d/
gradle --info --console plain --offline --stacktrace --no-daemon 
--refresh-dependencies --gradle-user-home .gradle -Duser.home=. 
-Duser.name=debian jar install -x :json-path-web-test:jar -x :json-path:javadoc
Starting Build
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using SubsetScriptTransformer.
Compiling initialization script '/<>/.gradle/init.d/init.gradle' 
using BuildScriptTransformer.
Loading the Maven rules...
Compiling settings file '/<>/settings.gradle' using 
SubsetScriptTransformer.
Compiling settings file '/<>/settings.gradle' using 
BuildScriptTransformer.
Settings evaluated using settings file '/<>/settings.gradle'.
Projects loaded. Root project using build file '/<>/build.gradle'.
Included projects: [root project 'json-path-parent', project ':json-path', 
project ':json-path-assert', project ':json-path-web-test']
Keep-alive timer started
Adding Debian repository to project 'json-path-parent'
Adding Debian repository to project 'json-path'
Adding Debian repository to project 'json-path-assert'
Adding Debian repository to project 'json-path-web-test'
Evaluating root project 'json-path-parent' using build file 
'/<>/build.gradle'.
Compiling build file '/<>/build.gradle' using 
SubsetScriptTransformer.
Ignoring me.champeau.gradle:gradle-javadoc-hotfix-plugin:jar:0.1
Ignoring com.github.jengelman.gradle.plugins:shadow:jar:1.2.1
Ignoring me.champeau.gradle:japicmp-gradle-plugin:jar:0.1.0
Compiling build file '/<>/build.gradle' using 
BuildScriptTransformer.
Evaluating project ':json-path' using build file 
'/<>/json-path/build.gradle'.
Compiling build file '/<>/json-path/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path/build.gradle' using 
BuildScriptTransformer.
Compiling script '/<>/gradle/publishMaven.gradle' using 
SubsetScriptTransformer.
Compiling script '/<>/gradle/publishMaven.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path'
Configuring javadoc links
Evaluating project ':json-path-assert' using build file 
'/<>/json-path-assert/build.gradle'.
Compiling build file '/<>/json-path-assert/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path-assert/build.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path-assert'
Configuring javadoc links
Evaluating project ':json-path-web-test' using build file 
'/<>/json-path-web-test/build.gradle'.
Compiling build file '/<>/json-path-web-test/build.gradle' using 
SubsetScriptTransformer.
Compiling build file '/<>/json-path-web-test/build.gradle' using 
BuildScriptTransformer.
Adding task debianMavenPom to project 'json-path-web-test'
Configuring javadoc links
All projects evaluated.
Selected primary task 'jar' from project :
Selected primary task 'install' from project :
Tasks to be executed: [task ':json-path:compileJava', task 
':json-path:processResources', task ':json-path:classes', task 
':json-path:debianMavenPom', task ':json-path:jar', task 
':json-path-assert:compileJava', task ':json-path-assert:processResources', 
task ':json-path-assert:classes', task ':json-path-assert:debianMavenPom', task 
':json-path-assert:jar', task ':json-path:javadocJar', task 
':json-path:sourcesJar', task ':json-path:signArchives', task 
':json-path:install', task ':json-path-assert:javadoc', task 
':json-path-assert:javadocJar', task ':json-path-assert:sourcesJar', task 
':json-path-assert:signArchives', task ':json-path-assert:install', task 
':json-path-web-test:startScripts', task ':json-path-web-test:distTar', task 
':json-path-web-test:distZip', task ':json-path-web-test:compileJava', task 
':json-path-web-test:processResources', task ':json-path-web-test:classes', 
task ':json-path-web-test:javadoc', task ':json-path-web-test:javadocJar', task 
':json-path-web-test:sou
 rcesJar', task ':json-path-web-test:signArchives', task 
':json-path-web-test:install']
:json-path:compileJava (Thread[main,5,main]) started.
:json-path:compileJava
Replacing net.minidev:json-smart:jar:2.1.1  ->  

Bug#840827: lucene-solr: Network tests are performed using public IP instead of 127.0.0.1

[Santiago Vila]

retitle 840827 lucene-solr: Network tests are performed using public IP instead 
of 127.0.0.1
severity 840827 normal
thanks

On Mon, Oct 24, 2016 at 05:08:39PM +0200, Emmanuel Bourg wrote:

> I got a look at this issue and it seems the failing tests are setting up
> a local RMI server but the subsequent connections do not work.
> 
> I don't know why it fails with your machines but if I'm not mistaken
> local connections are allowed during the build.
> 
> Is the IP you redacted the one from the machine building the package, or
> another machine on your network?

Big ooops! Sorry. That was why it failed.

Not all my machines have a fixed IP, and I made the mistake of putting
the public IP of the day in /etc/hosts instead of 127.0.1.1.

I've triggered rebuilds on the machines where it previously failed and
now it does not fail, so there is no FTBFS bug anymore.



But I have still to "redact" the build logs in case the tests fail.

Would not be better to do the tests by connecting to localhost or
127.0.0.1 instead of the machine name?

I think this would even simplify the code, as you could use always
"localhost" instead of having to guess the real hostname first.


Thanks a lot.

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

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

On Wed, Oct 19, 2016 at 10:50:33PM +0200, Emmanuel Bourg wrote:
> Le 19/10/2016 à 22:31, Santiago Vila a écrit :
> 
> > I have already reported a bug like this in other packages.
> > See Bug #841197 for a likely fix.
> 
> ...and you'll get the same issue with all reverse dependencies of
> maven-enforcer. These bugs are duplicates of the same issue, they should
> be assigned to maven-enforcer, merged, and marked as affecting the
> reverse dependencies:
> [...]

You are absolutely right. Sorry for the duplicates.

I read a message from Markus yesterday, but I read it too fast and
didn't realize he already said this was a bug in maven-enforcer.

I see that he already did the merge and the reassign.

I'm going to make the "affects" with the list of reverse depends you
have provided. This definitely helps me to avoid duplicate bugs.

Thanks a lot.

__
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#841363: junit4: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:junit4
Version: 4.12-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -pjunit4 --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[INFO] 
[INFO] 
[INFO] Building JUnit 4.12
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping JUnit
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.345 s
[INFO] Finished at: 2016-10-19T20:46:35+02:00
[INFO] Final Memory: 8M/90M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 

Bug#841362: activemq-protobuf: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibactivemq-protobuf-java --debian-build 
--keep-pom-version --maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--parallel -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package javadoc:jar 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[WARNING] 

[... snipped ...]

[WARNING] The POM for org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 
is missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-release-plugin:2.3.2: Plugin 
org.apache.maven.plugins:maven-release-plugin:2.3.2 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-release-plugin:jar:2.3.2 has not been downloaded 
from it before.
[INFO] 
[INFO] 
[INFO] Building ActiveMQ Protocol Buffers POM 1.1
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1: Plugin 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies 
could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1
[WARNING] The POM for org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from 
it before.
[WARNING] The POM for org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-antrun-plugin:1.7: Plugin 
org.apache.maven.plugins:maven-antrun-plugin:1.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-antrun-plugin:jar:1.7 has not been downloaded 
from it before.
[WARNING] The POM for 
org.apache.maven.plugins:maven-assembly-plugin:jar:2.2-beta-4 is missing, no 
dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4: Plugin 
org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4 or one of its 
dependencies could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline 

Bug#841296: openjpa: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:openjpa
Version: 2.4.0-3
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --parallel --buildsystem=maven
   dh_testdir -i -O--parallel -O--buildsystem=maven
   dh_update_autotools_config -i -O--parallel -O--buildsystem=maven
   dh_auto_configure -i -O--parallel -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibopenjpa-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- install
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo install -DskipTests 
-Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

[INFO] Replacing /<>/openjpa/target/openjpa-2.4.0.jar with 
/<>/openjpa/target/openjpa-2.4.0-shaded.jar
[INFO] Dependency-reduced POM written at: 
/<>/openjpa/dependency-reduced-pom.xml
[INFO] 
[INFO] --- maven-install-plugin:2.5.2:install (default-install) @ openjpa ---
[INFO] Installing /<>/openjpa/target/openjpa-2.4.0.jar to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Installing /<>/openjpa/dependency-reduced-pom.xml to 
/<>/debian/maven-repo/org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.pom
[INFO] 
[INFO] --- maven-bundle-plugin:2.5.4:install (default-install) @ openjpa ---
[INFO] Writing OBR metadata
[INFO] Installing org/apache/openjpa/openjpa/2.4.0/openjpa-2.4.0.jar
[INFO] Writing OBR metadata
[INFO] 
[INFO] 
[INFO] Building OpenJPA Parent POM 2.4.0
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] OpenJPA Utilities Library .. SUCCESS [  8.801 s]
[INFO] OpenJPA Kernel . SUCCESS [ 12.904 s]
[INFO] OpenJPA JDBC ... SUCCESS [  7.667 s]
[INFO] OpenJPA Persistence  SUCCESS [  4.218 s]
[INFO] OpenJPA Persistence JDBC ... SUCCESS [  1.028 s]
[INFO] OpenJPA XML Store .. SUCCESS [  0.481 s]
[INFO] OpenJPA Slice .. SUCCESS [  0.709 s]
[INFO] OpenJPA JEST ... SUCCESS [  0.609 s]
[INFO] OpenJPA Aggregate Jar .. SUCCESS [  6.807 s]
[INFO] OpenJPA Parent POM . FAILURE [  0.007 s]
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 44.824 s
[INFO] Finished at: 2016-10-19T13:58:12+02:00
[INFO] Final Memory: 53M/161M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/PluginResolutionException
dh_auto_build: 

Bug#841197: libhibernate3-java: FTBFS (Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of its dependencies could not be resolved)

[Santiago Vila]

Package: src:libhibernate3-java
Version: 3.6.10.Final-5
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibhibernate3-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
rm -Rf debian/maven-repo/org/hibernate/hibernate
rm -Rf debian/maven-repo/org/hibernate/hibernate-parent

[... snipped ...]

[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-deploy-plugin:2.7: Plugin 
org.apache.maven.plugins:maven-deploy-plugin:2.7 or one of its dependencies 
could not be resolved: Cannot access central 
(https://repo.maven.apache.org/maven2) in offline mode and the artifact 
org.apache.maven.plugins:maven-deploy-plugin:jar:2.7 has not been downloaded 
from it before.
[WARNING] The POM for org.apache.maven.plugins:maven-site-plugin:jar:3.3 is 
missing, no dependency information available
[WARNING] Failed to retrieve plugin descriptor for 
org.apache.maven.plugins:maven-site-plugin:3.3: Plugin 
org.apache.maven.plugins:maven-site-plugin:3.3 or one of its dependencies could 
not be resolved: Cannot access central (https://repo.maven.apache.org/maven2) 
in offline mode and the artifact 
org.apache.maven.plugins:maven-site-plugin:jar:3.3 has not been downloaded from 
it before.
[INFO] 
[INFO] 
[INFO] Building Hibernate Core Parent POM 3.6.10.Final
[INFO] 
[WARNING] The POM for org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1 
is invalid, transitive dependencies (if any) will not be available, enable 
debug logging for more details
[INFO] 
[INFO] 
[INFO] Skipping Hibernate Core Aggregator
[INFO] This project has been banned from the build due to previous failures.
[INFO] 
[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Hibernate Core Parent POM .. FAILURE [  0.010 s]
[INFO] Hibernate Core . SKIPPED
[INFO] Hibernate Testing .. SKIPPED
[INFO] Hibernate Testsuite  SKIPPED
[INFO] Hibernate Ehcache Integration .. SKIPPED
[INFO] Hibernate OSCache Integration .. SKIPPED
[INFO] Hibernate SwarmCache Integration ... SKIPPED
[INFO] Hibernate C3P0 ConnectionProvider .. SKIPPED
[INFO] Hibernate Proxool ConnectionProvider ... SKIPPED
[INFO] Hibernate JDBC3-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Entity Manager ... SKIPPED
[INFO] Hibernate JDBC4-JdbcSupport Testing  SKIPPED
[INFO] Hibernate Core Aggregator .. SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 0.980 s
[INFO] Finished at: 2016-10-18T14:29:33+02:00
[INFO] Final Memory: 8M/28M
[INFO] 
[ERROR] Plugin org.apache.maven.plugins:maven-enforcer-plugin:1.4.1 or one of 
its dependencies could not be resolved: Failed to read artifact descriptor for 
org.apache.maven.plugins:maven-enforcer-plugin:jar:1.4.1: 1 problem was 
encountered while building the effective model for 
org.apache.maven.plugins:maven-enforcer-plugin:1.4.1
[ERROR] [ERROR] 'dependencies.dependency.version' for 
org.apache.maven.plugin-tools:maven-plugin-annotations:jar is missing. @
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible 

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

[Santiago Vila]

I forgot to tell that I can reproduce this only on some machines but
not in others. The machines on which it fails (there are more than one)
seem to be the ones having some corporate firewall rules I can't
disable. This is probably not just a coincidence.

However, since packages are not supposed to use the network during the build,
a bad network configuration should never make the package to FTBFS anyway.

Thanks.

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

Bug#840827: lucene-solr: FTBFS (failing tests, no route to host)

[Santiago Vila]

Package: src:lucene-solr
Version: 3.6.2+dfsg-8
Severity: serious

Dear maintainer:

I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --with maven_repo_helper
   dh_testdir -i
   dh_update_autotools_config -i
   debian/rules override_dh_auto_configure
make[1]: Entering directory '/<>/lucene-solr-3.6.2+dfsg'
# Link in jars from /usr/share/java rather
# than patching the build process
for pkg in `cat debian/build-jars`; \
do \
ln -sf `echo $pkg | cut -d : -f 1` `echo $pkg | cut -d : -f 2`; \
done
ln: failed to create symbolic link './lucene/lib/ant.jar': No such file or 
directory

[... snipped ...]

[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.run(JUnitTestRunner.java:535)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.launch(JUnitTestRunner.java:1182)
[junit] at 
org.apache.tools.ant.taskdefs.optional.junit.JUnitTestRunner.main(JUnitTestRunner.java:1033)
[junit] Caused by: java.net.NoRouteToHostException: No route to host
[junit] at java.net.PlainSocketImpl.socketConnect(Native Method)
[junit] at 
java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
[junit] at 
java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
[junit] at 
java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
[junit] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
[junit] at java.net.Socket.connect(Socket.java:589)
[junit] at java.net.Socket.connect(Socket.java:538)
[junit] at java.net.Socket.(Socket.java:434)
[junit] at java.net.Socket.(Socket.java:211)
[junit] at 
sun.rmi.transport.proxy.RMIDirectSocketFactory.createSocket(RMIDirectSocketFactory.java:40)
[junit] at 
sun.rmi.transport.proxy.RMIMasterSocketFactory.createSocket(RMIMasterSocketFactory.java:148)
[junit] at 
sun.rmi.transport.tcp.TCPEndpoint.newSocket(TCPEndpoint.java:613)
[junit] ... 44 more
[junit] 
[junit] 
[junit] Tests run: 1, Failures: 0, Errors: 1, Time elapsed: 5.301 sec
[junit] 
[junit] - Standard Error -
[junit] NOTE: reproduce with: ant test 
-Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter 
-Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b 
-Dargs="-Dfile.encoding=ANSI_X3.4-1968"
[junit] NOTE: reproduce with: ant test 
-Dtestcase=TestRemoteCachingWrapperFilter -Dtestmethod=testTermRemoteFilter 
-Dtests.seed=360d91d04c9e1cb5:-d1bf13dc331d343:-5a995359e653cf8b 
-Dargs="-Dfile.encoding=ANSI_X3.4-1968"
[junit] NOTE: test params are: locale=it, timezone=Pacific/Enderbury
[junit] NOTE: all tests run in this JVM:
[junit] [TestRemoteCachingWrapperFilter]
[junit] NOTE: Linux 4.7.0-1-amd64 amd64/Oracle Corporation 1.8.0_102 
(64-bit)/cpus=1,threads=1,free=86734984,total=95354880
[junit] -  ---
[junit] Test org.apache.lucene.search.TestRemoteCachingWrapperFilter FAILED

BUILD FAILED
/<>/lucene-solr-3.6.2+dfsg/lucene/build.xml:584: The following error 
occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:1051: The 
following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/contrib/contrib-build.xml:61: The 
following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:692: 
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!
The following error occurred while executing this line:
/<>/lucene-solr-3.6.2+dfsg/lucene/common-build.xml:676: Tests failed!

Total time: 10 minutes 58 seconds
debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>/lucene-solr-3.6.2+dfsg'
debian/rules:8: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


The build was made in a KVM/QEMU virtual machine with 1 CPU using sbuild.

I attach a full build log, but the build system leaks the IP of the machine
(it probably shouldn't). I've redacted that.

If this is really a bug in one of the build-depends, please use reassign and 
affects,
so that this is still 

Bug#834682: mina2: FTBFS too much often (failing tests)

[Santiago Vila]

On Fri, 26 Aug 2016, Markus Koschany wrote:

> Control: severity -1 normal

Markus, this package fails to build from source:

* In my 5 autobuilders.

* In one of the three tests made by Gregor.

* In several autobuilders from the reproducible builds effort:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/mina2.html


As the failure has been verified from several independent parties, it
would not be unfair at all to say that, objectively, this package FTBFS.

Being able to build from source is a release goal since a lot of time
and deserves serious severity according to release policy:

https://release.debian.org/stretch/rc_policy.txt

which clearly says "Packages must autobuild".

So I ask you one more time that you respect release policy and
reconsider about this.

Thanks.

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

Bug#834682: mina2: FTBFS in testing (failing tests)

[Santiago Vila]

On Thu, 8 Sep 2016, gregor herrmann wrote:

> Logs attached. Unfortunately I don't have any idea on how to fix the
> problem, but if you want me to do something else just shout.

Well, if you don't mind burning a bunch of additional CPU cycles,
I would continue to build it several times until it fails again.

(If you tried three times and it failed once, it seems likely that it
happens again).

Then it would be interesting to see if the test which fails is the
same it failed the first time, which, in your case, was this one:

Failed tests: 
  DatagramBindTest>AbstractBindTest.testUnbindDisconnectsClients:187
expected:<5> but was:<4>

I have not analyzed my build logs, but I guess this is unfortunately
not the same test which fails for me.


BTW: I try to be objective by never reporting something when it only
happens to me. This is why I sometimes say "here is a build log and it
also fails in reproducible builds" or also "here you have several
build logs from several different autobuilders".

I think it would be just fair to ask the maintainer to be objective as
well and consider whether it is really justified to downgrade the
severity of a FTBFS bug when everybody else get a FTBFS too and his
computer is the only one in which it may not be reproduced.

If it is certainly frustrating when one receives a bug which is random
and difficult to reproduce, imagine the frustration of the bug
reporter who sees his report being downgraded or even closed (!)
(see Bug #834964 for a very recent example) when it's quite clear
that the package does not really "build from source".

Thanks a lot.

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

Bug#834682: mina2: FTBFS in testing (failing tests)

[Santiago Vila]

On Wed, 7 Sep 2016, Markus Koschany wrote:

> I am attaching two build logs (cowbuilder and sbuild) that show no
> issues at all. The build succeeds.

Thanks a lot for trying to reproduce this.

There are still a lot of differences, we should better remove them all,
until our building environments are the same. Then it should fail
for you too (hopefully).

Would you please add this to the mix?:

* Use a stretch chroot (as reported).

* Build only arch-independent packages (as reported).
  This is the equivalent to "dpkg-buildpackage -A".
  In sbuild it's done with options "--arch-all --no-arch-any".

* The chroot should be as small as possible. Well, I don't do exactly
  that because most packages build-depend on debhelper, and I want
  to save disk I/O so I have debhelper by default, but on the other side
  I don't have gnupg installed.
  
  To simplify: Would you please install the packages in
  package-list.txt (attached) and only those?
  
[ This is of course only the starting point, sbuild should then
  automatically download and install the required packages ].

* I'm also using --resolve-alternatives option of sbuild. Don't know if
  it's relevant but we should try to minimize differences. There is at
  least one package that FTBFS if I didn't use this option, which is
  otherwise the default (AFAIK) in the official buildds.

* Build with only one CPU. This is achieved by putting this in .sbuildrc:

$ENV{'DEB_BUILD_OPTIONS'} = 'parallel=1';

* Finally, I'm building on machines with not a lot of memory, because
  monitoring /proc/meminfo tells me that I don't need more for this
  particular package (but maybe I'm wrong).
  
  Please try on a virtual machine having only 1GB RAM and 1 GB swap.


If you do all this, the probability that you will reproduce the bug
may only increase (but of course it may also continue to be zero).
In either case, we should try.

Thanks.adduser
apt
autoconf
automake
autopoint
autotools-dev
base-files
base-passwd
bash
binutils
bsdmainutils
bsdutils
build-essential
bzip2
coreutils
cpp
cpp-6
dash
debconf
debhelper
debian-archive-keyring
debianutils
dh-autoreconf
dh-strip-nondeterminism
diffutils
dmsetup
dpkg
dpkg-dev
e2fslibs
e2fsprogs
eatmydata
fakeroot
file
findutils
g++
g++-6
gcc
gcc-5-base
gcc-6
gcc-6-base
gettext
gettext-base
gpgv
grep
groff-base
gzip
hostname
init-system-helpers
initscripts
insserv
intltool-debian
less
libacl1
libapt-pkg5.0
libarchive-zip-perl
libasan3
libatomic1
libattr1
libaudit-common
libaudit1
libblkid1
libbsd0
libbz2-1.0
libc-bin
libc-dev-bin
libc-l10n
libc6
libc6-dev
libcap-ng0
libcc1-0
libcilkrts5
libcomerr2
libcroco3
libdb5.3
libdebconfclient0
libdevmapper1.02.1
libdpkg-perl
libeatmydata1
libfakeroot
libfdisk1
libffi6
libfile-stripnondeterminism-perl
libgcc-6-dev
libgcc1
libgcrypt20
libgdbm3
libglib2.0-0
libgmp10
libgomp1
libgpg-error0
libicu57
libisl15
libitm1
liblsan0
liblz4-1
liblzma5
libmagic-mgc
libmagic1
libmount1
libmpc3
libmpfr4
libmpx2
libncurses5
libncursesw5
libpam-modules
libpam-modules-bin
libpam-runtime
libpam0g
libpcre3
libperl5.22
libpipeline1
libquadmath0
libselinux1
libsemanage-common
libsemanage1
libsepol1
libsigsegv2
libsmartcols1
libss2
libstdc++-6-dev
libstdc++6
libsystemd0
libtimedate-perl
libtinfo5
libtool
libtsan0
libubsan0
libudev1
libunistring0
libustr-1.0-1
libuuid1
libxml2
linux-libc-dev
locales
login
lsb-base
m4
make
man-db
mawk
mount
multiarch-support
nano
ncurses-base
ncurses-bin
passwd
patch
perl
perl-base
perl-modules-5.22
po-debconf
sed
sensible-utils
startpar
sysv-rc
sysvinit-utils
tar
tzdata
util-linux
xz-utils
zlib1g
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

On Wed, Sep 07, 2016 at 02:05:45PM +0200, Markus Koschany wrote:
> I have just filed
> 
> http://bugs.debian.org/836940
> 
> against cowbuilder and sbuild and asked both maintainers for a
> clarification. Apparently apt moved the dependency on gnupg from Depends
> to Recommends in version 1.3~exp1 and together with the recent gnupg2
> transition, this caused a behavioral change in sbuild.

IMHO, the bug is a waste of time, and I can easily imagine what sbuild
maintainer will probably tell you: If it's not required to have gnupg
inside the chroot, then there is no point in requiring it to be inside
the chroot.

> >   11) Drop requirement for gpg inside the chroot as external archive keys 
> > are
> >   now processed without gpg and signing of the internal repository is
> >   entirely optional with helpful warning and error messages in case
> >   signing failed.
> > 
> > 
> > Please note that this bug is not just "xmlgraphics-commons FTBFS".
> > 
> > This bug is "xmlgraphics-commons FTBFS if gnupg is not in chroot".
> 
> Actually this is not a specific issue in xmlgraphics-commons but affects
> all packages that relied on gnupg being installed by default.

There are not so many of them. These are the ones I remember:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834600
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834744
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=835098

including this one. So "All packages" = 3 so far. This is after building
all 15000 source packages in stretch that generate "Arch: all" binary packages.

> This bug only surfaced three weeks ago. We could always rely on gnupg
> being installed by default.

No, actually you could not rely on gnupg being installed by default,
because gnupg was not essential and it was never was.

This bug was "hidden", so to speak, but it has always been a bug,
it's just now that we discovered it.

The "theory" has not changed: If you need a package during build, you
have to put it in build-depends. This is clearly written in policy.

If gnupg is installed by default and there is not a build-depends,
nobody will notice, but it's still a bug.

> This cannot be achieved by filing RC bugs against numerous affected
> packages.

Yes, it can, because they are RC bugs, they have always been, and
there are not so many packages affected.

I can count them with the fingers in my two hands, and I don't even
need to announce it as a mass bug filing.

> In my opinion this is inefficient and just increases the
> workload of contributors.

You are now worried by workload of contributors? How ironic.
My workload is increased every time I have to explain obvious
and well established things to people who ignore Debian Policy
regarding the set of build essential packages.

If you are really worried about workload of contributors, I suggest
you follow Debian Policy and raise this to serious, where it belongs.

> Debian Policy is not a document to force
> maintainers into implementing something, it rather reflects common best
> practices in this distribution.

I don't want to force anything. You don't have to fix this bug. Do
nothing and let the autoremoval procedure happen if you wish, but this
bug is serious because, as you say, that has been common best practice
for ages every time we have discovered a missing build-depends.

> By the way marking the bug as unreproducible just means that
> feedback from someone else is appreciated.

We already have "help" for that. When we know exactly and precisely
how to reproduce something (in this case, building without gnupg in
the chroot), we don't use unreproducible.

> > Before I take this to the Technical Committee, do you want to propose
> > a summary of the disagreement? This is not required but it's
> > recommended here in point 2:
> > 
> > https://www.debian.org/devel/tech-ctte
> > 
> > Thanks.
> 
> I suggest to wait until both cowbuilder and sbuild maintainers responded
> to #836940.

I suggest to raise the severity now, as I have already wasted too much
time explaining obvious things in this report, and don't like the idea
of wasting even more time.

Thanks.

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

On Wed, 7 Sep 2016, Emmanuel Bourg wrote:

> I haven't been able to reproduce this issue either with a clean pbuilder
> environment. For some reason gnupg was installed by default in the
> environment, but maybe this changed recently?

I don't know if this changed recently with pbuilder, but recent
versions of sbuild do not require gnupg to be present in the chroot.

This is from the NEWS file:

 * Major changes in 0.70.0:

  11) Drop requirement for gpg inside the chroot as external archive keys are
  now processed without gpg and signing of the internal repository is
  entirely optional with helpful warning and error messages in case
  signing failed.


Please note that this bug is not just "xmlgraphics-commons FTBFS".

This bug is "xmlgraphics-commons FTBFS if gnupg is not in chroot".

If you or Markus insist on building xmlgraphics-commons with gnupg in
the chroot, then it's not that you can't reproduce the bug, it's that
you are not even *trying* to reproduce the bug.

By definition, to reproduce the bug you need a chroot not having
gnupg installed. Successful builds with gnupg in the chroot do not
give any information at all regarding the reproducibility or
unreproducibility of this bug.

I think this was evident enough from my use of "missing build-depends"
in the subject and the patch that I attached, so I'm really surprised
(and disappointed) that I have to tell again what this bug is about.

I'm even more disappointed by the fact that this is a missing
build-depends and it's downgraded to normal when we have considered
missing build-depends as RC for *ages*.

Before I take this to the Technical Committee, do you want to propose
a summary of the disagreement? This is not required but it's
recommended here in point 2:

https://www.debian.org/devel/tech-ctte

Thanks.

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:

> I disagree with your bug severity. The build does not fail in a clean
> cowbuilder environment. I'm attaching my build log as proof.

The build log is just a proof that the build succeeded, but *not* a proof
that the environment was clean.

If you are unable to do it with pbuilder, please post a build log made
with sbuild using a chroot not containing gnupg.

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:

> You should rather work towards defining a common build environment
> standard in Debian [...]

You must be joking. There is already a "common build environment standard",
and it's called the set of build essential packages, of which gnupg is not
(not the old gnupg, not the new gnupg, not the old gnupg2, and not the
new gnupg1).

Everything which is required to build and it's not in build essential
must go in build-depends.

What part of this standard (the build essential set of packages, the
one that really counts, not the list of packages in the package
builder of the day) is the one that you don't understand?

It's in Policy 4.2, here is a quote:

 If build-time dependencies are specified, it *must* be possible to
 build the package and produce working binaries on a system with
 *only* essential and build-essential packages installed and also
 those required to satisfy the build-time relationships (including
 any implied relationships).


This is what you are still not doing with your pbuilder example.

You say "unreproducible", I say unwillingess to reproduce.

This is a must directive in policy, and everybody agrees that missing
build-depends are RC. Do you still disagree that this is severity
serious?

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

severity 834744 serious
tags 834744 - unreproducible
thanks

Sorry, but missing build-dependencies are RC, and they have always been.


On Mon, 22 Aug 2016, Markus Koschany wrote:

> This package builds fine in a clean cowbuilder chroot environment

No, it does not. If the chroot environment includes gnupg, then
it's *not* a clean chroot.

To reproduce, please build in a chroot *not* having gnupg installed.

If you can't do that with cowbuilder, try sbuild.

I attach a full build log.

Please attach also your build log made with sbuild in a chroot *not*
having gnupg installed, so that we can compare.

If you can't reproduce a bug you should ask the submitter for a way
to reproduce it, not silently downgrade the bug and mark it as
unreproducible without telling the submitter.

Moreover, the bug report clearly said "missing build-depends" (it is
in the subject and it's difficult to miss) and it even included a
patch. Are you really unable to reproduce it, or you just "don't want"
to reproduce it?

Thanks.

xmlgraphics-commons_2.1-1_amd64-20160818T113412Z.gz
Description: application/gzip
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#812676: maven-scm: FTBFS - test fails with Unparseable date exception

[Santiago Vila]

On Mon, 25 Jan 2016, Michael Tautschnig wrote:

> java.text.ParseException: Unparseable date: "Wed Oct  4 15:42:47 2006"

This happened to me today while checking for "dpkg-buildpackage -A" bugs.
I attach my build log.

> The full build log is attached; please do let me know if the problem is
> unreproducible, in which case I shall try to investigate further.

The problem seems to be random. I guess that if you try to build many
times, a small fraction of the times will fail with the same error.

I would say there is a real problem here, so if you have time and
motivation, go ahead and investigate.

We want package builds to always succeed, not just "most of the time",
so bugs that only happen in a random way are also bugs.

Thanks.

maven-scm_1.3-7_amd64-20160826T002925Z.gz
Description: application/gzip
__
This is the maintainer address of Debian's Java team
. 
Please use
debian-j...@lists.debian.org for discussions and questions.

Bug#834671: closed by Emmanuel Bourg <ebo...@apache.org> (Bug#834671: fixed in cup 0.11a+20060608-8)

[Santiago Vila]

On Tue, Aug 23, 2016 at 10:27:07AM +, Debian Bug Tracking System wrote:

> Files:
>  70c1a6ff3530b04e6ad62d33ff99592a 1969 java optional cup_0.11a+20060608-8.dsc
>  a17d8727b785eed718e448c9dca0b13c 6148 java optional 
> cup_0.11a+20060608-8.debian.tar.xz
>  6be68ae5d67dfc667d3582757e6a3612 127308 java optional 
> cup_0.11a+20060608-8_all.deb

Dear Debian Java Maintainers:

Thank you for fixing this bug.

I have a question: Is there a particular reason why you are still not
doing source-only uploads?

Source-only uploads are particularly interesting for "Arch: all"
packages, because it's a way to double-check for package correctness
(FTBFS bugs in particular).

Ordinary uploads for "Arch: any" are tested by all the arch-dependent
autobuilders, so the effect of not doing source-only uploads in "Arch: all"
packages is that they are tested a lot less than "Arch: any" packages.

Thanks.

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

Bug#835114: airlift-slice: FTBFS in testing

[Santiago Vila]

Package: airlift-slice
Version: 0.10-1
Severity: serious

Dear maintainer: This package FTBFS in testing.

-
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the foll
owing articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionExce
ption
dh_auto_build: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plex
us-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar 
-Dmaven.home=/usr/share/mav
en -Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-d
ebian.conf -Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.
plexus.classworlds.launcher.Launcher -s/etc/maven/settings-debian.xml 
-Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US returned exit code 1
-

You can find several failed build logs here:

https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/airlift-slice.html

so I'm not attaching a build log.

Thanks.

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

Bug#834913: libslf4j-java: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:libslf4j-java
Version: 1.7.21-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibslf4j-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   dh_auto_build -i -O--buildsystem=maven
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo package -DskipTests 
-Dnotimestamp=true -Dlocale=en_US
[INFO] Scanning for projects...
[INFO] 

[... snipped ...]

at 
org.apache.maven.surefire.junit4.JUnit4Provider.execute(JUnit4Provider.java:264)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:153)
at 
org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:124)
at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)


Results :

Failed tests: 
  
SimpleLoggerMultithreadedInitializationTest>MultithreadedInitializationTest.multiThreadedInitialization:46
 388 < 0+16

Tests run: 17, Failures: 1, Errors: 0, Skipped: 0

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] SLF4J .. SUCCESS [  0.694 s]
[INFO] SLF4J API Module ... SUCCESS [  5.988 s]
[INFO] SLF4J Simple Binding ... FAILURE [  1.166 s]
[INFO] SLF4J NOP Binding .. SKIPPED
[INFO] SLF4J JDK14 Binding  SKIPPED
[INFO] SLF4J LOG4J-12 Binding . SKIPPED
[INFO] SLF4J JCL Binding .. SKIPPED
[INFO] JCL 1.1.1 implemented over SLF4J ... SKIPPED
[INFO] Log4j Implemented Over SLF4J ... SKIPPED
[INFO] JUL to SLF4J bridge  SKIPPED
[INFO] SLF4J Migrator . SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 8.642 s
[INFO] Finished at: 2016-08-18T23:48:34+02:00
[INFO] Final Memory: 12M/35M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project slf4j-simple: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/slf4j-simple/target/surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :slf4j-simple
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo test returned exit code 1
debian/rules:4: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 

Bug#834890: commons-math: FTBFS with probability > 0 in a deliberate way

[Santiago Vila]

Package: src:commons-math
Version: 2.2-5
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
/usr/share/maven-debian-helper/copy-repo.sh /<>/debian
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibcommons-math-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo 
touch debian/stamp-poms-patched
# before-build target may be used to unpatch the pom files, so we need to check 
if
# patching the pom files is needed here, normally not
if [ ! -f pom.xml.save ]; then \

[... snipped ...]

Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec - in 
org.apache.commons.math.genetics.BinaryChromosomeTest
Running org.apache.commons.math.genetics.TournamentSelectionTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.genetics.TournamentSelectionTest
Running org.apache.commons.math.genetics.RandomKeyMutationTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.genetics.RandomKeyMutationTest
Running org.apache.commons.math.genetics.OnePointCrossoverTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.004 sec - in 
org.apache.commons.math.genetics.OnePointCrossoverTest
Running org.apache.commons.math.genetics.GeneticAlgorithmTestBinary
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.027 sec - in 
org.apache.commons.math.genetics.GeneticAlgorithmTestBinary
Running org.apache.commons.math.geometry.Vector3DTest
Tests run: 18, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.016 sec - in 
org.apache.commons.math.geometry.Vector3DTest
Running org.apache.commons.math.geometry.Vector3DFormatTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 sec - in 
org.apache.commons.math.geometry.Vector3DFormatTest
Running org.apache.commons.math.geometry.RotationOrderTest
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.002 sec - in 
org.apache.commons.math.geometry.RotationOrderTest
Running org.apache.commons.math.geometry.RotationTest
Tests run: 12, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.145 sec - in 
org.apache.commons.math.geometry.RotationTest
Running org.apache.commons.math.geometry.FrenchVector3DFormatTest
Tests run: 28, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.008 sec - in 
org.apache.commons.math.geometry.FrenchVector3DFormatTest

Results :

Failed tests: 
  GammaDistributionTest>ContinuousDistributionAbstractTest.testSampling:275 
Chisquare test failed p-value = 7.68153812779615E-4 chisquare statistic = 
16.8239998. 
value   expectedobserved
1   250 230
2   250 296
3   250 211
4   250 263
This test can fail randomly due to sampling error with probability 0.001.

Tests run: 2461, Failures: 1, Errors: 0, Skipped: 2

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 35.898 s
[INFO] Finished at: 2016-08-20T08:57:22+02:00
[INFO] Final Memory: 7M/17M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project commons-math: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/target/surefire-reports for the 
individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
/usr/share/cdbs/1/class/maven.mk:127: recipe for target 
'debian/stamp-maven-check' failed
make: *** [debian/stamp-maven-check] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Tests are supposed to be always successful.

Sometimes we have packages having tests which fail randomly. Some
people forgive them because we don't know the reason why they fail.

But this package has a 

Bug#834833: javassist: FTBFS too much often (failing tests)

[Santiago Vila]

Package: javassist
Version: 3.20.0-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed several times.

A diff between a successful build and a failed build shows this:

--
Tests run: 376, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 20.789 sec 
<<< FAILURE! - in javassist.JvstTest
testJIRA150(javassist.JvstTest4)  Time elapsed: 0.711 sec  <<< FAILURE!
junit.framework.AssertionFailedError: 326 < 3 * 79
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at javassist.JvstTest4.testJIRA150(JvstTest4.java:666)


Results :

Failed tests: 
  javassist.JvstTest4#testJIRA150 AssertionFailedError 326 < 3 * 79

Tests run: 376, Failures: 1, Errors: 0, Skipped: 0
--

So apparently there are some tests based on performance.

If that's the case, such tests must be disabled, as it's not written
anywhere that the performance of any given autobuilder will remain
constant during the package build.

Thanks.

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

Bug#834744: xmlgraphics-commons: FTBFS (missing build-depends on gnupg)

[Santiago Vila]

Package: src:xmlgraphics-commons
Version: 2.1-1
Severity: serious
Tags: patch

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
BUILD FAILED
/<>/build.xml:620: The following error occurred while executing 
this line:
/<>/build.xml:591: Execute failed: java.io.IOException: Cannot run 
program "gpg" (in directory "/<>"): error=2, No such file or 
directory


The gnupg package is not essential. Therefore, whenever a package
requires it for building there should be a build-dependency on it.

Trivial (but untested) patch below.

Thanks.

--- a/debian/control
+++ b/debian/control
@@ -8,6 +8,7 @@ Build-Depends: debhelper (>= 9), javahelper
 Build-Depends-Indep: ant-optional,
  default-jdk,
  default-jdk-doc,
+ gnupg,
  junit4,
  libcommons-io-java (>= 1.3.1),
  libcommons-logging-java,

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

Bug#834682: mina2: FTBFS too much often (failing tests)

[Santiago Vila]

Package: src:mina2
Version: 2.0.13-1
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep --buildsystem=maven
   dh_testdir -i -O--buildsystem=maven
   dh_update_autotools_config -i -O--buildsystem=maven
   dh_auto_configure -i -O--buildsystem=maven
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compiler/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-compilers/*/*.jar': No 
such file or directory
find: '/usr/share/maven-repo/org/codehaus/plexus/plexus-containers/*/*.jar': No 
such file or directory
mh_patchpoms -plibmina2-java --debian-build --keep-pom-version 
--maven-repo=/<>/debian/maven-repo
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- -f src/pom.xml package javadoc:aggregate
/usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo -f src/pom.xml package 
javadoc:aggregate -DskipTests -Dnotimestamp=true -Dlocale=en_US

[... snipped ...]

Running org.apache.mina.core.IoServiceListenerSupportTest
Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 1.026 sec - in 
org.apache.mina.core.IoServiceListenerSupportTest

Results :

Tests in error: 
  NioFileRegionTest.testSendLargeFile ?? IO Broken pipe

Tests run: 201, Failures: 0, Errors: 1, Skipped: 5

[INFO] 
[INFO] Reactor Summary:
[INFO] 
[INFO] Apache MINA  SUCCESS [  0.007 s]
[INFO] Apache MINA Core ... FAILURE [01:26 min]
[INFO] Apache MINA APR Transport .. SKIPPED
[INFO] Apache MINA Compression Filter . SKIPPED
[INFO] Apache MINA JavaBeans Integration .. SKIPPED
[INFO] Apache MINA XBean Integration .. SKIPPED
[INFO] Apache MINA OGNL Integration ... SKIPPED
[INFO] Apache MINA JMX Integration  SKIPPED
[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 01:27 min
[INFO] Finished at: 2016-08-09T06:00:19+02:00
[INFO] Final Memory: 11M/60M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-surefire-plugin:2.17:test (default-test) on 
project mina-core: There are test failures.
[ERROR] 
[ERROR] Please refer to /<>/src/mina-core/target/surefire-reports 
for the individual test results.
[ERROR] -> [Help 1]
[ERROR] 
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] 
[ERROR] For more information about the errors and possible solutions, please 
read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR] 
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn  -rf :mina-core
dh_auto_test: /usr/lib/jvm/default-java/bin/java -noverify -cp 
/usr/share/maven/boot/plexus-classworlds-2.x.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dmaven.home=/usr/share/maven 
-Dmaven.multiModuleProjectDirectory=/<> 
-Dclassworlds.conf=/etc/maven/m2-debian.conf 
-Dproperties.file.manual=/<>/debian/maven.properties 
org.codehaus.plexus.classworlds.launcher.Launcher 
-s/etc/maven/settings-debian.xml -Ddebian.dir=/<>/debian 
-Dmaven.repo.local=/<>/debian/maven-repo -f src/pom.xml test 
returned exit code 1
debian/rules:12: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

Bug#834679: surefire: FTBFS in testing (1 required artifact is missing)

[Santiago Vila]

Package: src:surefire
Version: 2.17-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
cd . && /usr/lib/jvm/default-java/bin/java -classpath 
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/maven-core.jar:/usr/share/java/maven-model.jar:/usr/share/java/maven-plugin-api.jar:/usr/share/java/maven-project.jar:/usr/share/java/plexus-utils.jar:/usr/share/java/plexus-container-default-alpha.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dant.home=/usr/share/ant org.apache.tools.ant.Main -Dpackage=surefire 
-Dversion=2.17 -buildfile debian/build.xml package 
Buildfile: /<>/debian/build.xml

package:
[mkdir] Created dir: 
/<>/surefire-grouper/target/generated-sources
   [javacc] Java Compiler Compiler Version 5.0 (Parser Generator)
   [javacc] (type "javacc" with no arguments for help)
   [javacc] Reading from file 
/<>/surefire-grouper/src/main/javacc/category-expression.jj . . .
   [javacc] File "TokenMgrError.java" does not exist.  Will create one.

[... snipped ...]

 [java] 1) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java]   Try downloading the file manually from the project website.
 [java] 
 [java]   Then, install it using the command: 
 [java]   mvn install:install-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file
 [java] 
 [java]   Alternatively, if you host your own repository you can deploy the 
file there: 
 [java]   mvn deploy:deploy-file -DgroupId=org.apache.commons 
-DartifactId=commons-lang3 -Dversion=3.x -Dpackaging=jar -Dfile=/path/to/file 
-Durl=[url] -DrepositoryId=[id]
 [java] 
 [java]   Path to dependency: 
 [java] 1) 
org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 2) org.apache.maven.surefire:maven-surefire-common:jar:debian
 [java] 3) org.apache.commons:commons-lang3:jar:3.x
 [java] 
 [java] --
 [java] 1 required artifact is missing.
 [java] 
 [java] for artifact: 
 [java]   org.apache.maven.plugins:maven-surefire-plugin:maven-plugin:2.17
 [java] 
 [java] from the specified remote repositories:
 [java]   central (https://repo1.maven.org/maven2)
 [java] 
 [java] 
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:361)
 [java] at 
org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:304)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.resolveTransitiveDependencies(DefaultPluginManager.java:1499)
 [java] at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:442)
 [java] at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
 [java] ... 9 more
 [java] [INFO] 

 [java] [INFO] Total time: 1 second
 [java] [INFO] Finished at: Tue Aug 16 17:42:30 CEST 2016
 [java] [INFO] Final Memory: 5M/13M
 [java] [INFO] 


BUILD FAILED
/<>/debian/build.xml:111: The following error occurred while 
executing this line:
/<>/debian/build.xml:34: The following error occurred while 
executing this line:
/usr/share/maven-ant-helper/maven-build.xml:325: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:320: The following error occurred 
while executing this line:
/usr/share/maven-ant-helper/maven-build.xml:297: Java returned: 1

Total time: 48 seconds
/usr/share/cdbs/1/class/ant.mk:39: recipe for target 'debian/stamp-ant-build' 
failed
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

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

Bug#834680: tomcat7: FTBFS in testing (failing tests)

[Santiago Vila]

Package: src:tomcat7
Version: 7.0.70-2
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_update_autotools_config -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
ant -propertyfile debian/ant.properties -Dyear=2016 -Dtoday='Aug 2 2016' 
-Dtstamp=09:43:11 -Ddistribution.name=Debian extras-jmx-remote deploy
Buildfile: /<>/build.xml

extras-prepare:
[mkdir] Created dir: /<>/output/extras
[mkdir] Created dir: /<>/output/extras-src-jars

[... snipped ...]

[junit] INFO: Starting test case [testDuplicatePaths_02]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-6"]
[junit] Aug 10, 2016 9:40:15 PM org.apache.catalina.startup.LoggingBaseTest 
setUp
[junit] INFO: Starting test case [testDuplicatePaths_03]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-7"]
[junit] Aug 10, 2016 9:40:15 PM org.apache.catalina.startup.LoggingBaseTest 
setUp
[junit] INFO: Starting test case [testDuplicatePaths_04]
[junit] Aug 10, 2016 9:40:15 PM org.apache.coyote.AbstractProtocol destroy
[junit] INFO: Destroying ProtocolHandler ["http-nio-127.0.0.1-auto-8"]
[junit] Running util.TestCookieFilter
[junit] Tests run: 10, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
0.038 sec

test-apr-exists:

test-apr:

cobertura-report:

test:
   [concat] Testsuites with skipped tests:
   [concat] TEST-org.apache.catalina.comet.TestCometProcessor.BIO.txt
   [concat] 
TEST-org.apache.catalina.loader.TestWebappClassLoaderThreadLocalMemoryLeak.BIO.txt
   [concat] 
TEST-org.apache.catalina.loader.TestWebappClassLoaderThreadLocalMemoryLeak.NIO.txt
   [concat] 
TEST-org.apache.catalina.session.TestStandardSessionIntegration.BIO.txt
   [concat] 
TEST-org.apache.catalina.session.TestStandardSessionIntegration.NIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWsWebSocketContainer.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.TestWsWebSocketContainerWithProxy.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.TestWsWebSocketContainerWithProxy.NIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.server.TestWsRemoteEndpointImplServer.BIO.txt
   [concat] 
TEST-org.apache.tomcat.websocket.server.TestWsRemoteEndpointImplServer.NIO.txt
   [concat] Testsuites with failed tests:
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClient.BIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClient.NIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.BIO.txt
   [concat] TEST-org.apache.tomcat.websocket.TestWebSocketFrameClientSSL.NIO.txt

BUILD FAILED
/<>/build.xml:1381: Some tests completed with an Error. See 
/<>/output/build/logs for details, search for "ERROR".

Total time: 43 minutes 27 seconds
debian/rules:31: recipe for target 'override_dh_auto_test' failed
make[1]: *** [override_dh_auto_test] Error 1
make[1]: Leaving directory '/<>'
debian/rules:18: recipe for target 'build-indep' failed
make: *** [build-indep] Error 2
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

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

Bug#834671: libxalan2-java: FTBFS in testing (Error: could not match input)

[Santiago Vila]

Package: src:libxalan2-java
Version: 2.7.1-9
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:


[...]
 debian/rules build-indep
dh_listpackages: -s/--same-arch is deprecated; please use -a/--arch instead
test -x debian/rules
mkdir -p "."
rm -f lib/BCEL.jar lib/regexp.jar
ln -s /usr/share/java/bcel.jar lib/BCEL.jar
ln -s /usr/share/java/regexp.jar lib/regexp.jar
jh_linkjars
jh_build -J   
touch debian/jh_build_stamp
cd . && /usr/lib/jvm/default-java/bin/java -classpath 
/usr/share/ant/lib/ant.jar:/usr/share/ant/lib/ant-launcher.jar:/usr/share/java/xml-apis.jar:/usr/share/java/xercesImpl.jar:/usr/share/java/bsf.jar:/usr/share/java/bcel.jar:/usr/share/java/cup.jar:/usr/share/java/regexp.jar:/usr/share/java/stylebook.jar:/usr/share/java/JLex.jar:/usr/lib/jvm/default-java/lib/tools.jar
 -Dgnu.java.awt.peer.gtk.Graphics=Graphics2D -Dant.home=/usr/share/ant 
org.apache.tools.ant.Main -Dcompile.debug=true -Dcompile.optimize=true 
-propertyfile /<>/debian/ant.properties jar xsltc.unbundledjar 
javadocs docs
Buildfile: /<>/build.xml


[... snipped ...]

[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 7 warnings

xalan-interpretive.compile:
 [echo] Compiling Xalan interpretive classes
[javac] /<>/build.xml:404: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 114 source files to /<>/build/classes
[javac] warning: [options] source value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] Note: Some input files use or override a deprecated API.
[javac] Note: Recompile with -Xlint:deprecation for details.
[javac] Note: Some input files use unchecked or unsafe operations.
[javac] Note: Recompile with -Xlint:unchecked for details.
[javac] 3 warnings
 [copy] Copying 12 files to /<>/build/classes
 [copy] Copying 1 file to 
/<>/build/classes/org/apache/xalan/res

xsltc.prepare:
 [echo] Compiling XSLTC utilities
[javac] /<>/build.xml:452: warning: 'includeantruntime' was 
not set, defaulting to build.sysclasspath=last; set to false for repeatable 
builds
[javac] Compiling 2 source files to /<>/build/classes
[javac] warning: [options] source value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] target value 1.5 is obsolete and will be removed 
in a future release
[javac] warning: [options] To suppress warnings about obsolete options, use 
-Xlint:-options.
[javac] 3 warnings

xsltc.java_cup:
 [echo] java_cup preparsing
 [java] Exception in thread "main" java.lang.Error: Error: could not match 
input
 [java] at java_cup.Lexer.zzScanError(Lexer.java:728)
 [java] at java_cup.Lexer.next_token(Lexer.java:1058)
 [java] at java_cup.parser.scan(parser.java:417)
 [java] at java_cup.runtime.lr_parser.parse(lr_parser.java:578)
 [java] at java_cup.Main.parse_grammar_spec(Main.java:477)
 [java] at java_cup.Main.main(Main.java:186)
 [java] at 
org.apache.xalan.xsltc.util.JavaCupRedirect.main(JavaCupRedirect.java:90)

BUILD FAILED
/<>/build.xml:481: Java returned: 1

Total time: 8 seconds
/usr/share/cdbs/1/class/ant.mk:39: recipe for target 'debian/stamp-ant-build' 
failed
make: *** [debian/stamp-ant-build] Error 1
dpkg-buildpackage: error: debian/rules build-indep gave error exit status 2


Because this source package only generates "Arch: all" packages, this
is the same as a FTBFS bug in the usual sense and the fact that I was
using "dpkg-buildpackage -A" is quite irrelevant.

For this particular package, I've also checked that it fails to build
from source in the reproducible builds site:

https://tests.reproducible-builds.org/

Thanks.

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

Bug#805228: Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

On Sat, 16 Jul 2016, tony mancill wrote:

> The first two packages I tried, src:pegdown and src:libjbcrypt-java,
> both appear in the "successfully built reproducibly" set here [1], and
> neither has any bugs assigned to it.  Maybe I'm looking in the wrong place?

If those packages generate only "Arch: all" packages and they build ok
in the reproducible builds setup, then those packages are ok.

The problem with the helper program you are using seems to be that it
makes "dpkg-buildpackage -A" to fail on packages generating both
"Arch: all" and "Arch: any" binary packages.

The same packages might appear as "ok" in reproducible builds because
they just test for "dpkg-buildpackage".

So, it is possible that there are no other affected packages than the
ones in my list.

Thanks.

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

Bug#805228: Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

On Sat, 16 Jul 2016, tony mancill wrote:

> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
> 
> Hi Santiago,
> 
> Thanks for the list.  For 806640, the only bug that appears in this list
> related to mh_install 805228, I will mark it as blocked by 805228, but I
> won't reassign.
> 
> It might be worth noting that there are other arch:all packages that
> FTBFS with the same mh_install issue, but don't appear in your list of
> binary-indep packages.  Did your test build perhaps exclude packages
> that are strictly arch:all - as compared to src:libnative-platform-java,
> which builds both arch:any and arch:all binary packages? [...]

Yes, I have only tested packages which generate both "Arch: any" and
"Arch: all" packages, so source packages which only generate "Arch: all"
packages are excluded from my tests.

The reason is that those packages are already tested (and reported)
in the reproducible builds project, so I decided to concentrate
on packages that nobody tested.

Thanks.

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

Bug#805228: Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

On Sat, 16 Jul 2016, Markus Koschany wrote:

> On 16.07.2016 18:22, tony mancill wrote:
> [...]
> > I'd like to discuss options with the Java Team.  For example, we could
> > change mh_install to ignore '-i' when not passed in conjunction with a
> > maven.ignoreRules file, or change the DH sequencer, and probably some
> > other better options that I'm not creative enough to think of right now.
> 
> Hi,
> 
> I think
> 
> https://bugs.debian.org/805228
> 
> is the best place to discuss this issue.

Indeed.


One thing that you might want to do is to identify the affected
packages. The complete list of bugs I reported regarding
"dpkg-buildpackage -A" is available here in case it helps:

https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org


Thanks.

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

Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

On Sat, 16 Jul 2016, tony mancill wrote:

> There are 320-odd packages that build-depend on maven-repo-helper,
> although only a subset of them will use the DH sequencer.  Still, I
> think the bug belongs there as a problem in the tool chain and not
> against all of the packages that depend on it.

Hi.

As Markus Koschany has pointed out, there is already a bug reported
specifically for that.

So, even if this is considered as a bug in maven-repo-helper, please
don't reassign the bugs to that package, because then it would be a
lot more difficult for me to track the affected packages.

Thanks.

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

Bug#806613: eclipse: FTBFS when built with dpkg-buildpackage -A (dh_install: eclipse-jdt missing files)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

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

Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

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

Bug#806020: ecj: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".

If you need help to fix this bug, please tag it as "help".

Thanks.

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

Bug#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

On Thu, 14 Jul 2016, Emmanuel Bourg wrote:

> openjfx builds fine with "dpkg-buildpackage"

But there is not a way to tell the official autobuilders that they
do "dpkg-buildpackage" alone. They always do either -A or -B, so no,
it does not build fine as far as the official autobuilders is concerned.

For the record: The security team does source-only uploads as a normal
thing, so in some sense they are already mandatory for them.


In either case, there is little point in discussing about this being
or not RC for stretch in this particular bug report. If you don't like
this to be a release goal for stretch, you should really talk to the
Release Managers.

This is the relevant bug if you are interested:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=830997

However, before doing so, please consider the following:

We can make this a release goal now, or we can wait for the stable
release after stretch, i.e. about two years from now.

There are more than 23700 source packages in the archive. Of those,
only 100 source packages are affected by this, and from those only 62
do not have a patch available. The number of "key packages" affected
is less than 24.

With all this I mean that the "right time" to make this issue RC is
probably now, for stretch, not in two years.

Sorry if I did not convince you. You can still try discussing with the
Release Managers if you wish, but if I were you, I would just make an
upload for openjfx and forget about the issue. Or maybe wait a week
for the severity to be raised. Or maybe even wait until the last minute
before the autoremoval from testing.

Even if the package is big (about 100MB), I believe that snapshot.debian.org
can deal with a package like that every few months without problems.

And, if you are worried about your own bandwidth, remember that you
can make a source-only upload with "dpkg-buildpackage -S".

Thanks.

P.S. It has been nice to discuss with you, but please talk to the
Release Managers, not to me. Really :-)

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

Bug#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

On Thu, 14 Jul 2016, Emmanuel Bourg wrote:

> > Or even better: Consider a source package which only builds "Arch: all"
> > binary packages. Suppose your package has a missing build-depends but
> > it builds ok in your computer because you have installed the
> > build-dependency in your chroot. Since you provide all the "Arch: all"
> > packages, would it be ok not to consider the FTBFS in an official
> > autobuilder as serious?
> 
> I agree but that's a different case, this is just a plain old FTBFS.
> This issue is about "dpkg-buildpackage" working but not
> "dpkg-buildpackage -A".

Not exactly. This issue is really about packages failing in the "Arch: all"
autobuilder, or, in other words, "packages which may not be uploaded
in source-only form". This includes not only source packages
generating both "Arch: all" and "Arch: any" packages (which I usually test)
but also source packages which only generate "Arch: all" packages
(which I don't test because people from reproducible builds already
test them).

Following your reasoning, this plain old FTBFS would not have to
be serious at all, because "since the maintainer already provides
the .deb packages, there is nothing to worry about".

See what I mean? The same logic you want to apply to some packages
would make bugs which we already consider serious not to be serious
anymore.

Thanks.

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

Bug#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

On Thu, 14 Jul 2016, Emmanuel Bourg wrote:

> Le 14/07/2016 à 14:08, Santiago Vila a écrit :
> 
> > Would you apply the same reasoning to a package which fails to
> > build from source in every arch-dependent autobuilder but still builds
> > fine without the -B flag?
> 
> No I wouldn't but that's a different case.
> 
> If I build on amd64 and do a binary upload I can't ignore build failures
> with -B, because the package won't be available on the other
> architectures and that's indeed a serious issue impacting the users. On
> the other hand, if -A fails I'm still able to upload the architecture
> independent packages and there is no impact for the users.
> 
> -A failures are only relevant for source only uploads, and as long as
> they aren't mandatory I don't think this kind of issue should have a
> severity higher than important.

What you call "binary upload" is mostly an upload which includes all
the "Arch: all" binary packages.

If you were able to provide all the "Arch: any" binary packages, failure
to build in the official autobuilders would not be serious, then?

Consider a package which is both Linux and Intel specific, only
buildable in amd64 and i386. With a little bit of trickery, you could
make an upload including all the required packages even if they fail
in the official autobuilders. Would this be ok? I don't think so.

Or even better: Consider a source package which only builds "Arch: all"
binary packages. Suppose your package has a missing build-depends but
it builds ok in your computer because you have installed the
build-dependency in your chroot. Since you provide all the "Arch: all"
packages, would it be ok not to consider the FTBFS in an official
autobuilder as serious? I don't think so either.

Thanks.

__
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#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

On Thu, 14 Jul 2016, Emmanuel Bourg wrote:

> Le 14/07/2016 à 12:23, Santiago Vila a écrit :
> 
> > So there should not be a problem with this bug being serious and no
> > upload happening immediately, because you have just shown that you are
> > not MIA.
> 
> Actually the problem with this bug being serious is that is will trigger
> the autoremoval of openjfx from testing. I don't think it's fair to
> remove packages from testing just because dpkg-buildpackage -A fails.
> The package is still buildable without the -A flag.

Hmm. A little bit of background:

Would you apply the same reasoning to a package which fails to
build from source in every arch-dependent autobuilder but still builds
fine without the -B flag? Surely not!

The requirement "packages must autobuild" has always been one of the
release goals. The only difference is that we have now an "Arch: all"
autobuilder, but IMHO such autobuilder should not be a second-class
citizen. They should be on the same level.

Thanks.

__
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#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

On Thu, 14 Jul 2016, Emmanuel Bourg wrote:

> Le 13/07/2016 à 22:45, Santiago Vila a écrit :
> 
> > I have the ok from the Release Managers to consider this issue
> > as RC for stretch.
> > 
> > I'm going to wait a week before raising severities, but since this bug
> > is in pending state, I'd appreciate if you could make an upload
> > before that.
> 
> Hi,
> 
> Uploading now a fixed version of openjfx would just be a waste of
> bandwidth and space on the mirrors and snapshot.debian.org (about 155MB)
> and I'd like to avoid that. According to the Oracle release schedule
> OpenJFX should have two new releases before the freeze, so I'd prefer
> the severity to be only changed shortly before the freeze if a release
> didn't happen.

Hi.

My suggestion to make an upload was only to clean up the list of bugs
a little bit.

I will change all the severities at once, but I'd just like to point
out that this is (or will be) just a release goal for stretch, not a
security bug in stable or anything like that.

So there should not be a problem with this bug being serious and no
upload happening immediately, because you have just shown that you are
not MIA.

Thanks.

__
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#825276: openjfx: FTBFS when built with dpkg-buildpackage -A (dh_install: Cannot find "build/javadoc/*")

[Santiago Vila]

Greetings.

I have the ok from the Release Managers to consider this issue
as RC for stretch.

I'm going to wait a week before raising severities, but since this bug
is in pending state, I'd appreciate if you could make an upload
before that.

Thanks.

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

Bug#816998: jpathwatch: FTBFS in stretch, build dependencies not in stretch

[Santiago Vila]

Package: src:jpathwatch
Version: 0.95-4
Severity: serious

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.

But the failure is build-depends related, so it has nothing to do
with the fact that I was doing "dpkg-buildpackage -A", hence
the serious severity.


[...]
Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
The following NEW packages will be installed:
  sbuild-build-depends-core-dummy
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/770 B of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 file:/<>/resolver-ouaOcq/apt_archive ./ 
sbuild-build-depends-core-dummy 0.invalid.0 [770 B]
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package sbuild-build-depends-core-dummy.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Preparing to unpack .../sbuild-build-depends-core-dummy.deb ...
Unpacking sbuild-build-depends-core-dummy (0.invalid.0) ...
Setting up sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges
Merged Build-Depends: debhelper (>= 9), javahelper, default-jdk (>= 2:1.8), bnd 
(>= 2.1.0), maven-repo-helper
Filtered Build-Depends: debhelper (>= 9), javahelper, default-jdk (>= 2:1.8), 
bnd (>= 2.1.0), maven-repo-helper
dpkg-deb: building package 'sbuild-build-depends-jpathwatch-dummy' in 
'/<>/resolver-fye126/apt_archive/sbuild-build-depends-jpathwatch-dummy.deb'.
OK
Get:1 file:/<>/resolver-fye126/apt_archive ./ InRelease
Ign:1 file:/<>/resolver-fye126/apt_archive ./ InRelease
Get:2 file:/<>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:2 file:/<>/resolver-fye126/apt_archive ./ Release [2119 B]
Get:3 file:/<>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:3 file:/<>/resolver-fye126/apt_archive ./ Release.gpg [299 B]
Get:4 file:/<>/resolver-fye126/apt_archive ./ Sources [252 B]
Get:5 file:/<>/resolver-fye126/apt_archive ./ Packages [571 B]
Reading package lists...
W: No sandbox user '_apt' on the system, can not drop privileges
Reading package lists...

+--+
| Install jpathwatch build dependencies (apt-based resolver)   |
+--+

Installing build dependencies
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 sbuild-build-depends-jpathwatch-dummy : Depends: default-jdk (>= 2:1.8) but it 
is not going to be installed
E: Unable to correct problems, you have held broken packages.
apt-get failed.
Package installation failed
Reading package lists...
Building dependency tree...
Reading state information...
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists...
Building dependency tree...
Reading state information...
The following packages will be REMOVED:
  sbuild-build-depends-core-dummy*
0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
After this operation, 0 B of additional disk space will be used.
(Reading database ... 
(Reading database ... 5%
(Reading database ... 10%
(Reading database ... 15%
(Reading database ... 20%
(Reading database ... 25%
(Reading database ... 30%
(Reading database ... 35%
(Reading database ... 40%
(Reading database ... 45%
(Reading database ... 50%
(Reading database ... 55%
(Reading database ... 60%
(Reading database ... 65%
(Reading database ... 70%
(Reading database ... 75%
(Reading database ... 80%
(Reading database ... 85%
(Reading database ... 90%
(Reading database ... 95%
(Reading database ... 100%
(Reading database ... 14543 files and directories currently installed.)
Removing sbuild-build-depends-core-dummy (0.invalid.0) ...
W: No sandbox user '_apt' on the system, can not drop privileges

Bug#806613: eclipse: FTBFS when built with dpkg-buildpackage -A (dh_install: eclipse-jdt missing files)

[Santiago Vila]

Package: src:eclipse
Version: 3.8.1-8
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep
   dh_testdir -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>'
dh_auto_build -- provision.cvs
ant provision.cvs
Buildfile: /<>/build.xml
 [echo] Build log is available in build_20151025202140.log
 [echo] uname -m: x86_64. Build eclipse on x86_64 for x86_64.


[... snipped ...]

   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795/artifacts.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795/content.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/cache.timestamps
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951/artifacts.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951/content.jar
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/timestamps190749078
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/history/144580191.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/platform.xml
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data/listener_1925729951
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/90/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data/672778795
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/81/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/61/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/3818263
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/232360089
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data/1185816634
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.osgi/bundles/101/data
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update/history
   [delete] Deleting 
/<>/debian/tmp/usr/lib/eclipse/configuration/org.eclipse.update
[apply] Applied sed to 5 files and 0 directories.
 [echo] /<>/build/eclipse-3.8.1-src/installation
[apply] Applied gunzip to 1 file and 0 directories.
[apply] Applied sed to 1 file and 0 directories.
[apply] Applied gzip to 1 file and 0 directories.
[apply] Applied sed to 3 files and 0 directories.
[mkdir] Created dir: /<>/debian/tmp/etc
 [move] Moving 1 file to /<>/debian/tmp/etc

BUILD SUCCESSFUL
Total time: 1 minute 28 seconds
make[1]: Leaving directory '/<>'
   debian/rules override_dh_install-indep
make[1]: Entering directory '/<>'
dh_install --indep
dh_install: eclipse-jdt missing files 
(usr/share/eclipse/dropins/jdt/plugins/org.eclipse.ant.launching_*.jar), 
aborting
debian/rules:105: recipe for target 'override_dh_install-indep' failed
make[1]: *** [override_dh_install-indep] Error 2
make[1]: Leaving directory '/<>'
debian/rules:6: recipe for target 'binary-indep' failed
make: *** [binary-indep] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one. The common hints are:

* If the only architecture-independent packages are dummy transitional
ones and they were released with jessie, the easy fix is to drop them
now.

* When using "dh", it is allowed to use (independently)
optional targets override_dh_foo-arch and override_dh_foo-indep
(for several values of "foo").


Once that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B" work
properly, the package would be suitable to be uploaded in source-only
form if you wish.

Thanks.

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

Bug#806630: libnative-platform-java: FTBFS when built with dpkg-buildpackage -A (mh_installjar fails)

[Santiago Vila]

Package: src:libnative-platform-java
Version: 0.10+dfsg-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 debian/rules build-indep
dh build-indep --with maven_repo_helper
   dh_testdir -i
   dh_auto_configure -i
   debian/rules override_dh_auto_build
make[1]: Entering directory '/<>/libnative-platform-java-0.10+dfsg'
make -f debian/Makefile
make[2]: Entering directory '/<>/libnative-platform-java-0.10+dfsg'
mkdir -p build/classes
javac -source 1.5 -target 1.5 -d build/classes -classpath 
/usr/share/java/joptsimple.jar 
src/main/java/net/rubygrapefruit/platform/Terminals.java 
src/main/java/net/rubygrapefruit/platform/FileSystems.java 
src/main/java/net/rubygrapefruit/platform/ProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/NativeIntegration.java 
src/main/java/net/rubygrapefruit/platform/Terminal.java 
src/main/java/net/rubygrapefruit/platform/SystemInfo.java 
src/main/java/net/rubygrapefruit/platform/MissingRegistryEntryException.java 
src/main/java/net/rubygrapefruit/platform/ThreadSafe.java 
src/main/java/net/rubygrapefruit/platform/Native.java 
src/main/java/net/rubygrapefruit/platform/TerminalSize.java 
src/main/java/net/rubygrapefruit/platform/PosixFile.java 
src/main/java/net/rubygrapefruit/platform/NativeException.java 
src/main/java/net/rubygrapefruit/platform/FileSystem.java 
src/main/java/net/rubygrapefruit/platform/package-info.java 
src/main/java/net/rubygrapefruit/platform/NativeIntegrationUnava
 ilableException.java 
src/main/java/net/rubygrapefruit/platform/WindowsRegistry.java 
src/main/java/net/rubygrapefruit/platform/Process.java 
src/main/java/net/rubygrapefruit/platform/PosixFiles.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/NativeLibraryLocator.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsTerminals.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultFileSystem.java 
src/main/java/net/rubygrapefruit/platform/internal/Platform.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperProcess.java 
src/main/java/net/rubygrapefruit/platform/internal/PosixFileSystems.java 
src/main/java/net/rubygrapefruit/platform/internal/WrapperTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultPosixFiles.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/AbstractTerm
 inals.java 
src/main/java/net/rubygrapefruit/platform/internal/AbstractTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/MutableTerminalSize.java 
src/main/java/net/rubygrapefruit/platform/internal/FileSystemList.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultWindowsRegistry.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultSystemInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminalCapabilities.java 
src/main/java/net/rubygrapefruit/platform/internal/MutableSystemInfo.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminfoTerminals.java 
src/main/java/net/rubygrapefruit/platform/internal/NativeLibraryLoader.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsProcessLauncher.java 
src/main/java/net/rubygrapefruit/platform/internal/DefaultProcess.java 
src/main/java/net/rubygrapefruit/platform/internal/LibraryDef.java 
src/main/java/net/rubygrapefruit/platform/internal/TerminfoTerminal.java 
src/main/java/net/ruby
 grapefruit/platform/internal/FileStat.java 
src/main/java/net/rubygrapefruit/platform/internal/WindowsTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsConsoleFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/NativeLibraryFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/jni/TerminfoFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsHandleFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixFileSystemFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/jni/PosixFileFunctions.java 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixProcessFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/WindowsRegistryFunctions.java
 
src/main/java/net/rubygrapefruit/platform/internal/jni/PosixTerminalFunctions.java
 src/main/java/net/rubygrapefruit/platform/internal/AnsiTerminal.java 
src/main/java/net/rubygrapefruit/platform/internal/FunctionResult.java
warning: [options] bootstrap class path not set in conjunction with -source 1.5
Note: src/main/java/net/rubygrapefruit/platform/internal/WrapperProcess.java 
uses unchecked or unsafe operations.

[... snipped ...]

-V --version: show the version

Bug#806020: ecj: FTBFS when built with dpkg-buildpackage -A (No such file or directory)

[Santiago Vila]

Package: src:ecj
Version: 3.10.1-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important

Dear maintainer:

I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:


[...]
 fakeroot debian/rules binary-indep
ls: cannot access /usr/bin/gcj: No such file or directory
test -x debian/rules
dh_testroot
dh_prep 
dh_installdirs -A 
mkdir -p "."
Adding cdbs dependencies to debian/libecj-java.substvars
dh_installdirs -plibecj-java 
mh_installpoms -plibecj-java
mh_installjar -plibecj-java -l debian/poms/ecj.pom build/dist/eclipse-ecj.jar \
--usj-name=eclipse-ecj
Cannot find the jar to install: build/dist/eclipse-ecj.jar
debian/rules:183: recipe for target 'install/libecj-java' failed
make: *** [install/libecj-java] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary-indep gave error exit 
status 2


Sorry not to have a fix, as I am reporting many bugs similar to
this one, but I can give some general hints:

* If all the arch-independent packages are dummy transitional packages
released with jessie, the easy fix is to drop them now.
 
* If not, debian/rules should be modified so that the binary-indep
target works in all cases, even when binary-arch is not used (this is
what the "Architecture: all" autobuilder does). For that:

* If you are using debhelper, you might want to use options -a and -i
for dh_* commands so that they do not act on packages they do not
have to act.

* Also, if you are using dh, the (independently) optional targets
override_dh_foo-arch and override_dh_foo-indep (for several values
of "foo") may be useful to write a debian/rules which behaves exactly
as desired.


After checking that both "dpkg-buildpackage -A" and "dpkg-buildpackage -B"
work properly, this package will be suitable to be uploaded in
source-only form if you wish (you might want to try it).

Thanks.

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