9) dpkg -S can return multiple packages in one line, and also over
multiple lines, depending on what matches.
Example for one line with multiple packages:
$ dpkg -S /etc/grub.d
tuned, fwupd, grub-common, memtest86+: /etc/grub.d
And multiple lines:
$ dpkg -S grub.d
grub-common: /etc/grub.d/20_linux_xen
grub-common: /etc/grub.d/10_linux_zfs
memtest86+: /etc/grub.d/20_memtest86+
fwupd: /etc/grub.d/35_fwupd
grub-common: /etc/grub.d/25_bli
grub-common: /etc/grub.d/05_debian_theme
grub-common: /etc/grub.d/README
grub-common: /etc/grub.d/40_custom
grub-common: /etc/grub.d/30_os-prober
grub-common: /etc/grub.d/00_header
grub-common: /etc/grub.d/10_linux
grub-common: /etc/grub.d/41_custom
tuned, fwupd, grub-common, memtest86+: /etc/grub.d
tuned: /etc/grub.d/00_tuned
grub-common: /etc/grub.d/30_uefi-firmware
grub-common: /etc/default/grub.d
Is the symlink target of /etc/default/grub.d/oem-flavour.cfg guaranteed
to be owned by a single package in any ubuntu system?
10) How sure are we that the HWE kernel has the exact same functionality of the
oem kernel? Why not update the OEM kernel to match the nvidia drivers?
11) Shouldn't there be a reboot notification in this update?
12) What is it that makes it a sure bet that removing that oem-flavor
symlink will leave the system with a bootable kernel? Or in other words,
what is guaranteeing that the HWE, or any other kernel, is installed?
13) Why is this being done in ubuntu-drivers-common, and not an oem-specific
package? Perhaps even the one that puts that symlink in place?
ubuntu-drivers-common is seeded all over the place, and many (all?) users will
get this update. Or is it that just nvidia users should have this package
installed? I have it installed on my laptop, which has no nvidia card, btw.
14) Out of curiosity, I installed oem-somerville-lapras-meta
22.04ubuntu9 in a jammy vm. In its oem-somerville-lapras-meta.postinst
we see:
case "$1" in
configure)
mkdir -p /etc/default/grub.d/
ln -sf /usr/share/oem-somerville-lapras-meta/oem-flavour.cfg
/etc/default/grub.d/oem-flavour.cfg
if [ -e /boot/grub/grub.cfg ] && command -v update-grub; then
update-grub
fi
;;
esac
So if oem-somerville-lapras-meta is reinstalled, or upgraded, won't it
just create the symlink again? Wouldn't this be the best place to a)
remove the symlink; b) not create it after some specific version?
15) Where is GRUB_FLAVOUR_ORDER used/defined? (This is more of a
curiosity question, as I haven't encountered this variable before). Is
it used by update-grub?
--
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