Bug#1065416: requesting input on recent posts to #1065416

Hi Matthias (2024.07.20_13:01:42_+0200)
> I still don't see this as an issue that the Technical Committee should
> decide.

The Technical Committee is hoping that this will be resolved without
requiring us to make a decision. If the take-over offer resolves the
issue, then we will probably vote to take no further action.

> - I am accepting the offer given in
>   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416#108
>   to take over the linux-libc-dev package.
>   I will start working on that at DebCamp and DebConf.

Can you tell us a little more about how you plan to maintain
linux-libc-dev?

Specifically:

Will it be another binary package in cross-toolchain-base, built from
linux-source-*?

Will cross-toolchain-base now contain linux-libc-dev-*-cross and
linux-libc-dev, as separate Arch: all, Multi-Arch: foreign binary
packages?

I don't know much about the stability of these headers, but I see
regular changes. I assume moving linux-libc-dev from the linux source
to cross-toolchain-base will mean that you'll have to do more frequent
uploads of cross-toolchain-base to keep them up to date, where this was
less critical for cross-compiler toolchains.

What are the consequences of not staying up to date? I'm guessing
incoming bug reports from other packages wanting to use new features.

Stefano