On 15.03.25 14:02, Aurelien Jarno wrote:
On 2025-03-15 12:03, Matthias Klose wrote:
What I'm really missing here is any commitment testing such changes as
adding the conflicts. Things can break, and I unfortunately also got a lot
of untested patches even breaking GCC native builds. And for that particular
change, I don't think this is appropriate six weeks before a freeze.
Retrospectively it's always easy to say this is not appropriate. But
it's always difficult to spot which changesat needs to be tested. And
no, testing the cross-toolchain-base + gcc-X-cross for each upload is
way too heavy and not something you can ask.
This is exactly thing I am asking Helmut about. Then ok, I'll handle
that more strict. My first priority are the native packages, then the
cross packages in the archive. In the past I've seen unfortunately
patches which break either of these, and where claims were made, that
these were tested, which in the end, were not tested.
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!
How many users are affected by this? If users are confused by multilib
packages, then let's remove them in trixie. No need to have them anymore in
forky, I assume. People can use the cross compilers instead.
I am all for removing the biarch packages, especially the ones built by
c-t-b, I never understood their use case, and that will have prevented
this bug to happen. But each time I talked about disabling multilib in
gcc, you told me you don't want to diverge from upstream. Has your
position changed since then?
yes, once you have a solution to depend on foreign architectures, for
both release and ports architectures. Are you willing to work on this?
No, I'm not fine to drop support before there is a replacement.
Matthias
