[Bug 1363519] Re: start-stop-daemon fails debsums check

[Brian Murray]

Hello Rafał, or anyone else affected,

Accepted live-build into vivid-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/live-
build/3.0~a57-1ubuntu16.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: live-build (Ubuntu Vivid)
       Status: New => Fix Committed

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

Title:
  start-stop-daemon fails debsums check

Status in live-build package in Ubuntu:
  Fix Released
Status in live-build source package in Trusty:
  Fix Committed
Status in live-build source package in Vivid:
  Fix Committed
Status in live-build source package in Wily:
  Fix Released

Bug description:
  [ SRU Justification ]
  Currently, systems installed from live media have several critical files (like initctl and start-stop-daemon) failing debsums checks because they are incorrectly using the files from the release pocket versions of their packages, rather than the -updates version that's actually installed.

  [ Test Case ]
  Build a test CD, run through an install, and verify that, post-install, all the files referenced in the patches are the expected content.  Those files are:

  For trusty:
  /sbin/initctl (should be from the -updates version of upstart)
  /sbin/start-stop-daemon (should be from the -updates version of dpkg)
  /bin/hostname (should be from the release pocket version of hostname)
  /usr/sbin/policy-rc.d (should not exist on the filesystem, post-install)

  For vivid:
  /sbin/initctl (should be from the -updates version of upstart)
  None of the other packages have had an SRU in vivid.

  [ Regression Potential ]
  Assuming the above test case passes, pretty minimal.  The change isn't invasive, except for swapping silly mv && do_stuff && mv semantics with more correct dpkg-divert add/remove.

  [ Original Report ]
  After fresh install from 14.04.1-amd64-dvd - debsums -c results in: /sbin/start-stop-daemon. I checked dpkg package with dpkg -s dpkg and got: Status: install ok installed, Version: 1.17.5ubuntu5.3 (the latest version) but when I did md5sum /sbin/start-stop-daemon, I got b1b8894ae2e3b547dca0e288634cce4a, which is md5sum for start-stop-daemon from dpkg version 1.17.5ubuntu5!
  I confirmed the problem in Ubuntu/Xubuntu 14.04.1-i386 (VirtualBox) - the same case - latest version of dpkg package contains older version of start-stop-daemon. I guess this is the same problem I reported here: https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1150737. I fixed the problem with sudo apt-get install --reinstall dpkg - simple if You know about it, otherwise You have outdated/buggy/ package/system...
  Rgds!

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: dpkg 1.17.5ubuntu5.3
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Aug 30 23:47:41 2014
  InstallationDate: Installed on 2014-08-07 (23 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
  SourcePackage: dpkg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/live-build/+bug/1363519/+subscriptions