DB410c: DB820c: mark Linux kernel package as held

By default, hold the kernel debian package. To work properly, the kernel Image
and the kernel modules must be in sync. On Dragonboards, the kernel Image is
stored in the boot partition as an Android boot image, while the kernel modules
reside in the rootfs in /lib/modules.

When the kernel package is upgraded, new modules are installed in the rootfs,
however the kernel Image in the boot partition is not updating, which can lead
to kernel/module mismatch.

Until we implement a better option, we hold the kernel package so that it is not
ugpraded. We will provide instruction to un-hold the package for power users
that understand the risks they are taking.

Change-Id: Ic18e753ea33e1183d3655ed00d2fe7d5a9370c65
Signed-off-by: Nicolas Dechesne <nicolas.dechesne@linaro.org>
2 files changed
tree: bb4f18990950c0f4e288d12b5c471eb893699997
  1. class/
  2. debconf/
  3. disk_config/
  4. files/
  5. hooks/
  6. package_config/
  7. scripts/
  8. tests/
  9. tools/
  10. .gitreview
  11. README.md
README.md

Usage example on arm64 host:

sudo modprobe loop docker run --privileged -v $(pwd):/work --rm -it linaro/arm64-fai /bin/bash cd /work git clone http://git.linaro.org/ci/fai.git fai-diskimage -v --cspace $(pwd)/fai --hostname linaro-test -S 3G --class BUSTER,DEBIAN,DEVELOPER,LINARO,QCOM,DB410C,RAW linaro.raw 2>&1|tee fai.log

Gotchas:

  • loop devices need to exist before starting docker
  • order of classes matter - latter classes override variables from earlier ones
  • missing packages in packages from package_lists and errors while installing packages will not error the build out
    • grep the log for warnings and erros before proceeding