Currently backports of src:linux in the backports suites include udebs, which may be used in unofficial installer builds. I'm proposing to also do this for a backport in the bookworm(-security) suites. This was previously requested for bullseye (#1117674) and I would llke to do this for bookworm when LTS maintenance starts.
Since the backports suites are not supported for a full 5 years, I add a
backported kernel to the -security suite at the start of LTS
maintenance. Until now, I have conservatively disabled building udebs
in these backports.
For bookworm specifically, this will require either updating kernel-
wedge or disabling compressed kernel modules, because bookworm's version
does not support them. I verified that updating kernel-wedge from 2.104
to 2.106 did not change (1) the debian/control file generated for
src:linux (2) the contents of the udebs produced after a
build/sign/build of src:linux. (The udebs were not bit-identical due to
modules being signed with an ephemeral key, but otherwise the packages
were the same.) So I think this is quite safe to do.
I have *not* tested whether having these additional udebs available will
affect the inclusion of packages in official installer builds for the
final point release. To test this, would it be sufficient to put them
in localudebs/, or should I put them in a local APT archive and add a
sources.list.udeb.local pointing at them?
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption]
would be development of an easy way to factor large prime numbers.
- Bill Gates
signature.asc
Description: This is a digitally signed message part
