From: Leo Famulari <leo@famulari.name>
To: Sebastian Pipping <sebastian@pipping.org>
Cc: guix-devel@gnu.org
Subject: Re: Expat 2.3.0 has been released
Date: Sun, 9 May 2021 10:32:13 -0400 [thread overview]
Message-ID: <YJfybT5ohbLPZQrn@jasmine.lan> (raw)
In-Reply-To: <b7d82cb3-9e69-baec-4837-08d236e980c2@pipping.org>
On Sun, May 09, 2021 at 04:23:16PM +0200, Sebastian Pipping wrote:
> On 09.05.21 16:07, Leo Famulari wrote:
> > On Sun, May 09, 2021 at 02:53:09PM +0200, Sebastian Pipping wrote:
> >> The related soversions are:
> >>
> >> 2.2. 9 = 7:11:6 -> libexpatso.1.6.11 (GUIX today)
> >> 2.2.10 = 7:12:6 -> libexpatso.1.6.12
> >> 2.3. 0 = 8: 0:7 -> libexpatso.1.7.0 (GUIX W.I.P.)
> >> 2.4. 0 = 9: 0:8 -> libexpatso.1.8.0 (upcoming)
> >
> > Alright, in this case we'll need to cherry-pick the relevant bug fixes.
> >
> > See the manual section Security Updates for this note:
> >
> > "Other restrictions may apply: for instance, when adding a graft to a
> > package providing a shared library, the original shared library and its
> > replacement must have the same SONAME and be binary-compatible."
>
> The soname is the same: it's libexpatso.1 for all of them — no?
>
> # objdump -p libexpat.so.1.7.0 | grep SONAME
> SONAME libexpat.so.1
>
> They are binary-compatible. So I think there may be a misunderstanding
> here.
Ah, I misunderstood. It should be fine then to do the full update.
next prev parent reply other threads:[~2021-05-09 14:34 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 [this message]
2021-05-09 14:25 ` Maxime Devos
2021-05-09 22:07 ` Marius Bakke
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YJfybT5ohbLPZQrn@jasmine.lan \
--to=leo@famulari.name \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.