Bug#769267: javamail: FTBFS in jessie/i386: tests failures

Hi Emmanuel, On 12/11/14 at 17:24 +0100, Emmanuel Bourg wrote: I haven't been able to reproduce this error on i386. On my machine IMAPIdleUntaggedResponseTest completed in about 2 seconds. I can confirm that it still fails for me (on amd64, but not on i386) when building with sbuild. However,

libjchart2d-java_3.2.2+dfsg-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sat, 25 Oct 2014 19:38:46 +0200 Source: libjchart2d-java Binary: libjchart2d-java libjchart2d-java-doc Architecture: source all Version: 3.2.2+dfsg-1 Distribution: unstable Urgency: medium Maintainer: Debian Java

noggit_0.6-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 11 Nov 2014 23:22:28 +0100 Source: noggit Binary: libnoggit-java Architecture: source all Version: 0.6-1 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers

Bug#766977: elasticsearch not starting

On Thu, 2014-11-06 at 00:50 +0100, Hilko Bengen wrote: I ended up with systemd at some point, too. And I still have no idea how to debug daemon startup problems. :-( Is there someone among the systemd maintainers who might be willing to lend a hand here? Jamie __ This is the maintainer

Processed: severity of 767541 is grave

Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 severity 767541 grave Bug #767541 [src:jenkins] jenkins: CVE-2014-3665 Severity set to 'grave' from 'important' End of message, stopping processing here. Please contact

Bug#768220: dupe of #722665?

This sounds more like a dupe of #722665 where the fault is that libjackson-json-java never should've had the symlink called jackson-core-java... Renaming the versionless jar symlink in -core would break other software (dogtag-pki for instance). So update libjackson-json-java in wheezy instead?

Bug#768715: really ship this VM in jessie?

We're trying to limit the number of VMs which need to be supported in a stable release. Is it really necessary to ship this one in jessie and have security support for it? __ This is the maintainer address of Debian's Java team

Bug#768715: really ship this VM in jessie?

Le 14/11/2014 08:17, Matthias Klose a écrit : We're trying to limit the number of VMs which need to be supported in a stable release. Is it really necessary to ship this one in jessie and have security support for it? Yes please, this is an important VM for Java developers. The security