[Bug 795845] Re: lintian errors in latest vtk binaries

[Steve Langasek]

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?

** Changed in: pkgbinarymangler (Ubuntu)
       Status: New => Triaged

** Changed in: pkgbinarymangler (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Summary changed:

- lintian errors in latest vtk binaries
+ pkgstripfiles: removes changelogs but leaves records in md5sums

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to pkgbinarymangler in Ubuntu.
https://bugs.launchpad.net/bugs/795845

Title:
  pkgstripfiles: removes changelogs but leaves records in md5sums

Status in “pkgbinarymangler” package in Ubuntu:
  Triaged
Status in “vtk” package in Ubuntu:
  Confirmed

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pkgbinarymangler/+bug/795845/+subscriptions