Processing of libcommons-validator-java_1.4.0-2_amd64.changes

2013-08-08 Thread Debian FTP Masters
libcommons-validator-java_1.4.0-2_amd64.changes uploaded successfully to localhost along with the files: libcommons-validator-java_1.4.0-2.dsc libcommons-validator-java_1.4.0-2.debian.tar.gz libcommons-validator-java_1.4.0-2_all.deb libcommons-validator-java-doc_1.4.0-2_all.deb

libcommons-validator-java_1.4.0-2_amd64.changes ACCEPTED into unstable

2013-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 08 Aug 2013 12:50:34 +0200 Source: libcommons-validator-java Binary: libcommons-validator-java libcommons-validator-java-doc Architecture: source all Version: 1:1.4.0-2 Distribution: unstable Urgency: low

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
Package: javahelper Version: 0.43 Severity: important I've tried listing my classpath JARs in both debian/manifest and in debian/rules (export CLASSPATH) Either way, the generated MANIFEST.MF is broken, because of the line wrapping issue, e.g. I have Class-Path: /usr/share/java/jar1.jar

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Emmanuel Bourg
Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make the initial line longer than this, it should

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in its UTF8-encoded form. If a value would make

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Niels Thykier
On 2013-08-08 15:15, Daniel Pocock wrote: On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be longer than 72 bytes (not characters), in

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:47, Niels Thykier wrote: On 2013-08-08 15:15, Daniel Pocock wrote: On 08/08/13 15:08, Emmanuel Bourg wrote: Manifest files support wrapped values, see: http://docs.oracle.com/javase/1.3/docs/guide/jar/jar.html#Notes%20on%20Manifest%20and%20Signature%20Files No line may be

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Niels Thykier
On 2013-08-08 15:49, Daniel Pocock wrote: [...] Just to clarify: you are suggesting that I should manually break the lines in debian/manifest at 72 characters No, jh_manifest will do that for you - whether you like it or not. and then the JVM will concatenate them back together again at

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 15:59, Niels Thykier wrote: On 2013-08-08 15:49, Daniel Pocock wrote: [...] Just to clarify: you are suggesting that I should manually break the lines in debian/manifest at 72 characters No, jh_manifest will do that for you - whether you like it or not. and then the JVM will

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Daniel Pocock
On 08/08/13 16:43, Emmanuel Bourg wrote: If you just want to set the classpath I suggest using jh_classpath instead. The debian/package.classpath file contains one line per jar and you don't have to care about the length of the lines: usr/share/java/foo.jar jar1.jar jar2.jar jar3.jar

Bug#719094: generates broken Class-Path in MANIFEST.MF

2013-08-08 Thread Emmanuel Bourg
If you just want to set the classpath I suggest using jh_classpath instead. The debian/package.classpath file contains one line per jar and you don't have to care about the length of the lines: usr/share/java/foo.jar jar1.jar jar2.jar jar3.jar __ This is the maintainer address of Debian's

libjuniversalchardet-java_1.0.3-1_amd64.changes ACCEPTED into unstable, unstable

2013-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 18 Jun 2013 14:22:51 +0200 Source: libjuniversalchardet-java Binary: libjuniversalchardet-java libjuniversalchardet-java-doc Architecture: source all Version: 1.0.3-1 Distribution: unstable Urgency: low Maintainer:

Comments regarding aspectj-maven-plugin_1.4-1_amd64.changes

2013-08-08 Thread Paul Richards Tagliamonte
Howdy maintainer, The correct DEP5 term for upstream's license is `Expat' not `MIT'. Please also comply with policy 4.9's requirement that get-orig-source can be invoked from anywhere (not just in the package root) It'd be nice to get both of these fixed in the next upload. Cheers, Paul

aspectj-maven-plugin_1.4-1_amd64.changes ACCEPTED into unstable, unstable

2013-08-08 Thread Debian FTP Masters
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sat, 22 Jun 2013 00:00:28 +0200 Source: aspectj-maven-plugin Binary: libaspectj-maven-plugin-java Architecture: source all Version: 1.4-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers