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

On Sat, Jul 20, 2024 at 01:01:42PM +0200, Matthias Klose wrote:
> I am re-adding [email protected], and now also [email protected]. I still
> don't see this as an issue that the Technical Committee should decide. This
> is aggressively confrontational behavior of one of the Debian kernel
> maintainers, and it should be handled as that.

So this is a personal, not a technical problem.

> - 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.

No.  Also maybe you want to talk to [email protected], as
his question started all of this.

>  - Bastian's assertion that the current linux-libc-dev package doesn't
>    break anything in the archive, doesn't say anything.  These bits
>    are just not used by anything in the archive.

Ah, now we finally get somewhere.  All of this is about non-Debian.

> As you can see from the commits for the gcc-for-{build,host} changes, these
> were done around the same time as this controversial linux-libc-dev upload.
> So while having to fix one messy set of patches from Helmut, Bastian assumes
> a no-reply on the linux-libc-dev issue as an OK, that's odd.

This was a bug report at a source package you maintain.  Did you not see it?

Bastian