From: Janneke Nieuwenhuizen <janneke@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>, andreas@enge.fr
Subject: Re: [Bruno Haible] GNU gettext 0.23.1 is released
Date: Wed, 08 Jan 2025 18:58:37 +0100 [thread overview]
Message-ID: <87frltrxv6.fsf@gnu.org> (raw)
In-Reply-To: <87tta9wuqj.fsf@gnu.org> ("Ludovic Courtès"'s message of "Wed, 08 Jan 2025 09:55:00 +0100")
Ludovic Courtès writes:
Hi!
> Sharing this message about upgrading Gettext, with Bruno’s permission (I
> believe gettext should be in the scope of the ‘core-packages’ team).
Thanks!
> New in 0.23.1:
>
> * Bug fixes:
> - Building with libxml2 >= 2.12.0 and gcc >= 14 now works.
FWIW, libxml2 is (still) at 2.9.14, also on core-packages-team, and
building with gcc-14.2 just worked on core-packages-team.
It didn't need updating and I'm trying to avoid scope creep beyond
moving to gcc-14 at this time, esp. an upgrade storm.
We still need to disable test-execute.sh, just like with 0.23
--8<---------------cut here---------------start------------->8---
;;libgettextlib-0.23.so => not found
(substitute* "gettext-tools/gnulib-tests/test-execute.sh"
(("^#!.*" all)
(string-append all "exit 77;\n")))
--8<---------------cut here---------------end--------------->8---
so I'm not seeing any difference. But I guess newer is better and while
we're upgrading...
> - XML: The value of the xml:lang attribute, inserted by msgfmt, is now
> more correct.
Okay, I've pushed an upgrade commit 0.23.1 to core-packages-team with
back-to-back a REMOVEME Revert... commit to not trigger a world rebuild
at this time.
Greetings,
Janneke
--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | Avatar® https://AvatarAcademy.com
prev parent reply other threads:[~2025-01-08 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-08 8:55 [Bruno Haible] GNU gettext 0.23.1 is released Ludovic Courtès
2025-01-08 17:58 ` Janneke Nieuwenhuizen [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87frltrxv6.fsf@gnu.org \
--to=janneke@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).