Processed: found 786378 in libguava-java-doc/18.0-3

2015-07-04 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: > found 786378 libguava-java-doc/18.0-3 Bug #786378 [libguava18-java-doc] libguava18-java-doc and libguava-java-doc: error when trying to install together The source libguava-java-doc and version 18.0-3 do not appear to match any binary packages M

openjfx 8u40-b25-2 MIGRATED to testing

2015-07-04 Thread Debian testing watch
FYI: The status of the openjfx source package in Debian's testing distribution has changed. Previous version: 8u40-b25-1 Current version: 8u40-b25-2 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will r

user-agent-utils 1.16-1 MIGRATED to testing

2015-07-04 Thread Debian testing watch
FYI: The status of the user-agent-utils source package in Debian's testing distribution has changed. Previous version: 1.15-1 Current version: 1.16-1 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will

jackrabbit_2.3.6-1+deb8u1_amd64.changes ACCEPTED into proposed-updates->stable-new, proposed-updates

2015-07-04 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 25 Jun 2015 18:47:39 +0200 Source: jackrabbit Binary: libjackrabbit-java Architecture: source all Version: 2.3.6-1+deb8u1 Distribution: jessie-security Urgency: medium Maintainer: Debian Java Maintainers Changed-

Bug#787316: marked as done (CVE-2015-1833)

2015-07-04 Thread Debian Bug Tracking System
Your message dated Sat, 04 Jul 2015 18:17:05 + with message-id and subject line Bug#787316: fixed in jackrabbit 2.3.6-1+deb8u1 has caused the Debian Bug report #787316, regarding CVE-2015-1833 to be marked as done. This means that you claim that the problem has been dealt with. If this is not

Bug#791446: liblog4j1.2-java: org/apache/log4j/pattern is missing from .jar.

2015-07-04 Thread Hilko Bengen
Package: liblog4j1.2-java Version: 1.2.17-5 Severity: grave I am trying to build apache-log4j-extras1.2 (a dependency for Elasticsearch 1.6) and am failing because a number of symbols cannot be resolved, see below. It turns out that those classes are present in the jar file -- and also in the sour

Processed: Re: Bug#791446: liblog4j1.2-java: org/apache/log4j/pattern is missing from .jar.

2015-07-04 Thread Debian Bug Tracking System
Processing control commands: > tag -1 patch Bug #791446 [liblog4j1.2-java] liblog4j1.2-java: org/apache/log4j/pattern is missing from .jar. Added tag(s) patch. -- 791446: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791446 Debian Bug Tracking System Contact ow...@bugs.debian.org with proble

Bug#791446: liblog4j1.2-java: org/apache/log4j/pattern is missing from .jar.

2015-07-04 Thread Hilko Bengen
Control: tag -1 patch * Hilko Bengen: > All of the missing classes are in the org/apache/log4j/pattern directory > which is missing from the jar that ships with this package. Apparently the build.xml file that is used to build the jar has not been kept up-to-date. The patch below seems to fix th