Ubuntu kernel packages across flavors - current issues and future planing

Registered by Ricardo Salveti

Currently for every kernel flavour we need the following packages:
 - kernel-headers-abi
 - kernel-headers-abi-flavour
 - kernel-image-abi-flavour
 - kernel-image-abi-flavour-dbgsym
 - linux-tools-abi-flavour
 - linux-tools-common

Until we have one single kernel that could support different flavours, we need to support having different packages at our overlay.

Common issues we have with the current solution:
 - DKMS depends on linux-headers/image-generic
 - How to depend on a common and single headers package
 - same dependency issue with the debug package

This session is about discussin possible ways to fix this long standing issues at the Ubuntu LEB, and future planing on how to properly add new flavors in the future.

Blueprint information

Status:
Not started
Approver:
Ricardo Salveti
Priority:
Undefined
Drafter:
None
Direction:
Needs approval
Assignee:
John Rigby
Definition:
Discussion
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

Session Notes:

Ubuntu kernel packages across flavors - current issues and future planing

ABI:
 * 1000 -> linaro
 * 1400 -> LTs (all of them initially)
   * Why we're generating the generic-headers for every LT kernel
   * LT kernel (not maintained by the dev platform) should avoid creating the generic headers by just providing the linux-headers-abi-flavour (but also providing the generic-headers package)

Headers:
 * Make sure the headers related package are also providing linux-headers
 * Request the headers to be installed at the hwpacks

Debug:
 * No easy way to find the correct package at runtime
 * We can provide the debug-generic, but giving the correct instructions to the user would be a better start

Tools:
 * Also request the meta package to provide the proper linux-tools package

CI:
 * ARM: based on 3.1
 * TI: also based on 3.1
 * Freescale: also on 3.1
 * Origen: Should be in 3.1
 * Snowball: Should be 3.1 (Pending resolution of bug #894828)

Actions:
 * Push the additional packaging for other flavors at the lt-packaging-tree
 * Enable the CI build for the other possible flavours
 * Enable other flavours at the meta-package

(?)

Work Items