start-stop-daemon fails debsums check
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
live-build (Ubuntu) |
Fix Released
|
High
|
Adam Conrad | ||
Trusty |
Fix Released
|
High
|
Adam Conrad | ||
Vivid |
Fix Released
|
Undecided
|
Adam Conrad | ||
Wily |
Fix Released
|
High
|
Adam Conrad |
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-
/bin/hostname (should be from the release pocket version of hostname)
/usr/sbin/
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-
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:/
Rgds!
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: dpkg 1.17.5ubuntu5.3
ProcVersionSign
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)
affects: | dpkg (Ubuntu) → live-build (Ubuntu) |
Changed in live-build (Ubuntu Wily): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in live-build (Ubuntu Trusty): | |
importance: | Undecided → High |
status: | Confirmed → Triaged |
Changed in live-build (Ubuntu): | |
status: | Confirmed → Triaged |
importance: | Undecided → High |
description: | updated |
Changed in live-build (Ubuntu Trusty): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in live-build (Ubuntu Vivid): | |
assignee: | nobody → Adam Conrad (adconrad) |
Changed in live-build (Ubuntu Wily): | |
assignee: | nobody → Adam Conrad (adconrad) |
description: | updated |
The above mentioned system also reports problem (debsums -c) with /boot/vmlinuz- 3.13.0- 32-generic. 7e5ad6294527413 10 vmlinuz- 3.13.0- 32-generic. I couldn't find that hash anywhere online. 3.13.0- 32-generic downloaded from http:// packages. ubuntu. com/trusty/ amd64/linux- image-3. 13.0-32- generic/ download is: 70f26e2f62b9dc8 ee05309fe96170e e7 vmlinuz- 3.13.0- 32-generic.
My md5sum is: 144bf4beed11fb7
Hash of vmlinuz-
There was no problem with debsums in the system when I installed it from 14.04-amd64.iso right after Trusty was released.