Re: regex.c sync with libc broken

2024-01-02 Thread Paul Eggert
On 2024-01-02 08:05, Karl Berry wrote: Looks like the pragmas recently added to lib/regex.c have not been installed upstream. Actually it's the other way around, so things are good now. I recently removed those pragmas from Gnulib, not realizing the file was synced from glibc. You autoupdated

regex.c sync with libc broken

2024-01-02 Thread Karl Berry
Looks like the pragmas recently added to lib/regex.c have not been installed upstream. I did the sync from libc anyway ... -k *** lib/regex.c Sun Dec 31 00:26:03 2023 --- /tmp/gnulib.srclist/regex.c Tue Jan 2 00:26:37 2024 *** *** 1,4 /* Extended regular expression matching and

Re: Behaviour of strverscmp(3)

2024-01-02 Thread Bruno Haible
Dmitry Bogatov wrote: > > Example code: > > > > #include > > #include > > > > int main() > > { > > int value = strverscmp("UNKNOWN", "2.2.0"); > > printf("%d\n", value); > > return 0; > > } > > > > Under glibc value "35" is printed (positive), under musl value "-1" is > > printed (neg

Re: Copyright year update

2024-01-02 Thread Bernhard Voelker
On 1/2/24 01:58, Paul Eggert wrote: On 2024-01-01 16:08, Bernhard Voelker wrote: That commit broke the 'update-copyright' tests, because the test script got messed up. Thanks for reporting that. Turing would have been amused by update-copyright modifying its own test, and then failing the modi