A few thoughts on my end:
Point 1. As an alternative, what about having one single amd64-microcode
package contain multiple versions of the microcode? The blobs are rather
tiny (100KB is the biggest).
Point 3.
- A particular kernel can support a microcode package *or* older. We also
want to allow people to downgrade their microcode package.
- At the moment, aren't just some of the metapackages depending on
amd64-microcode, so the versioned kernel package doesn't actually force the
microcode packages to install? So, for example, you can install
linux-image-virtual without installing any microcode.
- On other hand, from a logical point of view, the amd64-microcode package
depends on a particular kernel package (or newer).
- Could the amd64-microcode package depend on the linux-image virtual package
(seems to be provided by the versioned image packages)?
- Would depending on the virtual package without a concrete alternative
work so that a particular microcode package isn't installable, but without
automatically pulling in a newer kernel version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2130658
Title:
hashed microcode updates
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/amd64-microcode/+bug/2130658/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
