Bug#1059936: Tracked down `behavior of -n is non-portable`
I believe the offending line is in the `klibc` package, after some tracing: https://salsa.debian.org/kernel-team/klibc/-/blob/2078f63fe594652d42e19060b05aa03966fbd8a5/debian/initramfs-tools/hooks/klibc-utils#L31 -- Alex
Bug#685706: libc-bin: order of /etc/ld.so.conf.d/*.conf
Hello all, I have a branch on Salsa [0] that would provide ordering for the two files I currently see placed in /etc/ld.so.conf.d/: * libc.conf * $(uname -m)-linux-gnu.conf I've also done a sweep of the rest of the repo, adding ordering to other files that could appear in /etc/ld.so.conf.d/. Who is the best person to review, and merge? I tried created a merge request to glibc-team/glibc, but did not have proper permissions. Unfortunately, I'm not familiar enough with Lintian to add the associated changes to ensure that files in /etc/ld.so.conf.d/ are numbered. Thanks for taking a look, Alex [0]: https://salsa.debian.org/ahrex-guest/glibc/commits/bug-685706-add-ld.so.conf.d-ordering
Bug#685706: libc-bin: order of /etc/ld.so.conf.d/*.conf
We've hit this issue recently when building software packages for multiple architectures. I believe the general consensus is we should order things, but another point to discuss is the specific ordering Debian should use. IOhannes' example lists libc.conf earlier in the ordering, putting /usr/local/lib before /usr/lib/$(uname -m)-linux-gnu. My colleagues and I agree that this is preferred for us, since this enables the local administrator to effectively overwrite system-defined libraries, if they so choose. Thoughts? Thanks, – Alex
