[Bug 1898729] Re: shim can end up being removed

[Steve Langasek]

On Wed, Oct 07, 2020 at 10:10:57AM -0000, Julian Andres Klode wrote:
> We could mark bootloader packages as Protected: yes (Important: yes
> before groovy). That would not only prevent autoremoval, it would also
> add another step to manual removal as it triggers the same removal
> prompts as essential packages.

> Arguably top-level kernel packages, oem metapackages should have those
> set too.

I'm not sure it's a good idea to use this for kernel packages since it makes
it more difficult to change kernel flavors.  It would definitely have
knock-on effects on various image build infrastructure.

But setting this for shim-signed and grub-pc sounds like a good idea to
me.

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

Title:
  shim can end up being removed

Status in apt package in Ubuntu:
  New
Status in shim package in Ubuntu:
  New

Bug description:
  I just did a set of package updates in focal that ended up with shim
  shim-signed mokutil being autoremoved.

  I rebooted without noticing, and had to manually recover the system
  thereafter. :(

  Julian says there was a period of time where these were marked auto. I
  suppose that I installed during this window, and now some dependency
  change meant that as far as apt was concerned they weren't required
  any more.

  Can we please consider never proposing these packages for autoremoval?
  apt has NeverAutoRemove for this which could be used, or some other
  appropriate method.

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