From: Christian Heusel <gromit@archlinux.org>
To: "Petr Tesařík" <petr@tesarici.cz>
Cc: Stephen Brennan <stephen@brennan.io>,
linux-debuggers@vger.kernel.org,
Omar Sandoval <osandov@osandov.com>
Subject: Re: drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch
Date: Thu, 2 Jan 2025 15:13:29 +0100 [thread overview]
Message-ID: <29b93529-5e28-4458-bf39-e12c00d84c16@heusel.eu> (raw)
In-Reply-To: <20250102145728.0c61ed68@meshulam.tesarici.cz>
[-- Attachment #1: Type: text/plain, Size: 1119 bytes --]
On 25/01/02 02:57PM, Petr Tesařík wrote:
> On Thu, 2 Jan 2025 09:57:52 +0100
> Christian Heusel <gromit@archlinux.org> wrote:
> > thanks for your report and suggestions to fix the underlying issue! It
> > turns out I somehow missed the soname bump in libkdumpfile's last
> > release (also I'm a bit annoyed that it had one in a patch release)
> > ... 😅
>
> Hey, you may want to know that libkdumpfile (package) does not follow
> any kind of semantic versioning rules. So, there's nothing like a
> "patch release".
Alright, thats good to know!
> I will reconsider this approach with the release of v1.0, but that's
> not planned until there is feature parity with the crash utility...
>
> However, since some people have already found the library useful, I
> maintain libtool versioning, which takes care of API and ABI updates
> (and makes it possible to install multiple ABI-incompatible versions on
> a single system).
Yeah again as I wrote initially, missing the soname bump one is
definitely on me!
> Petr T
Hope y'all had a great start into the year 🎉🎆
~ Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2025-01-02 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-02 8:08 drgn 0.0.30 and libkdumpfile 0.5.5 incompatibility in Arch Stephen Brennan
2025-01-02 8:31 ` Stephen Brennan
2025-01-02 8:57 ` Christian Heusel
2025-01-02 13:57 ` Petr Tesařík
2025-01-02 14:13 ` Christian Heusel [this message]
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=29b93529-5e28-4458-bf39-e12c00d84c16@heusel.eu \
--to=gromit@archlinux.org \
--cc=linux-debuggers@vger.kernel.org \
--cc=osandov@osandov.com \
--cc=petr@tesarici.cz \
--cc=stephen@brennan.io \
/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