From: Paul Eggert <eggert@cs.ucla.edu>
To: Wookey <wookey@wookware.org>, "Daniel P. Berrangé" <berrange@redhat.com>
Cc: "Bruno Haible" <bruno@clisp.org>,
"Richard W.M. Jones" <rjones@redhat.com>,
"Demi Marie Obenour" <demiobenour@gmail.com>,
"Eric Blake" <eblake@redhat.com>, "Sam James" <sam@gentoo.org>,
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>,
autoconf@gnu.org, c-std-porting@lists.linux.dev,
"Zack Weinberg" <zack@owlfolio.org>,
"David Seifert" <soap@gentoo.org>,
"Gentoo Toolchain" <toolchain@gentoo.org>,
"Arsen Arsenović" <arsen@aarsen.me>,
dueno@redhat.com
Subject: Re: On time64 and Large File Support
Date: Thu, 2 Mar 2023 21:50:41 -0800 [thread overview]
Message-ID: <efff842e-a362-1552-c236-905f9d7d864a@cs.ucla.edu> (raw)
In-Reply-To: <20230303033045.GO12440@mail.wookware.org>
On 3/2/23 19:30, Wookey wrote:
> Gnulib automatically changing the ABI for packages that use it is
> deeply unhelpful and is going to cause significant breakage and
> hassle.
This change to Gnulib was reverted in December[1] and that propagated
into bleeding-edge GnuTLS last month[2]. So if I understand things
correctly the next GnuTLS release will go back to the old way of doing
things, which will tempt the 32-bit time_t rearguard to fall back into
"Let's not worry about 2038" mode.
However this is just one package. We'll likely see similar issues with
other packages, independently of whether they use Gnulib, and
independently of whether the built packages are not supposed to be used
after the year 2038.
So this incident is a warning siren for the 32-bit time_t community.
It's no time to relax.
[1]:
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=7c7c8a519f3892f6f5b30a1c6b22796ab314a45c
[2]:
https://gitlab.com/gnutls/gnutls/-/commit/9622d7201e1d73d217c18802e1d435ba3404adb3
next prev parent reply other threads:[~2023-03-03 5:50 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:38 Sam James
2022-11-11 9:16 ` Paul Eggert
2022-11-11 9:19 ` Sam James
2022-11-11 23:48 ` Joseph Myers
2022-11-11 9:19 ` Florian Weimer
2022-11-11 9:27 ` Sam James
2022-11-11 11:38 ` Florian Weimer
2022-11-11 20:12 ` Paul Eggert
2022-11-12 2:20 ` Zack Weinberg
2022-11-12 3:57 ` Sam James
2022-11-12 14:16 ` Zack Weinberg
2022-11-12 17:41 ` Paul Eggert
2022-11-12 18:50 ` Bruno Haible
2022-11-12 19:15 ` Paul Eggert
2022-11-12 20:23 ` Wookey
2022-11-12 20:54 ` Russ Allbery
2022-11-12 21:31 ` Paul Eggert
2022-11-15 5:09 ` Sam James
2022-11-12 18:19 ` Paul Eggert
2022-11-11 9:40 ` Andreas K. Huettel
2022-11-11 11:30 ` Florian Weimer
2022-11-11 19:01 ` Andreas K. Huettel
2022-11-11 19:28 ` Palmer Dabbelt
2022-11-11 9:46 ` Paul Eggert
2022-11-11 11:22 ` Florian Weimer
2022-11-11 19:56 ` Paul Eggert
2022-11-12 4:20 ` Wookey
2022-11-12 4:28 ` Sam James
2022-11-12 4:56 ` Wookey
2022-11-12 4:59 ` Sam James
2022-11-12 18:33 ` Paul Eggert
2022-11-14 8:39 ` Adam Sampson
2022-11-14 11:47 ` Florian Weimer
2022-11-14 20:26 ` Arsen Arsenović
2022-11-14 20:52 ` Florian Weimer
2022-11-15 7:39 ` Arsen Arsenović
2022-11-11 10:25 ` Richard Purdie
2023-03-01 22:38 ` Eric Blake
2023-03-02 0:29 ` Demi Marie Obenour
2023-03-02 9:04 ` Daniel P. Berrangé
2023-03-02 10:28 ` Paul Eggert
2023-03-02 10:38 ` Andreas Schwab
2023-03-03 5:46 ` Paul Eggert
2023-03-06 8:58 ` Andreas Schwab
2023-03-06 10:19 ` Florian Weimer
2023-03-02 11:02 ` Richard W.M. Jones
2023-03-02 12:17 ` Bruno Haible
2023-03-02 13:24 ` Daniel P. Berrangé
2023-03-03 3:30 ` Wookey
2023-03-03 5:50 ` Paul Eggert [this message]
2023-03-03 14:01 ` Wookey
2023-03-03 14:14 ` Daniel P. Berrangé
2023-03-03 23:21 ` Arsen Arsenović
2023-03-03 11:49 ` Florian Weimer
2023-03-03 12:39 ` Richard W.M. Jones
2023-03-02 8:30 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=efff842e-a362-1552-c236-905f9d7d864a@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=arsen@aarsen.me \
--cc=autoconf@gnu.org \
--cc=berrange@redhat.com \
--cc=bruno@clisp.org \
--cc=c-std-porting@lists.linux.dev \
--cc=demiobenour@gmail.com \
--cc=dueno@redhat.com \
--cc=eblake@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=rjones@redhat.com \
--cc=sam@gentoo.org \
--cc=soap@gentoo.org \
--cc=toolchain@gentoo.org \
--cc=wookey@wookware.org \
--cc=zack@owlfolio.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).