public inbox for distributions@lists.linux.dev
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: distributions@lists.linux.dev
Subject: tzdata-2024b chaos
Date: Tue, 10 Sep 2024 01:17:17 +0100	[thread overview]
Message-ID: <87jzfk1hwy.fsf@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1117 bytes --]

Hi!

There's two issues with the latest tzdata-2024b release.

1) "Apr" vs "April" which has confused some broken parsers;
there's a patch for this post-release [0].

2) Both libc++ and libstdc++ appear broken with a separate problem
[1][2][3].

This manifests in Waybar, for example [4].

It's not clear to me if libc++ is broken or not, as people in the bug
may have been testing a clang configured to use libstdc++ (the default),
and I don't have a system to test it on to hand.

--

Paul Eggert, the tzdata maintainer, notes on the ML in one of the
threads discussing this that rolling back to 2024a is a reasonable
workaround for now, as there's no critical data changes in 2024b [5].

[0] https://github.com/eggert/tz/commit/926b507fa5c3192b1b68fab5910cbd3ba9377c97
[1] https://github.com/llvm/llvm-project/issues/107779
[2] https://gcc.gnu.org/PR116657
[3] https://lists.iana.org/hyperkitty/list/tz@iana.org/message/TECYKLZV3BBPYEJ73YWRQWFCKN62P67Z/
[4] https://github.com/Alexays/Waybar/issues/3575
[5] https://lists.iana.org/hyperkitty/list/tz@iana.org/message/HSKHZBRALUYDSSSQQ73E5VMJMEWEI4OO/

thanks,
sam

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

             reply	other threads:[~2024-09-10  0:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10  0:17 Sam James [this message]
2024-09-10  8:21 ` tzdata-2024b chaos Yao Zi
2024-09-10  8:35   ` Michał Górny

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=87jzfk1hwy.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=distributions@lists.linux.dev \
    /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