In certain circumstances (e.g. rpm-ostree compose, upgrades) rpm-ostree attempts to detect if the kernel has changed. This happens in rpmostree_context_assemble by way of rpmte_is_kernel which uses a hard-coded set of "Provides" entries to test if a package is sufficiently kernel:
For an internal use-case we're using Oracle Linux's UEK kernel which is installed via the kernel-uek or kernel-uek-core package and has the relevant "Provides" entries of kernel-uek and kernel-uek-core but lacks any of the entries in the list built in to rpmte_is_kernel. This results in upgrades not creating new boot entries.
Would it be possible to either add kernel-uek and/or kernel-uek-core to this list, or to make the list configurable in some way?
In certain circumstances (e.g.
rpm-ostree compose
, upgrades)rpm-ostree
attempts to detect if the kernel has changed. This happens inrpmostree_context_assemble
by way ofrpmte_is_kernel
which uses a hard-coded set of "Provides" entries to test if a package is sufficiently kernel:https://github.com/coreos/rpm-ostree/blob/366cb8739cbed0f432068518bf63958d5b713273/src/libpriv/rpmostree-core.cxx#L3821-L3836
For an internal use-case we're using Oracle Linux's UEK kernel which is installed via the
kernel-uek
orkernel-uek-core
package and has the relevant "Provides" entries ofkernel-uek
andkernel-uek-core
but lacks any of the entries in the list built in torpmte_is_kernel
. This results in upgrades not creating new boot entries.Would it be possible to either add
kernel-uek
and/orkernel-uek-core
to this list, or to make the list configurable in some way?