From: Marius Bakke <marius@gnu.org>
To: Sebastian Pipping <sebastian@pipping.org>
Cc: guix-devel@gnu.org
Subject: Re: Expat 2.3.0 has been released
Date: Mon, 10 May 2021 00:07:06 +0200 [thread overview]
Message-ID: <8735uvwohh.fsf@gnu.org> (raw)
In-Reply-To: <20afb227-5e89-e416-4ca4-12bd0ac98a29@pipping.org>
[-- Attachment #1: Type: text/plain, Size: 951 bytes --]
Sebastian Pipping <sebastian@pipping.org> skriver:
> Hello everyone,
>
>
> just a quick heads up that there will be a new release of libexpat with
> security fix in a few weeks. Unless I looked in the wrong place, I
> noticed that your distro has not updated to libexpat 2.3.0 as of today.
> If you ran into any issues with packaging 2.3.0, please let me know now
> so that I can fix things upstream for you and everyone while there is
> still a window before next releases to do so. Thank you!
Hi Sebastian,
I have updated expat on our "core-updates" branch, since it entails a
full rebuild:
https://git.savannah.gnu.org/cgit/guix.git/commit/?h=core-updates&id=831c6d84e1bcff4b68dfd0f6e299f2c0bb60d0b8
I notice 2.3.0 does not have any ABI changes from 2.2.9. In that case
the security fix/version can be "grafted" in place without rebuilding
the world. So count us ready, we'll test 2.3.0 meanwhile. :-)
Thanks for the heads-up,
Marius
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
next prev parent reply other threads:[~2021-05-09 22:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 20:27 Expat 2.3.0 has been released Sebastian Pipping
2021-05-08 16:00 ` Sebastian Pipping
2021-05-09 9:12 ` Maxime Devos
2021-05-09 9:17 ` Maxime Devos
2021-05-09 12:53 ` Sebastian Pipping
2021-05-09 14:07 ` Leo Famulari
2021-05-09 14:23 ` Sebastian Pipping
2021-05-09 14:32 ` Leo Famulari
2021-05-09 14:25 ` Maxime Devos
2021-05-09 22:07 ` Marius Bakke [this message]
2021-05-09 22:23 ` Sebastian Pipping
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=8735uvwohh.fsf@gnu.org \
--to=marius@gnu.org \
--cc=guix-devel@gnu.org \
--cc=sebastian@pipping.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).