Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
On Wed, Mar 20, 2024 at 09:59:31PM +0100, Matthias Klose wrote: > Independent of any technical issues, this is a hijacking of a package name. > Please revert that change. Okay. Please prepare to take over linux-libc-dev alltogether then, there can be only one copy. Bastian -- Insufficient facts always invite danger. -- Spock, "Space Seed", stardate 3141.9
Bug#1067429: nmu: iproute2_6.8.0-1
Package: release.debian.org Severity: normal X-Debbugs-Cc: iprou...@packages.debian.org Control: affects -1 + src:iproute2 User: release.debian@packages.debian.org Usertags: binnmu nmu iproute2_6.8.0-1 . armel armhf . unstable . -m "Rebuild with libelf1t64" See https://packages.debian.org/unstable/iproute2
Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
On 21.03.24 07:58, Bastian Blank wrote: On Wed, Mar 20, 2024 at 09:59:31PM +0100, Matthias Klose wrote: Independent of any technical issues, this is a hijacking of a package name. Please revert that change. Okay. Please prepare to take over linux-libc-dev alltogether then, there can be only one copy. please drop the provides: linux-libc-dev-alpha-cross (= 6.7.9-2), linux-libc-dev-amd64-cross (= 6.7.9-2), linux-libc-dev-arm64-cross (= 6.7.9-2), linux-libc-dev-armel-cross (= 6.7.9-2), linux-libc-dev-armhf-cross (= 6.7.9-2), linux-libc-dev-hppa-cross (= 6.7.9-2), linux-libc-dev-i386-cross (= 6.7.9-2), linux-libc-dev-loong64-cross (= 6.7.9-2), linux-libc-dev-m68k-cross (= 6.7.9-2), linux-libc-dev-mips-cross (= 6.7.9-2), linux-libc-dev-mips64-cross (= 6.7.9-2), linux-libc-dev-mips64el-cross (= 6.7.9-2), linux-libc-dev-mips64r6el-cross (= 6.7.9-2), linux-libc-dev-mipsel-cross (= 6.7.9-2), linux-libc-dev-powerpc-cross (= 6.7.9-2), linux-libc-dev-ppc64-cross (= 6.7.9-2), linux-libc-dev-ppc64el-cross (= 6.7.9-2), linux-libc-dev-riscv64-cross (= 6.7.9-2), linux-libc-dev-s390x-cross (= 6.7.9-2), linux-libc-dev-sh4-cross (= 6.7.9-2), linux-libc-dev-sparc64-cross (= 6.7.9-2), linux-libc-dev-x32-cross (= 6.7.9-2)
Processed: Re: Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
Processing control commands: > reassign -1 tech-ctte Bug #1065416 [linux-libc-dev] linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely Bug reassigned from package 'linux-libc-dev' to 'tech-ctte'. No longer marked as found in versions linux/6.7.7-1. Ignoring request to alter fixed versions of bug #1065416 to the same values previously set > severity -1 normal Bug #1065416 [tech-ctte] linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely Severity set to 'normal' from 'serious' -- 1065416: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1065416 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1065416: linux-libc-dev claims to provide linux-libc-dev-ARCH-cross, but it doesn't do that completely
Control: reassign -1 tech-ctte Control: severity -1 normal Hi I don't see any way to solve this issue right now. Please decide this matter according to 6.1 nr 2 Debian Constitution. Background: linux-libc-dev provides the Linux API for consumption by all userspace stuff. This package was arch-any for as long as I remember and provided only the headers for this single architecture. Since a short while this package is now arch-all and provides headers for all known Debian architectures in one swoop. This change was done when the Ubuntu maintainers asked if we wanted to follow. This now means that new architectures will need to get added to linux-libc-dev first and it is not longer required to push hand crafted packages somewhere in the ports archive. However the package now contains everything that is also contained in the uncoordinated linux-libc-dev-*-cross packages. The only difference is the physical location of the files (/usr/include instead of the policy violating /usr/*/include). This API proofed to be compatible with all tested packages available in the archive. Because of this (from my side unnecessary) code duplication, I opened the plan to replace linux-libc-dev-*-cross, see #1059786. Two months later the following bug report comes in: On Mon, Mar 04, 2024 at 08:53:11AM +0100, Matthias Klose wrote: > 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. Even after several e-mails, the OP was unable or unwilling to show where the problem actually lies. Please decide who is going to provide linux-libc-dev and all the associated cross stuff and how it should look like. Regards, Bastian -- Vulcans never bluff. -- Spock, "The Doomsday Machine", stardate 4202.1
