public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
To: "Michał Górny" <>,
Subject: Re: Please raise version number above RPM releases
Date: Fri, 02 Jul 2021 12:36:53 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Hi Michał,

On Sun, 2021-06-27 at 08:36 +0200, Michał Górny wrote:
> We've been packaging the RPM's debugedit executable as 'debugedit'
> since 2006.  This means that the versions of debugedit packages
> in Gentoo have corresponded to RPM releases.
> Now, we'd like to switch to your version.  However, the problem is that
> you've restarted versioning -- at least from our perspective.  If we
> added debugedit-0.3 to Gentoo today, it would be seen as an older
> version that the 'old' debugedit- (i.e. rpm's debugedit).
> There are hacks around this but they're all particularly ugly.  Hence,
> I'm wondering if it wouldn't be too much of a hassle to you to raise
> the version number above the current RPM version, i.e. version 5.* or
> 6.* (if you take rpm5 into consideration, it is pretty dead though).
> While I do realize the problem's on our end, it's non-trivial to fix
> because of backwards compatibility requirements we have.  And as I said,
> workarounds are particularly ugly and confusing, so I'd rather avoid
> them if possible.

Thanks for bringing that up. I think it is fine to make the first
official release debugedit 5.0. It will make us look like a really
mature project :)

Before the first formal release I am doing a few more cleanups, just
simple stuff like making sure we are checking all errors, etc. And I
would like to make sure there are command line equivalents for the few
remaining RPM environment variables used in find-debuginfo:
There is also one bug reported against Fedora where we fail to produce
the main source file in some cases when processing DWARF5:
For which I have a partial patch, but I am unsure if it is complete.



  reply	other threads:[~2021-07-02 10:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-27  6:36 Michał Górny
2021-07-02 10:36 ` Mark Wielaard [this message]
2021-07-02 10:39   ` Michał Górny
2021-07-02 10:41     ` Mark Wielaard
2021-07-02 10:43       ` Michał Górny

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).