This article describes the workflow to update the Linux kernel in Cauldron or a stable release. It is meant for use by the kernel maintainer group, but might also be relevant for whoever wants to build their own kernel RPMs.
Contents
Updating the kernel SRPM
Upstream sources
We use the linux-5.x.tar.xz tarballs from http://www.kernel.org/ as well as the appropriate patch-5.x.y.xz patch to the stable series. One can download them by editing the "SPECS/kernel.spec" file and running "mgarepo sync -d".
Patches
See the file PATCHES/Documentation/managing-patches.txt in our kernel SVN source tree.
See also Kernel patches policy.
Third Party patches
We added some modules directly in our kernel ( mainly for network devices ). This is in the 3rdparty folder of our kernel.
Here is the list of those projects:
- ndiswrapper: https://github.com/pgiri/ndiswrapper[1]
- rtl8812au: https://github.com/aircrack-ng/rtl8812au.git[2]
- rtl8723de: https://github.com/smlinux/rtl8723de[3]
- viahss
- rtl8821ce: https://github.com/tomaspinho/rtl8821ce[4]
- aufs: https://github.com/sfjro/aufs5-linux[5]
Rebuilding kernel-dependent packages
There are various packages which must be kept in sync with the current kernel EVR. Those are:
- kernel-userspace-headers
- kmod-virtualbox
- kmod-vboxadditions
- kmod-xtables-addons
- drakx-installer-images (both Core and Nonfree)
kmods and drakx-installer-images
Those packages all requires the kernel devel packages to build, so should be submitted once the kernel was successfully built and uploaded.
For the three kmod packages, the kernel version and release macros must be updated, and the main release bumped.
The four packages have no cross-dependencies and can thus be submitted concurrently. drakx-installer-images needs to be rebuilt on Core first, and then Nonfree.
