Processing of snappy-java_1.1.1.6-2_amd64.changes

snappy-java_1.1.1.6-2_amd64.changes uploaded successfully to localhost along with the files: snappy-java_1.1.1.6-2.dsc snappy-java_1.1.1.6-2.debian.tar.xz libsnappy-java_1.1.1.6-2_all.deb libsnappy-jni_1.1.1.6-2_amd64.deb Greetings, Your Debian queue daemon (running on host franck

Bug#780316: snappy-java: FTBFS: POM 'org.sonatype.oss:oss-parent' not found ... offline

Thank you for the suggestion, I'll apply it. The solution was to split the build target into -indep and -arch. I'll upload the fix shortly. __ This is the maintainer address of Debian's Java team . Please use debian-j.

Bug#780316: marked as done (snappy-java: FTBFS: POM 'org.sonatype.oss:oss-parent' not found ... offline)

Your message dated Thu, 12 Mar 2015 15:48:58 + with message-id and subject line Bug#780316: fixed in snappy-java 1.1.1.6-2 has caused the Debian Bug report #780316, regarding snappy-java: FTBFS: POM 'org.sonatype.oss:oss-parent' not found ... offline to be marked as done. This means that you

snappy-java_1.1.1.6-2_amd64.changes ACCEPTED into unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 12 Mar 2015 16:32:11 +0100 Source: snappy-java Binary: libsnappy-java libsnappy-jni Architecture: source all amd64 Version: 1.1.1.6-2 Distribution: unstable Urgency: medium Maintainer: Debian Java Maintainers Chang

Bug#780316: snappy-java: FTBFS: POM 'org.sonatype.oss:oss-parent' not found ... offline

Thanks for clarifying. I don't know why libsnappy-java.poms's --no-parent directive is only sometimes effective, but I do see that the reference to oss-parent comes from debian/pom.xml; why not simply remove or comment out that node? Also, purely as a matter of style, I'd suggest simplifying

Bug#780316: snappy-java: FTBFS: POM 'org.sonatype.oss:oss-parent' not found ... offline

Hi Aaron, Thank you for the report. snappy-java/1.1.1.6-1 already includes the --no-parent directive [1]. This error occurs when running 'debuild binary-arch', in this case the pom isn't patched as expected. A normal debuild works fine. I'm not a debhelper expert, suggestions on how to resolve thi

snappy-java_1.1.1.6-1_amd64.changes ACCEPTED into unstable, unstable

Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 26 Nov 2014 09:50:13 +0100 Source: snappy-java Binary: libsnappy-java libsnappy-jni Architecture: source all amd64 Version: 1.1.1.6-1 Distribution: unstable Urgency: low Maintainer: Debian Java Maintainers Changed-