Refresh patches for upstream changes
d/config: Update with the help of kconfigeditor2
Add CVE id references
Add Debian bug closer for #1119232
Add Debian bug closer for #1120602
Add Debian bug closer for #1106411
Add Debian bug closer for #1114557
Add Debian bug closer for #1120680
Cleanup debian/changelog file
Currently orig tarball caching is broken in CI. The fix for this on
debian/latest doesn't cleanly apply here, in part because:
- Here we use genorig.py, which puts tarballs in ../orig and
creates symlinks to them in ..
- There we use uscan, which puts tarballs in ..
To reduce the conflicts, change genorig.py to create tarballs in ..
and change debian/rules and debian/salsa-ci.yml to work with that.
(cherry picked from commit d16220d004)
This backports merge request kernel-team/linux!1646
Commits:
- NFSv4: Clear the NFS_CAP_XATTR flag if not supported by the server
- NFSv4: Clear the NFS_CAP_FS_LOCATIONS flag if it is not set
- NFSv4: Don't clear capabilities that won't be reset
The change for "NFSv4: Clear NFS_CAP_OPEN_XOR and NFS_CAP_DELEGTIME if
not supported" is dropped as it does not apply to the 6.1.y series.
The bug closer for #1114898 as te regression did not hit Debian bookworm
but the change needs to be included to not introduce the regression from
6.1.149 upstream.
Now that the Salsa common pipeline builds packages under sbuild, the
variable DEBIAN_KERNEL_DISABLE_INSTALLER=true in the pipeline's
environment is filtered out of the package build environment and
gencontrol_signed.py doesn't see it (but gencontrol.py does).
This problem doesn't occur in later branches because the functionality
of gencontrol_signed.py was moved into gencontrol.py.
To fix this, change gencontrol.py to set the appropriate config field
when $DEBIAN_KERNEL_DISABLE_INSTALLER is set. This change will be
saved in config.defines.dump and seen by gencontrol_signed.py later,
but the source config files will be unchanged.
This backports merge request kernel-team/linux!1548
Commits:
- d/salsa-ci.yml: Suppress unreleased changes and mismatching
distribution lintian tags
- d/salsa-ci.yml: Merge the extract-source job into the build's job
script
Adjusted for context changes in version from debian/6.1/bookworm.
When the kernel is in FIPS mode, ECDSA is not supported and modules
signed with ECDSA will fail to load (even if Lockdown is not active).
This was fixed in later kernel versions, but it seems safer to revert
to using RSA signatures than to backport those changes.
Closes: #1114773
Apply patch for a regression in 6.16.1. This has not yet been applied
upstream but has been tested and looks OK to me.
(cherry picked from commit 8765ecb339)
[Salvatore Bonaccorso: Do not explicitly mention regression from 6.16.1]
(cherry picked from commit 62a4ef2d64)
Backport just enough of commit 2fb2d2b8e1 "Merge main image build
and install into one target" to be able to apply commit ca3d0e60f5
"Store build time signing key encrypted".
pycodestyle reports:
debian/bin/gencontrol.py:615:29: E241 multiple spaces after ','
debian/bin/gencontrol.py:616:29: E241 multiple spaces after ','
debian/bin/gencontrol.py:617:27: E241 multiple spaces after ','
debian/bin/gencontrol.py:618:28: E241 multiple spaces after ','
Using multiple spaces to align columns is perfectly valid, and flake8
(as we use in more recent branches) doesn't complain about this. So
add this to the ignore list.
