Sorry this has taken so long - I've been swamped IRL :-( On Mon, Nov 04, 2024 at 04:25:03AM -0600, Daniel Lewart wrote: >On Tue, 08 Oct 2024 02:00:00 -0500, I wrote: > >> linux-image is version 6.10.11-1, but there are multiple versions >> of module udebs in the pool. E.g.: >> * btrfs-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb >> * btrfs-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb >> * btrfs-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb >> * btrfs-modules-6.11.2-amd64-di_6.11.2-1_amd64.udeb >> * crc-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb >> * crc-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb >> * crc-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb >> * crypto-dm-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb >> * crypto-dm-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb >> * crypto-dm-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb >> * crypto-dm-modules-6.11.2-amd64-di_6.11.2-1_amd64.udeb >> >> Is there any reason to have non-6.10.11-1 versions of the module udebs? > >Now linux-image is version 6.11.5-1, and the bloat keeps increasing: > * btrfs-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb > * btrfs-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb > * btrfs-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb > * btrfs-modules-6.11.2-amd64-di_6.11.2-1_amd64.udeb > * btrfs-modules-6.11.4-amd64-di_6.11.4-1_amd64.udeb > * btrfs-modules-6.11.5-amd64-di_6.11.5-1_amd64.udeb > * crc-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb > * crc-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb > * crc-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb > * crypto-dm-modules-6.10.9-amd64-di_6.10.9-1_amd64.udeb > * crypto-dm-modules-6.10.11-amd64-di_6.10.11-1_amd64.udeb > * crypto-dm-modules-6.10.12-amd64-di_6.10.12-1_amd64.udeb > * crypto-dm-modules-6.11.2-amd64-di_6.11.2-1_amd64.udeb > * crypto-dm-modules-6.11.4-amd64-di_6.11.4-1_amd64.udeb > * crypto-dm-modules-6.11.5-amd64-di_6.11.5-1_amd64.udeb >...
I think there's a problem here in (the archive|the kernel packaging), as far as I can see. Look at https://packages.debian.org/source/unstable/linux-signed-amd64 and you'll see that right now the linux-signed-amd64 (6.12.3+1) source package claims to build modules for all of the following kernel ABIs. Picking crypto-dm-modules-* as an example: * crypto-modules-6.10.9-amd64-di * crypto-modules-6.10.9-amd64-di * crypto-modules-6.10.11-amd64-di * crypto-modules-6.10.11-amd64-di * crypto-modules-6.10.12-amd64-di * crypto-modules-6.10.12-amd64-di * crypto-modules-6.11.2-amd64-di * crypto-modules-6.11.2-amd64-di * crypto-modules-6.11.4-amd64-di * crypto-modules-6.11.4-amd64-di * crypto-modules-6.11.5-amd64-di * crypto-modules-6.11.5-amd64-di * crypto-modules-6.11.6-amd64-di * crypto-modules-6.11.6-amd64-di * crypto-modules-6.11.7-amd64-di * crypto-modules-6.11.7-amd64-di * crypto-modules-6.11.9-amd64-di * crypto-modules-6.11.9-amd64-di * crypto-modules-6.11.10-amd64-di * crypto-modules-6.11.10-amd64-di * crypto-modules-6.12.3-amd64-di * crypto-modules-6.12.3-amd64-di debian-cd just pulls in all the modules in a release, expecting that to be a sensible set. WTH is happening here? -- Steve McIntyre, Cambridge, UK. st...@einval.com "The problem with defending the purity of the English language is that English is about as pure as a cribhouse whore. We don't just borrow words; on occasion, English has pursued other languages down alleyways to beat them unconscious and rifle their pockets for new vocabulary." -- James D. Nicoll