pkgstripfiles: symlinks doc files but leaves records in md5sums

[Steve Langasek]

A number of bugs in the vtk package have been picked up by lintian as part of NEW processing. The lintian messages, and corresponding explanations, are listed below:

E: libvtk-java: md5sums-lists-nonexisting-file usr/share/doc/libvtk-java/changelog.Debian.gz
E: libvtk5-dev: md5sums-lists-nonexisting-file usr/share/doc/libvtk5-dev/changelog.Debian.gz
E: libvtk5.6-qt4: md5sums-lists-nonexisting-file usr/share/doc/libvtk5.6-qt4/changelog.Debian.gz
E: tcl-vtk: md5sums-lists-nonexisting-file usr/share/doc/tcl-vtk/changelog.Debian.gz
N:
N: The md5sums control file lists a file which is not included in the
N: package.
N:
N: Usually, this error occurs during the package build process, if the
N: debian/tmp/ directory is touched after dh_md5sums or debstd is run.
N:
N: If all the files in the DEBIAN/ subdirectory are listed above, the
N: problem was probably caused by building the package using a buggy
N: debstd/debmake. In this case, rebuilding the package with an updated
N: debstd should fix the problem.
N:
N: Severity: important, Certainty: certain
N:

W: libvtk-java: postinst-has-useless-call-to-ldconfig
N:
N: The postinst script calls ldconfig even though no shared libraries are
N: installed in a directory controlled by the dynamic library loader.
N:
N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) for details.
N:
N: Severity: minor, Certainty: certain
N:
W: libvtk-java: postrm-has-useless-call-to-ldconfig
N:
N: The postrm script calls ldconfig even though no shared libraries are
N: installed in a directory controlled by the dynamic library loader.
N:
N: Refer to Debian Policy Manual section 8.1.1 (ldconfig) for details.
N:
N: Severity: minor, Certainty: certain
N:

I'm really not sure what's going on with the changelogs; this may point to a bug in pkgbinarymangler rather than in vtk.

[Steve Langasek (vorlon)]

Confirmed that this is a bug in pkgbinarymangler; have just seen the same problem in another package in NEW. Martin, this seems to have been introduced in pkgstripfiles in pbm 96. Can you fix this to make sure md5sums files get updated in tandem with documentation removals from packages?

[Launchpad Janitor (janitor)]

This bug was fixed in the package pkgbinarymangler - 100

---------------
pkgbinarymangler (100) oneiric; urgency=low

  * test/run: Add forgotten check_deb_integrity() to documentation symlink
    tests. This catches the wrong md5sums of symlinked doc files.
  * pkgstripfiles: Remove doc files from md5sums which get replaced with a
    symlink. (LP: #795845)
  * test/run: Call check_deb_integrity() in build(), and remove the explicit
    call from all the individual tests. There is no situation where we expect
    broken debs to be created, so this saves us from accidentally forgetting
    to call it in newly created tests.
  * test/run: Drop separate check_translation_tarball() test, and integrate it
    into check_deb_mo(). We now want to move to only building translation
    tarballs for packages which we actually strip, so it does not make sense
    any more to check those two individually.
  * pkgstriptranslations: Do not build a translation tarball if we did not
    strip the packages. With that, Launchpad does not need to check the
    component of the package any more, but can just import everything we throw
    at it. This also allows us to put some selected universe packages under
    langpack support. (LP: #788685, part 1)
  * pkgstriptranslations: Force stripping and translation tarball build if
    debian/control has "X..-Ubuntu-Use-Langpack: yes" header. Add
    corresponding test case. (LP: #788685, part 2)
  * test/run: Fix ResourceWarnings for unclosed files. Python 3, you are
    overly picky!
 -- Martin Pitt <email address hidden> Wed, 15 Jun 2011 09:08:54 +0200