(→kernel-userspace-headers) |
(→Upstream sources) |
||
Line 7: | Line 7: | ||
== Upstream sources == | == Upstream sources == | ||
− | + | We use the linux-4.x.tar.xz tarballs from http://www.kernel.org/ as well as the appropriate patch-4.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 == | == Patches == |
Revision as of 17:25, 12 October 2016
Please remove this {{Draft}}template, when you're sure the page is complete and correct.
|
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-4.x.tar.xz tarballs from http://www.kernel.org/ as well as the appropriate patch-4.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.
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)
kernel-userspace-headers
One can use this script to generate the tarball after updating its "kver" and "ever" variables at the top, and running it from the kernel source directory (with the top-level Makefile) under the BUILD directory of the built "kernel" .rpm. Note that it puts the stuff directly under the home directory ("~" or "$HOME").
This package does not depend per se on the kernel to build, so it can be submitted at the same time as the kernel, without waiting for the latter to be built and uploaded.
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.