From: Stephen Brennan <stephen@brennan.io>
To: Christian Heusel <gromit@archlinux.org>
Cc: linux-debuggers@vger.kernel.org
Cc: Omar Sandoval <osandov@osandov.com>
Cc: Petr Tesarik <petr@tesarici.cz>
Subject: drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch
Date: Thu, 02 Jan 2025 00:08:34 -0800 [thread overview]
Message-ID: <875xmxljst.fsf@brennan.io> (raw)
Hi Christian,
I think you may already be aware of this, but I wanted to let you know
that there's an incompatibility with drgn 0.0.30-2 and libkdumpfile
0.5.5-1 on Arch. libkdumpfile 0.5.5 changed some APIs in a
backward-incompatible way. Building drgn against the new version fails,
and running a version built against 0.5.4 of course fails due to the
soname change. The current drgn 0.0.30-2 on Arch's repositories was
built against 0.5.4.
Thus a user installing drgn & libkdumpfile on Arch, who is fully
up-to-date, gets this:
ImportError: libkdumpfile.so.10: cannot open shared object file: No such file or directory
The incompatibility is fixed in drgn's main branch by the changes in
[1]. Unfortunately, that was merged after drgn 0.0.30 was released.
Some major changes have been merged since then, so I don't think a
0.0.31 release is likely for a few months. So I think it may be a good
idea to carry the two commits in [1] as downstream patches in a new
0.0.30-3 release. I'd be happy to implement those changes if it'd help.
I'm Ccing the linux-debuggers mailing list for posterity, as well as
Omar and Petr as an FYI.
Thanks,
Stephen
[1]: https://github.com/osandov/drgn/pull/452
next reply other threads:[~2025-01-02 8:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 8:08 Stephen Brennan [this message]
2025-01-02 8:31 ` drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch Stephen Brennan
2025-01-02 8:57 ` Christian Heusel
2025-01-02 13:57 ` Petr Tesařík
2025-01-02 14:13 ` Christian Heusel
2025-01-02 17:22 ` Stephen Brennan
2025-01-02 8:58 ` Petr Tesařík
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=875xmxljst.fsf@brennan.io \
--to=stephen@brennan.io \
--cc=gromit@archlinux.org \
--cc=linux-debuggers@vger.kernel.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