Your message dated Thu, 16 Oct 2025 09:20:07 -0400
with message-id <[email protected]>
and subject line notes from the linux-libc-dev-*-cross bof
has caused the Debian Bug report #1065416,
regarding linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it
doesn't do that completely
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 [email protected]
immediately.)
--
1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: linux-libc-dev
Version: 6.7.7-1
Severity: serious
Tags: sid trixie
linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it
doesn't do that completely
Provides: linux-libc-dev-amd64-cross (= 6.7.7-1), ...
However the links in /usr/DEB_HOST_GNU_TYPE/include are missing.
Please stop providing the cross-packages, you don't even need a breaks,
because the current cross packages continue to work.
Once that is done, I'll reduce the cross packages to some symlinks.
--- End Message ---
--- Begin Message ---
The Debian Technical Committee was asked in #1065416 to settle a disagreement
on which package will ship kernel headers for -cross toolchain use -- linux,
or cross-toolchain-base.
During DebConf 25, the Technical Committee hosted a BoF along with folks party
to this topic, and other interested contributors. I'd like to thank everyone
for their participation and contributions to this discussion.
This issue did *not* get a Committee vote -- no resolution was voted on.
Rather, the maintainers involved were able to work to a mutually agreeable
solution.
In the spirit of ensuring we maintain a neutral record of the agreement
reached, the Technical Committee is posting this statement and closing this
bug.
1) The long-term goal of the -cross ecosystem within the project is to do away
with of the old "sysroot style" /usr/{DEB_HOST_GNU_TYPE}/ paths. This is a
long-term goal, and not something that will be done overnight -- but there
was agreement that the status quo is not the desired end-state.
2) There was a decision to not think too hard about documenting the current
state of the *-cross packages on disk in Debian Policy, due to our long-term
goals described in #1 above, so documenting the current (and temporary)
state of how to produce a "sysroot style" /usr/${DEB_HOST_GNU_TYPE}/
*-<arch>-cross package (as implemented by dpkg-cross), does not make sense
at this time.
3) linux-libc-dev-*-cross packages may be provided by a package from src:linux,
so long as it provides "sysroot style" compatable headers on disk via real
files or symlinks, separate from the linux-libc-dev (multiarch-layout)
headers -- however -- separate per-target binary packages would be preferred
by most people in the room. There was agreement to leave the decision
regarding binary package structure, and how to provide that layout to the
src:linux package maintainers.
4) If there are issues in the handover, we consider any resulting issues to be
Release Critical (RC) bugs, given the maintainer(s) involved here today have
agreed to consider it RC -- Linux as the package's maintainer, and
cross-toolchain-base, as the de-facto authority on the -cross namespace and
only consumer. The Release Team (RT) may provide further input here if it
needs to, given this is ultimately a RT decision.
5) The TC will post a statement saying that consensus was reached and the
future long-term path we see. (This is that statement)
On behalf of the Technical Committee,
paultag
signature.asc
Description: PGP signature
--- End Message ---
