On Fri, Feb 16, 2024 at 02:19:04PM +0100, Christoph Berg wrote:
> Re: Steve Langasek
> > 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.

> That was in a different sub-thread on this bug:

>   For postgresql-16 (where libpq-dev comes from), the only symbol
>   affected seems to be pqWaitTimed as indicated above.

>   The good news is that the function is only used internally in libpq,
>   and by no external user:

>   https://codesearch.debian.net/search?q=pqWaitTimed&literal=1
>   https://github.com/search?q=pqWaitTimed&type=code

>   (GitHub finds a bunch of instances, but these are all either
>   PostgreSQL itself, or vendored copies of libpq.)

Got it, thanks.  I've added it now to our "manual" override list and we will
not NMU. 
https://salsa.debian.org/vorlon/armhf-time_t/-/commit/3e2127d44325b60b4f3b3905f0c841899898f3fb

>   So I think we can safely ignore the difference and not rename libpq5.
>   (It has been named like that for 20 years and I really don't want to
>   break compatibility there.)

I have a different perspective, I find the idea of getting rid of the 'g'
decorator on libpam0 after 25+ years to be quite exciting and am looking
forward to it :-)

-- 
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

Attachment: signature.asc
Description: PGP signature

Reply via email to