Package: src:glibc
Version: 2.41-4
Severity: serious
Tags: sid trixie
Affects: gcc-14-cross

sudo apt build-dep gcc-14-cross

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
builddeps:gcc-14-cross : Depends: libc6-dev-amd64-cross (>= 2.37) but
it is not installable
libc6-dev-i386-amd64-cross : Depends: libc6-dev-amd64-cross (=
2.40-4cross1) but it is not installable
libc6-dev-x32-amd64-cross : Depends: libc6-dev-amd64-cross (=
2.40-4cross1) but it is not installable
Error: Unable to correct problems, you have held broken packages.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

reassign -1 libc6-dev-i386

Bug #1100544 [src:glibc] glibc adds some conflicts letting gcc-14-cross ftbfs Bug reassigned from package 'src:glibc' to 'libc6-dev-i386'.
No longer marked as found in versions glibc/2.41-4.
Ignoring request to alter fixed versions of bug #1100544 to the same values previously set

affects -1 = src:gcc-14-cross

Bug #1100544 [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs
Added indication that 1100544 affects src:gcc-14-cross

tags -1 + ftbfs

Bug #1100544 [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs
Added tag(s) ftbfs.

--
1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-03-15 07:01, Helmut Grohne wrote:

Control: reassign -1 libc6-dev-i386
Control: affects -1 = src:gcc-14-cross
Control: tags -1 + ftbfs

On Sat, Mar 15, 2025 at 05:45:15AM +0100, Matthias Klose wrote:

sudo apt build-dep gcc-14-cross

Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
builddeps:gcc-14-cross : Depends: libc6-dev-amd64-cross (>= 2.37) but it is
not installable
libc6-dev-i386-amd64-cross : Depends: libc6-dev-amd64-cross (= 2.40-4cross1) but it is not installable
libc6-dev-x32-amd64-cross : Depends: libc6-dev-amd64-cross (= 2.40-4cross1)
but it is not installable
Error: Unable to correct problems, you have held broken packages.

Matthias and me discussed the matter on irc. The bug introducing the
problem was #1092278 asking for libc6-dev-* to conflict with one
another. Now the transformed libc6-dev-*-*-cross packages move e.g. /usr/lib32 to /usr/<triplet>/lib32 thereby resolving the underyling
conflict in the transformed packages. Moreover, since the conflicts lack architecture qualifiers we get funky ones such as
libc6-dev-amd64-amd64-cross that don't exist anywhere. Qualifying them
is not a solution, because gcc-14-cross really wants both libc6-dev-x32-i386-cross and libc6-dev-x32-amd64-cross at the same time
and while their package contents are coinstallable, the underlying glibc packages libc6-dev-x32:i386 and libc6-dev-x32:amd64 really are not coinstallable. It is the sysroot transformation that renders them coinstallable.

Our discussion arrived at three ways to move forward from here and we
did not reach any agreement here.

1. glibc should conditionally emit these Conflicts. When a particular
environment variable is set by c-t-b, their emission is suppressed.

2. Someone (me?) develops a c-t-b patch that discards the conflicts in
the repacking step as that also is the step that fixes
coinstallability.

3. We revert those conflicts in trixie and retry with more time in
forky.

Matthias prefers 1. I object to 1 on reproducibility grounds and
favour 3 given the state of discussion.

cross-toolchain-base has been an increasing burden in packaging glibc,
imposing too many development constraints and limiting changes that can
be made. Therefore my plan is to stop shipping the debian/ directory in
the glibc-source package starting with forky. cross-toolchain-base we'll
have to build the glibc from sources in its own way.

The toolchain being already frozen (since today), any change needs a pre-approval, so I would rather go with option 1 to make the approval
easier.

Regards
Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On 2025-03-15 11:08, Matthias Klose wrote:

On 15.03.25 10:55, Aurelien Jarno wrote:

On 2025-03-15 07:01, Helmut Grohne wrote:

Control: reassign -1 libc6-dev-i386
Control: affects -1 = src:gcc-14-cross
Control: tags -1 + ftbfs

On Sat, Mar 15, 2025 at 05:45:15AM +0100, Matthias Klose wrote:

sudo apt build-dep gcc-14-cross

Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

Unsatisfied dependencies:
builddeps:gcc-14-cross : Depends: libc6-dev-amd64-cross (>= 2.37) but it is
not installable
libc6-dev-i386-amd64-cross : Depends: libc6-dev-amd64-cross (= 2.40-4cross1) but it is not installable
libc6-dev-x32-amd64-cross : Depends: libc6-dev-amd64-cross (= 2.40-4cross1)
but it is not installable
Error: Unable to correct problems, you have held broken packages.

Matthias and me discussed the matter on irc. The bug introducing the problem was #1092278 asking for libc6-dev-* to conflict with one
another. Now the transformed libc6-dev-*-*-cross packages move e.g. /usr/lib32 to /usr/<triplet>/lib32 thereby resolving the underyling conflict in the transformed packages. Moreover, since the conflicts lack architecture qualifiers we get funky ones such as libc6-dev-amd64-amd64-cross that don't exist anywhere. Qualifying them
is not a solution, because gcc-14-cross really wants both libc6-dev-x32-i386-cross and libc6-dev-x32-amd64-cross at the same time and while their package contents are coinstallable, the underlying glibc packages libc6-dev-x32:i386 and libc6-dev-x32:amd64 really are not coinstallable. It is the sysroot transformation that renders them coinstallable.

Our discussion arrived at three ways to move forward from here and we
did not reach any agreement here.

1. glibc should conditionally emit these Conflicts. When a particular
environment variable is set by c-t-b, their emission is suppressed.

2. Someone (me?) develops a c-t-b patch that discards the conflicts in
the repacking step as that also is the step that fixes
coinstallability.

3. We revert those conflicts in trixie and retry with more time in
forky.

Matthias prefers 1. I object to 1 on reproducibility grounds and
favour 3 given the state of discussion.

cross-toolchain-base has been an increasing burden in packaging glibc, imposing too many development constraints and limiting changes that can
be made. Therefore my plan is to stop shipping the debian/ directory in
the glibc-source package starting with forky. cross-toolchain-base we'll have to build the glibc from sources in its own way.

The toolchain being already frozen (since today), any change needs a pre-approval, so I would rather go with option 1 to make the approval easier.

so instead of fixing the issue, threatening to remove the cross compilers from the distro. Great! Users are our priority!

I am not threatening to remove them. I am telling that we will have to
find alternative way to build the cross toolchain-base packages. The
current approach of just cross-building the glibc and later converting
the resulting packages just imposes a lot of constraints. Even minor
change to the glibc packaging can lead to breakages (and complaints), so
I am avoiding too many changes, even if it shows not enough. This in
turns removed me the courage to look at bigger packaging changes like locales-all or gconv libraries splitting.

This is now the another time that patches from Helmut for out-of-the-archive cross builds are breaking the in-archive cross compilers.

You are completely mixing things. This has nothing to do with out-of-the-archive cross build. Those are conflicts that users can
encounter when installing libc-dev biarch packages on a multiarch
system. And as you say it well: Users are our priority!

Regards
Aurelien

--
Aurelien Jarno GPG: 4096R/1DDD8C9B aurelien@aurel32.net http://aurel32.net

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

This is a multi-part message in MIME format...

Your message dated Sat, 15 Mar 2025 14:26:22 +0100
with message-id <Z9V__g1XHZOjhWYW@aurel32.net>
and subject line Re: Bug#1100544: glibc adds some conflicts letting gcc-14-cross ftbfs
has caused the Debian Bug report #1100544,
regarding glibc adds some conflicts letting gcc-14-cross ftbfs
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 owner@bugs.debian.org
immediately.)


--
1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

Received: (at submit) by bugs.debian.org; 15 Mar 2025 04:45:26 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.6-bugs.debian.org_2005_01_02
(2021-04-09) on buxtehude.debian.org
X-Spam-Level:
X-Spam-Status: No, score=-15.6 required=4.0 tests=BAYES_00,
BODY_INCLUDES_PACKAGE,FORGED_SPF_HELO,FROMDEVELOPER,HAS_PACKAGE,
KHOP_HELO_FCRDNS,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,
SPF_NONE autolearn=ham autolearn_force=no
version=3.4.6-bugs.debian.org_2005_01_02
X-Spam-Bayes: score:0.0000 Tokens: new, 14; hammy, 120; neutral, 35; spammy,
0. spammytokens: hammytokens:0.000-+--trixie, 0.000-+--H*F:U*doko,
0.000-+--builddep, 0.000-+--H*RU:sk:einhorn, 0.000-+--H*r:sk:einhorn Return-path: <doko@debian.org>
Received: from einhorn.in-berlin.de ([192.109.42.8]:56813 helo=einhorn-mail-out.in-berlin.de)
by buxtehude.debian.org with esmtps (TLS1.3:ECDHE_

Processing control commands:

reopen -1

Bug #1100544 {Done: Aurelien Jarno <aurel32@debian.org>} [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs
Bug reopened
Ignoring request to alter fixed versions of bug #1100544 to the same values previously set

--
1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

reassign -1 cross-toolchain-base-mipsen

Bug #1100544 [libc6-dev-i386] glibc adds some conflicts letting gcc-14-cross ftbfs
Bug reassigned from package 'libc6-dev-i386' to 'cross-toolchain-base-mipsen'. Ignoring request to alter found versions of bug #1100544 to the same values previously set
Ignoring request to alter fixed versions of bug #1100544 to the same values previously set

--
1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Processing control commands:

tag -1 + patch

Bug #1100544 [cross-toolchain-base-mipsen] glibc adds some conflicts letting gcc-14-cross ftbfs
Added tag(s) patch.

--
1100544: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1100544
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)