Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #86434
| From | Bastian Blank <waldi@debian.org> |
|---|---|
| Newsgroups | linux.debian.bugs.dist, linux.debian.kernel |
| Subject | Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap |
| Date | 2025-03-13 07:40 +0100 |
| Message-ID | <KpKox-5IIY-11@gated-at.bofh.it> (permalink) |
| References | (7 earlier) <KcuUh-enFc-1@gated-at.bofh.it> <Jw7ND-HVS-1@gated-at.bofh.it> <KmDMC-3AFS-15@gated-at.bofh.it> <Jw7ND-HVS-1@gated-at.bofh.it> <KmDMC-3AFS-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Cross-posted to 2 groups.
On Tue, Mar 04, 2025 at 12:47:37PM -0400, Stefano Rivera wrote: > Bastian is concerned that if both linux-libc-dev and linux-libc-dev-*-cross > provide linux headers in different paths they should conflict with each > other to avoid compilers accidentally sourcing the wrong headers. > linux-libc-dev installs in the usual multiarch include directory > (/usr/include/$ARCH/linux/). linux-libc-dev-*-cross installs in the sysroot > directory (/usr/$ARCH/include/linux/) > > I would imagine that any conflicts like that would make > linux-libc-dev-*-cross practically uninstallable in any situation where > you'd need them (libc6-dev depends on linux-libc-dev). Yes. An unversioned conflict would make the whole cross stuff effectively uninstallable. > I could see a scenario where linux-libc-dev-*-cross are tiny wrapper > packages, depending on linux-libc-dev and including symlinks from one > include directory to the other. I assume that wouldn't need the Conflicts? This is what I implemented as well, a symlink farm. But those symlinks needs to be belong to the same source package, as the set of required symlinks change over time. Or we are back at: requires conflicts. I only consider symlinks to files acceptable. With symlinks to directories we are back in aliased directories land, with all the same problems as merged-/usr. > Or if the Conflicts were more version-targetted and allow linux-libc-dev and > linux-libc-dev-*-cross to co-install if they were built from the same linux > source version, would that be acceptable? Only if the *-cross maintainer is fine with updating it within a day, every week or so for unstable, but even for stable or security. So, not possible, given that the existing conflict for the same reason against glibc was only solved by NMU after a week or so. Bastian -- Where there's no emotion, there's no motive for violence. -- Spock, "Dagger of the Mind", stardate 2715.1
Back to linux.debian.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-10-10 22:20 +0200
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2024-10-19 15:40 +0200
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-10-19 18:30 +0200
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Ben Hutchings <ben@decadent.org.uk> - 2024-10-24 01:40 +0200
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-11-29 08:00 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2024-12-04 22:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-12-05 13:10 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Ben Hutchings <ben@decadent.org.uk> - 2024-10-24 01:40 +0200
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2024-12-04 23:00 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-12-05 13:10 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2024-12-05 15:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Helmut Grohne <helmut@subdivi.de> - 2024-12-05 22:30 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Stefano Rivera <stefanor@debian.org> - 2025-01-28 00:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2025-02-04 15:10 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap stefanor@debian.org - 2025-02-04 18:30 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2025-02-04 20:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Chris Hofstaedtler <zeha@debian.org> - 2025-02-05 00:00 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Stefano Rivera <stefanor@debian.org> - 2025-03-04 18:00 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2025-03-13 07:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Bastian Blank <waldi@debian.org> - 2025-03-15 11:40 +0100
Bug#1084908: arch:all linux-libc-dev causes problems to architecture bootstrap Stefano Rivera <stefanor@debian.org> - 2024-11-29 14:20 +0100
csiph-web