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

[Iain Lane]

Cheers Steve. Nope, -proposed is not enabled.

Yes, it happened - it was the result of an explicit autoremove on my
part though after I had dist-upgraded to current focal-updates. I should
have noticed that this was happening and stopped it, granted. :)

Attached is the snippet of apt's term.log corresponding to the
autoremove run. It crapped out at the end as usual because I have a tiny
/boot; not included but mentioning because it might mean the log is
truncated a bit.

Now, this system has been through several Ubuntu development cycles.
It's likely to be unclean. So I don't mind if the priority is low but
making use of this feature of apt feels sensible to me, although
admittedly there's a question about where we would stop if we started to
do it.

** Attachment added: "shim"
   https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1898729/+attachment/5418422/+files/shim

-- 
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