> 8. What happens if reimaging from the OEM image, and then upgrading to the updates pocket all at once, including the update that triggered this bug together with this for it? Which postinst will run first? If not deterministic, and this one runs first, will that cause a problem? Do we need a Breaks clause for ordering purposes? Or is it OK to remove /etc/default/grub.d/oem-flavour.cfg _before_ the bug is triggered?
If OEM metapackage postinst runs first, it will create the symbolic link of /etc/default/grub.d/oem-flavour.cfg. And then ubuntu-drivers-common postinst will remove it. If ubuntu-drivers-common postinst first, there is nothing happening. But OEM metapackage postinst will still create the symbolic link of /etc/default/grub.d/oem-flavour.cfg. However the content in /etc/default/grub.d/oem-flavour.cfg for the later OEM images from right now for jammy should only be 'GRUB_FLAVOUR_ORDER=generic' instead of 'GRUB_FLAVOUR_ORDER=oem'. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2083657 Title: Remove oem-flavour.cfg for the OEM kernel retirement To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2083657/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
