Re: Releasing groff 1.22.5?

[Bertrand Garrigues]

Hi Ingo,

On Thu, Oct 15 2020 at 05:32:32 PM, Ingo Schwarze <schwarze@usta.de> wrote:
> Meanwhile, i heard rumours that the upcoming change in libc that will
> cause %n in writeable memory to abort the program will cause some
> gnulib ./configure tests to (wrongly) fail, again resulting in
> compilation of vasnprintf.c with %n and ultimately killing groff
> at run-time.  I'll have to check whether such a problem really
> exists for groff.  If yes, i'll have to investigate further and
> find a fix.  If not, all this can be postponed until after release.
[...]
>> From what I understand we build this code only on some old platforms.
>> The code that uses %n is not built on my system.
>
> You probably have glibc, right?

Yes, I have glibc,

[...]
> If i manage to confirm that the tests for HAVE_SNPRINTF_RETVAL_C99
> and HAVE_SNPRINTF_TRUNCATION_C99 are reasoably robust, we can
> postpone further deliberation until after release, i think.
[...]
> I will re-test ASAP with the upcoming libc change; to save time,
> i will do so without waiting for that change to be committed.

OK, thanks for doing these tests; for the moment I think there is nothing
blocking the release.

Regards,
Bertrand Garrigues