Re: RFC: use of shlib bump for libc dependency on new multiarch directories?

On Wed, 23 Feb 2011 at 13:52:35 -0800, Steve Langasek wrote: we almost certainly will not be using the path which has been enabled in glibc up to now, namely /lib/i486-linux-gnu. I'd heard that, and was somewhat concerned about whether that'd block multiarch for yet another release cycle; I'm

Bug#915621: glibc-source: needs versioned Breaks on some binary from cross-toolchain-base (<< 29~)

Package: glibc-source Version: 2.28-1 Severity: important autopkgtest fails while trying to test whether glibc in unstable could migrate to testing: https://ci.debian.net/data/autopkgtest/testing/amd64/c/cross-toolchain-base/1438735/log.gz > tar -x -f /usr/src/glibc/glibc-2.28.tar.xz > cp -a

Bug#877900: How to get 24-hour time on en_US.UTF-8 locale now?

On Thu, 07 Feb 2019 at 14:05:33 +0100, Adam Borowski wrote: > a locale for a silly country with weird customs Please don't take this tone. Insulting people who disagree with you[1] is rarely an effective way to persuade them that you're right and they're wrong. > • promoting C.UTF-8 in our user

Re: Options for 64-bit time_t support on 32-bit architectures

On Fri, 19 Jul 2019 at 15:13:00 +0300, Adrian Bunk wrote: > Remaining usecases of i386 will be old binaries, some old Linux binaries > but especially old software (including many games) running in Wine. > Old Linux binaries will still need the old 32bit time_t. Based on background from my