Remove obsolete versioned dependency on initramfs-tools Edit

Bug #1721626 reported by Steve Langasek on 2017-10-05
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
console-setup (Ubuntu)
Undecided
Unassigned
Xenial
Undecided
Steve Langasek

Bug Description

[SRU Justification]
Up until artful, console-setup declares a versioned dependency on initramfs-tools. This was an Ubuntu-specific dependency only needed for upgrades, and the version referenced is ancient (ca. 2008). In artful and later, the dependency has now been removed.

Since this is no longer relevant for upgrades and we would not otherwise have a dependency on initramfs-tools, we should drop this dependency to support building of images with initramfs-tools removed for systems that we know don't require an initramfs.

[Test case]
1. On a xenial default cloud image install, try to run 'sudo apt purge initramfs-tools'.
2. Verify that this tries to remove console-setup, console-setup-linux, and kbd.
3. Cancel the removal.
4. Install console-setup from xenial-proposed.
5. Run 'sudo apt purge initramfs-tools' again.
6. Verify that console-setup, console-setup-linux, and kbd are not removed.
7. Run 'sudo apt install --reinstall console-setup' and confirm that the package can be installed successfully without initramfs-tools installed.

[Regression Potential]
If a user needs an initramfs in order to mount their root device, and console-setup is the only package on their system which depends on initramfs-tools, it is possible that the user may remove initramfs-tools and render their system unbootable.

This is unlikely because initramfs-tools is still part of the 'minimal' seed and is therefore a dependency of ubuntu-minimal; and it remains a dependency of the generic kernel image.

Steve Langasek (vorlon) on 2017-10-05
Changed in console-setup (Ubuntu):
status: New → Fix Released
Changed in console-setup (Ubuntu Xenial):
status: New → In Progress
assignee: nobody → Steve Langasek (vorlon)

Hello Steve, or anyone else affected,

Accepted console-setup into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/console-setup/1.108ubuntu15.4 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 on 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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 console-setup (Ubuntu Xenial):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-xenial
Steve Langasek (vorlon) wrote :

I've run through this test case and confirmed console-setup works without initramfs-tools.

tags: added: verification-done-xenial
removed: verification-needed verification-needed-xenial
Jeremy Bicha (jbicha) wrote :

Please see LP: #1723806 which suggests that there is a regression here.

Jeremy Bicha (jbicha) wrote :

I'm setting this to verification-failed because we should investigate LP: #1723806 before releasing this to -updates.

tags: added: verification-failed-xenial
removed: verification-done-xenial

On Thu, Oct 19, 2017 at 06:40:19PM -0000, Jeremy Bicha wrote:
> I'm setting this to verification-failed because we should investigate
> LP: #1723806 before releasing this to -updates.

It's fine to hold this in -proposed for right now.

Given that we have a recent spate of reports about maintainer scripts
hanging on 'plymouth --ping' due to plymouthd having hung, and console-setup
calls plymouth --ping in its postinst, I think this is not a bug in
console-setup, and therefore also not a regression. However, since any
upgrade of console-setup is going to tickle the bug for affected users, I
think we need to resolve the plymouth problem first before pushing this SRU
out.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers