Bug#774745: Upgrade to maven 3.1.1/3.2.5

2015-01-11 Thread Chris
Hi Emmanuel, > FYI the packaging of the new version has started but is blocked by nasty > build issues thanks for the info. Seems my google search skills where not that good. :-/ __ This is the maintainer address of Debian's Java team

Processing of lucene4_4.6.1+dfsg-3_amd64.changes

2015-01-11 Thread Debian FTP Masters
lucene4_4.6.1+dfsg-3_amd64.changes uploaded successfully to localhost along with the files: lucene4_4.6.1+dfsg-3.dsc lucene4_4.6.1+dfsg-3.debian.tar.xz liblucene4-java_4.6.1+dfsg-3_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) __ This is the mainta

lucene4_4.6.1+dfsg-3_amd64.changes ACCEPTED into unstable

2015-01-11 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Sun, 11 Jan 2015 09:10:47 -0800 Source: lucene4 Binary: liblucene4-java Architecture: source all Version: 1:4.6.1+dfsg-3 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Changed-By: tony manc

Bug#773829: #773829 lucene4: JavaCC parsers are not generated during the build

2015-01-11 Thread tony mancill
On 01/10/2015 06:26 PM, tony mancill wrote: > On 01/07/2015 10:41 PM, Niels Thykier wrote: >> Hi, >> >> If the bug is RC on its own, but you believe it is irrelevant for the >> Jessie release, the correct option would be to have it ignored (please >> file a bug against release.debian.org for that).

Bug#773829: marked as done (lucene4: JavaCC parsers are not generated during the build)

2015-01-11 Thread Debian Bug Tracking System
Your message dated Sun, 11 Jan 2015 17:33:32 + with message-id and subject line Bug#773829: fixed in lucene4 1:4.6.1+dfsg-3 has caused the Debian Bug report #773829, regarding lucene4: JavaCC parsers are not generated during the build to be marked as done. This means that you claim that the p

Bug#775010: libmaven-archiver-java: please allow pom.properties' date to be deterministic

2015-01-11 Thread solo-debianbugs
On Sat, Jan 10, 2015 at 10:19:19PM +0100, Emmanuel Bourg wrote: > Thank you for the update. It's safe to assume the date always follow the > comment specified, the Javadoc for the store() method states: > > "Next, a comment line is always written, consisting of an ASCII # > character, the current

Bug#775171: libapache-poi-java: CVE-2014-9527

2015-01-11 Thread Moritz Muehlenhoff
Package: libapache-poi-java Severity: important Tags: security Justification: user security hole This was assigned CVE-2014-9527: https://issues.apache.org/bugzilla/show_bug.cgi?id=57272 Could you please make a targeted fix for jessie? Cheers, Moritz __ This is the maintainer address of