On Tue, Feb 04, 2020 at 01:14:10PM +0000, Steve McIntyre wrote: > So, we're all fine? Not so much: for our 32-bit Debian arches, we will > need to basically rebuild the world to be 2038-safe. When we had to do > something like this in the past, to deal with the libc5->libc6 > transition, we had an SONAME change in libc to work with. We decided > to append the "g" tag to the names of our library binary packages to > signal that a library was built against libc6. We can still see some > of the effects of this in the archive, many years later > (e.g. zlib1g). The problem now is that we will *not* have an soname > change here to help identify code compatibility on the 32-bit front.
Why not? This seems like the type of problem that SONAMEs are made for. What am I missing? -- To the thief who stole my anti-depressants: I hope you're happy -- seen somewhere on the Internet on a photo of a billboard
