On Thu, Feb 15, 2024 at 10:22:34AM +0100, Christoph Berg wrote: > Re: Steve Langasek > > postgresql-server-dev-16 also shows up as impacted by LFS but the output is > > confusing, mentioning only redefinitions of constants from perl and python > > headers, why should those have disappeared based on defining LFS flags? The > > changes are suspicious enough that I'm not prepared to conclusively declare > > it a false positive.
> postgresql-16 as a whole source package contains a single affected > symbol that is not used by any external user (as per > codesearch.debian.org and github.com). Sorry, did you manage to get sensible a-c-c output? Otherwise, how did you determine that there was a single symbol affected? The only compat_report output I have shows *zero* symbols affected but also shows a bunch of garbage output that makes me not trust it at all. > Please exclude postgresql-16 from the transition. > Where am I supposed to file these requests so they don't get > forgotten? my inbox is fine :) -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer https://www.debian.org/ slanga...@ubuntu.com vor...@debian.org
signature.asc
Description: PGP signature
