libquartz-java is marked for autoremoval from testing

libquartz-java 1:1.8.6-3 is marked for autoremoval from testing on 2017-07-28 It is affected by these RC bugs: 864769: libquartz-java: Disable the update checker __ This is the maintainer address of Debian's Java team

ha-jdbc is marked for autoremoval from testing

ha-jdbc 2.0.16+rc1-3 is marked for autoremoval from testing on 2017-07-28 It (build-)depends on packages with these RC bugs: 864769: libquartz-java: Disable the update checker __ This is the maintainer address of Debian's Java team

uima-as is marked for autoremoval from testing

uima-as 2.3.1-5 is marked for autoremoval from testing on 2017-07-28 It (build-)depends on packages with these RC bugs: 864769: libquartz-java: Disable the update checker __ This is the maintainer address of Debian's Java team

shiro is marked for autoremoval from testing

shiro 1.3.2-1 is marked for autoremoval from testing on 2017-07-28 It (build-)depends on packages with these RC bugs: 864769: libquartz-java: Disable the update checker __ This is the maintainer address of Debian's Java team

activemq is marked for autoremoval from testing

activemq 5.14.3-3 is marked for autoremoval from testing on 2017-07-28 It (build-)depends on packages with these RC bugs: 864769: libquartz-java: Disable the update checker __ This is the maintainer address of Debian's Java team

Bug#865499: gradle fails to start in unstable after plexus-containers update

Package: gradle Version: 3.2.1-1 Severity: important Hi, It looks like the recent upload of plexus-containers1.5 [1] has left gradle in a bad way in unstable (and possibly soon in testing too). It fails to start, and running "gradle --stacktrace" results in a long stacktrace that includes this:

reproducible.debian.net status changes for zookeeper

2017-06-21 01:11 https://tests.reproducible-builds.org/debian/unstable/amd64/zookeeper changed from reproducible -> unreproducible 2017-06-21 03:17 https://tests.reproducible-builds.org/debian/unstable/amd64/zookeeper changed from unreproducible -> reproducible __ This is the maintainer

reproducible.debian.net status changes for apache-log4j2

2017-06-21 18:45 https://tests.reproducible-builds.org/debian/unstable/amd64/apache-log4j2 changed from unreproducible -> FTBFS __ This is the maintainer address of Debian's Java team . Please use

reproducible.debian.net status changes for libcommons-collections4-java

2017-06-21 21:56 https://tests.reproducible-builds.org/debian/unstable/amd64/libcommons-collections4-java changed from FTBFS -> reproducible __ This is the maintainer address of Debian's Java team . Please use

Processed: reassign 865354 eclipse

Processing commands for cont...@bugs.debian.org: > reassign 865354 eclipse Bug #865354 [libtomcat8-java] java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager Bug reassigned from package 'libtomcat8-java' to 'eclipse'. No longer marked as found in versions tomcat8/8.5.14-2. Ignoring

Bug#865354: java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager

OK, just sent a message to try to reassign it to eclipse (first time I've tried this! Hoping the reporter can do the reassign, not a maintainer...). Emmanuel Bourg writes: >Le 20/06/2017 à 21:48, Joe Pfeiffer a écrit : > >> So... should this bug be reported against eclipse (or, I suppose, >>

zookeeper_3.4.10-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 21 Jun 2017 11:47:20 -0700 Source: zookeeper Binary: libzookeeper-java zookeeper zookeeperd libzookeeper-java-doc libzookeeper-mt2 libzookeeper-st2 libzookeeper2 libzookeeper-mt-dev libzookeeper-st-dev

Processing of zookeeper_3.4.10-2_amd64.changes

zookeeper_3.4.10-2_amd64.changes uploaded successfully to localhost along with the files: zookeeper_3.4.10-2.dsc zookeeper_3.4.10-2.debian.tar.xz libzookeeper-java-doc_3.4.10-2_all.deb libzookeeper-java_3.4.10-2_all.deb libzookeeper-mt-dev_3.4.10-2_amd64.deb

Processed: Pending fixes for bugs in the jython package

Processing commands for cont...@bugs.debian.org: > tag 864859 + pending Bug #864859 {Done: Markus Koschany } [src:jython] jython: CVE-2016-4000: Unsafe deserialization leads to code execution Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need

Bug#864859: Pending fixes for bugs in the jython package

tag 864859 + pending thanks Some bugs in the jython package are closed in revision fa94dba7f47bf6e245a0016e840e8f3b817000ca in branch ' jessie' by Markus Koschany The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/jython.git/commit/?id=fa94dba Commit message: Import

hsqldb_2.4.0-2_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Wed, 21 Jun 2017 17:38:08 +0200 Source: hsqldb Binary: libhsqldb-java libhsqldb-java-doc hsqldb-utils Architecture: source Version: 2.4.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Processing of hsqldb_2.4.0-2_source.changes

hsqldb_2.4.0-2_source.changes uploaded successfully to localhost along with the files: hsqldb_2.4.0-2.dsc hsqldb_2.4.0-2.debian.tar.xz hsqldb_2.4.0-2_amd64.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __ This is the maintainer address of

conversant-disruptor_1.2.10-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jun 2017 13:53:14 +0200 Source: conversant-disruptor Binary: libconversant-disruptor-java Architecture: source Version: 1.2.10-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

tomcat8_8.5.15-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jun 2017 13:00:44 +0200 Source: tomcat8 Binary: tomcat8-common tomcat8 tomcat8-user libtomcat8-java libtomcat8-embed-java libservlet3.1-java libservlet3.1-java-doc tomcat8-admin tomcat8-examples tomcat8-docs

Processing of conversant-disruptor_1.2.10-1_source.changes

conversant-disruptor_1.2.10-1_source.changes uploaded successfully to localhost along with the files: conversant-disruptor_1.2.10-1.dsc conversant-disruptor_1.2.10.orig.tar.xz conversant-disruptor_1.2.10-1.debian.tar.xz conversant-disruptor_1.2.10-1_source.buildinfo Greetings,

Processing of tomcat8_8.5.15-1_source.changes

tomcat8_8.5.15-1_source.changes uploaded successfully to localhost along with the files: tomcat8_8.5.15-1.dsc tomcat8_8.5.15.orig.tar.xz tomcat8_8.5.15-1.debian.tar.xz tomcat8_8.5.15-1_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org) __

Processed: Pending fixes for bugs in the tomcat8 package

Processing commands for cont...@bugs.debian.org: > tag 864447 + pending Bug #864447 {Done: Emmanuel Bourg } [src:tomcat8] tomcat8: CVE-2017-5664: Security constrained bypass in error page mechanism Ignoring request to alter tags of bug #864447 to the same tags previously set >

Bug#864447: Pending fixes for bugs in the tomcat8 package

tag 864447 + pending thanks Some bugs in the tomcat8 package are closed in revision b8a566435d0f49d29acfea3654cda356977372c1 in branch ' stretch' by Emmanuel Bourg The full diff can be seen at https://anonscm.debian.org/cgit/pkg-java/tomcat8.git/commit/?id=b8a5664 Commit message: Fixed

apache-log4j2_2.8.2-1_source.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Wed, 21 Jun 2017 12:55:58 +0200 Source: apache-log4j2 Binary: liblog4j2-java liblog4j2-java-doc Architecture: source Version: 2.8.2-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes is NEW

binary:libnetty-tcnative-1.1-java is NEW. binary:libnetty-tcnative-1.1-jni is NEW. binary:libnetty-tcnative-1.1-jni is NEW. binary:libnetty-tcnative-1.1-java is NEW. source:netty-tcnative-1.1 is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to

Processing of apache-log4j2_2.8.2-1_source.changes

apache-log4j2_2.8.2-1_source.changes uploaded successfully to localhost along with the files: apache-log4j2_2.8.2-1.dsc apache-log4j2_2.8.2.orig.tar.xz apache-log4j2_2.8.2-1.debian.tar.xz apache-log4j2_2.8.2-1_source.buildinfo Greetings, Your Debian queue daemon (running on host

Processing of netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes

netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes uploaded successfully to localhost along with the files: netty-tcnative-1.1_1.1.33.Fork26-2.dsc netty-tcnative-1.1_1.1.33.Fork26.orig.tar.xz netty-tcnative-1.1_1.1.33.Fork26-2.debian.tar.xz libnetty-tcnative-1.1-java_1.1.33.Fork26-2_all.deb

netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes REJECTED

netty-tcnative-1.1_1.1.33.Fork26-2.dsc: Refers to non-existing file 'netty-tcnative-1.1_1.1.33.Fork26.orig.tar.xz' Perhaps you need to include the file in your upload? === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new

Processing of netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes

netty-tcnative-1.1_1.1.33.Fork26-2_amd64.changes uploaded successfully to localhost along with the files: netty-tcnative-1.1_1.1.33.Fork26-2.dsc netty-tcnative-1.1_1.1.33.Fork26-2.debian.tar.xz libnetty-tcnative-1.1-java_1.1.33.Fork26-2_all.deb

netty-tcnative-1.1_1.1.33.Fork26-2_source.changes REJECTED

Source-only uploads to NEW are not allowed. binary:libnetty-tcnative-1.1-java is NEW. binary:libnetty-tcnative-1.1-jni is NEW. source:netty-tcnative-1.1 is NEW. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which

Processing of netty-tcnative-1.1_1.1.33.Fork26-2_source.changes

netty-tcnative-1.1_1.1.33.Fork26-2_source.changes uploaded successfully to localhost along with the files: netty-tcnative-1.1_1.1.33.Fork26-2.dsc netty-tcnative-1.1_1.1.33.Fork26.orig.tar.xz netty-tcnative-1.1_1.1.33.Fork26-2.debian.tar.xz

Bug#865354: java.lang.NoClassDefFoundError: org/apache/tomcat/InstanceManager

Le 20/06/2017 à 21:48, Joe Pfeiffer a écrit : > So... should this bug be reported against eclipse (or, I suppose, > eclipse-platform-data)? And can you suggest a workaround? Considering that InstanceManager is properly built by tomcat8 I think this is indeed an eclipse issue and the bug should