Your message dated Thu, 5 Dec 2024 09:09:33 +0100
with message-id <20241205080933.47nls5kfkngsf...@shell.thinkmo.de>
and subject line Re: Bug#1081826: linux-libc-dev ships header files not needed 
for 99% of it's users
has caused the Debian Bug report #1081826,
regarding linux-libc-dev ships header files not needed for 99% of it's users
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1081826: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081826
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-libc-dev
Version: 6.10.9-1
Severity: important
Tags: sid trixie

linux-libc-dev started shipping header files not needed for 99% of it's users. The default usage of linux-libc-dev is the availability of the user facing header files for native builds. These make up likely 99% or more of the use cases. There is no need to add extra stuff like the header files for any other architecture. These should be split out into separate packages.

Please optimize for our users, not the space of a package on a ftp mirror, or for cross build users (which also don't need these header files all at a time).
--- End Message ---
--- Begin Message ---
On Sun, Sep 15, 2024 at 10:53:45AM +0200, Matthias Klose wrote:
> linux-libc-dev started shipping header files not needed for 99% of it's
> users.

No, those files are needed by users.

If you think differently, then please provide a list of files you think
are not needed and why.

Bastian

-- 
There's a way out of any cage.
                -- Captain Christopher Pike, "The Menagerie" ("The Cage"),
                   stardate unknown.

--- End Message ---

Reply via email to