[Debian-med-packaging] Bug#697158: libsnappy1.0.3-java: Missing jar due to broken debian/links

[Jeremy Bicha]

Package: libsnappy1.0.3-java
Version: 1.0.3-rc3~dfsg-3
Severity: grave
Justification: renders package unusable

The two filenames in debian/links are in the wrong order, in other
words, /usr/share/java/snappy1.0.3-java.jar should be listed first.

Compare the two attached build logs to see that the current package is
missing the 23778 byte file /usr/share/java/snappy1.0.3-java.jar when
built in a clean chroot.

This bug caused picard-tools to fail to build on Ubuntu, but it builds
fine with the corrected debian/links:
https://bugs.launchpad.net/ubuntu/+source/picard-tools/+bug/1078012

Jeremy

- -- System Information:
Debian Release: wheezy/sid
  APT prefers raring-updates
  APT policy: (500, 'raring-updates'), (500, 'raring-security'), (500,
'raring'), (500, 'raring-proposed'), (100, 'raring-backports')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Versions of packages libsnappy1.0.3-java depends on:
ii  libsnappy1  1.0.5-2
-------------- next part --------------
A non-text attachment was scrubbed...
Name: fixed-debian-links.log
Type: application/octet-stream
Size: 142152 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20130101/ae360aaf/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: current.log
Type: application/octet-stream
Size: 130267 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/debian-med-packaging/attachments/20130101/ae360aaf/attachment-0003.obj>