On 3/19/20 4:54 PM, Gregor Riepl wrote: >>>>> [1] >>>>> https://salsa.debian.org/glibc-team/glibc/-/blob/sid/debian/debhelper.in/libc.postinst >>> >>> Could you check if b33e946fbb1659d2c5937c4dd756a7c49a132dff changes >>> anything? > > Where can I find that commit?
In the glibc git, I assume. >> Yes, sure. That will take 2-3 hours though. > > Does that mean you've been able to reproduce the problem or should I > monkey-patch my system to test the patch? Well, I already answered you that this bug exists in glibc 2.30 but not 2.31 which is why I uploaded glibc 2.31 to unreleased for sparc64. I have not verified yet whether this commit fixes the problem, but I assume it's a commit that is part of the working 2.31 and not in 2.30 branch. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - [email protected] `. `' Freie Universitaet Berlin - [email protected] `- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
