[Henrique de Moraes Holschuh] > And what should we do about Debian stretch, then?
I believe a good start would be to add an assert() in a test version of glibc and then run all the autopkgtest scripts on the packages in the archive to see how widespread the problem is. It will not cover all packages, but at least a significant portion of the archive. I suspect we are too close to the Stretch freeze to try to modify all the packages affected by the problem, and if so we should probably disable the more strict code for Stretch too, and make it an RC issue in unstable after the freeze in February. A problem is that it will be hard to test all the packages in time, as such locking issue might not trigger on every run. Is there already, or can you create, a wiki page to collect the details on this problem? You seem to have more grasp of the issue than me, otherwise I would have started one myself. I assume other distributions are affected too. What are they doing to handle it? -- Happy hacking Petter Reinholdtsen
