[Bug 1978931] Re: `debsums -c` returns the error of /sbin/start-stop-daemon
Shih-Yuan Lee
1978931 at bugs.launchpad.net
Wed Jul 6 08:13:59 UTC 2022
** Description changed:
+ [Impact]
+
+ * Affects Canonical OEM images for Dell on focal and jammy
+
+ [Test Plan]
+
+ * Built Canonical OEM images for Dell on focal or jammy that includes
+ the latest Ubiquity packages.
+
+ * Use the customized image to install Ubuntu system
+
+ * Install debsums after the installation to check the system.
+
+ [Where problems could occur]
+
+ * N/A
+
+ [Other Info]
+
+ * Anything else you think is useful to include
+ * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
+ * and address these questions in advance
+
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
ubiquity 22.04.16
3) What you expected to happen
`debsums -c` returns no error.
4) What happened instead
`debsums -c` returns the error of /sbin/start-stop-daemon
We made the OEM jammy base image for Dell that contains dpkg
1.21.1ubuntu2 and then use dell-recovery (Ubiquity plugin) fish
mechanism to install/upgrade dpkg 1.21.1ubuntu2.1.
Because Ubiquity will rename it to /sbin/start-stop-daemon.REAL and provide a fake /sbin/start-stop-daemon during the installation.
When installing newer dpkg, /sbin/start-stop-daemon will be replaced. However Ubiquity will rename /sbin/start-stop-daemon.REAL back to /sbin/start-stop-daemon after the installation.
So /sbin/start-stop-daemon will be kept as the older one.
That is why the issue happens.
** Description changed:
[Impact]
- * Affects Canonical OEM images for Dell on focal and jammy
+ * Affects Canonical OEM images for Dell on focal and jammy
[Test Plan]
- * Built Canonical OEM images for Dell on focal or jammy that includes
- the latest Ubiquity packages.
+ * Built Canonical OEM images for Dell on focal or jammy that includes
+ the latest Ubiquity packages from *-proposed or *-updates.
- * Use the customized image to install Ubuntu system
+ * Use the customized image to install Ubuntu system
- * Install debsums after the installation to check the system.
+ * Install debsums after the installation to check the system.
[Where problems could occur]
- * N/A
+ * N/A
[Other Info]
-
- * Anything else you think is useful to include
- * Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
- * and address these questions in advance
+
+ * I have built and included the customized Ubiquity packages that
+ included the patch for focal and jammy so there should also be no
+ problem after we finished the SRU updates.
+
+ [Original Bug Description]
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
ubiquity 22.04.16
3) What you expected to happen
`debsums -c` returns no error.
4) What happened instead
`debsums -c` returns the error of /sbin/start-stop-daemon
We made the OEM jammy base image for Dell that contains dpkg
1.21.1ubuntu2 and then use dell-recovery (Ubiquity plugin) fish
mechanism to install/upgrade dpkg 1.21.1ubuntu2.1.
Because Ubiquity will rename it to /sbin/start-stop-daemon.REAL and provide a fake /sbin/start-stop-daemon during the installation.
When installing newer dpkg, /sbin/start-stop-daemon will be replaced. However Ubiquity will rename /sbin/start-stop-daemon.REAL back to /sbin/start-stop-daemon after the installation.
So /sbin/start-stop-daemon will be kept as the older one.
That is why the issue happens.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1978931
Title:
`debsums -c` returns the error of /sbin/start-stop-daemon
Status in OEM Priority Project:
In Progress
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Focal:
New
Status in ubiquity source package in Jammy:
New
Bug description:
[Impact]
* Affects Canonical OEM images for Dell on focal and jammy
[Test Plan]
* Built Canonical OEM images for Dell on focal or jammy that includes
the latest Ubiquity packages from *-proposed or *-updates.
* Use the customized image to install Ubuntu system
* Install debsums after the installation to check the system.
[Where problems could occur]
* N/A
[Other Info]
* I have built and included the customized Ubiquity packages that
included the patch for focal and jammy so there should also be no
problem after we finished the SRU updates.
[Original Bug Description]
1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu
Description: Ubuntu 22.04 LTS
Release: 22.04
2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center
ubiquity 22.04.16
3) What you expected to happen
`debsums -c` returns no error.
4) What happened instead
`debsums -c` returns the error of /sbin/start-stop-daemon
We made the OEM jammy base image for Dell that contains dpkg
1.21.1ubuntu2 and then use dell-recovery (Ubiquity plugin) fish
mechanism to install/upgrade dpkg 1.21.1ubuntu2.1.
Because Ubiquity will rename it to /sbin/start-stop-daemon.REAL and provide a fake /sbin/start-stop-daemon during the installation.
When installing newer dpkg, /sbin/start-stop-daemon will be replaced. However Ubiquity will rename /sbin/start-stop-daemon.REAL back to /sbin/start-stop-daemon after the installation.
So /sbin/start-stop-daemon will be kept as the older one.
That is why the issue happens.
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1978931/+subscriptions
More information about the foundations-bugs
mailing list