public inbox for
 help / color / mirror / Atom feed
From: Mark Wielaard <>
Cc: Alexander Larsson <>,
	Matthias Klose <>,
	 "Dmitry V. Levin" <>,, Martin Liska <>,
Subject: debugedit project setup
Date: Mon, 22 Mar 2021 18:42:33 +0100	[thread overview]
Message-ID: <> (raw)


As discussed I setup a separate debugedit project:

It contains the debugedit and sepdebugcrcfix programs and the find- script and the testsuite. I used git-filter-
repo to keep the git history of the files from the rpm repo. Then I
resynced the libiberty and binutils files and added a minimal
automake/autoconf/autotest build system. Replace popt with getopt
argument parsing. And use libiberty md5 or sha1 instead of rpmDigest
algorithms for build-id updates.

There is a test debugedit-0.1 release to see whether this works. But I
would like to make sure first that things are setup so that flatpak and
rpm can use this as is before people start packaging it. Once we know
it can be used as replacement for the built-in rpm/flatpak debugedit we
do a proper debugedit 1.0 release.

Please join the debugedit mailinglist for discussions:

File bugs or feature requests:

Checkout the git repo:
git clone git://

I have played a bit with pagure, but haven't set it up properly, sorry.
So for now we'll do patches by email.



             reply	other threads:[~2021-03-22 17:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-22 17:42 Mark Wielaard [this message]
2021-03-23 12:29 ` [Rpm-ecosystem] " Panu Matilainen
     [not found]   ` <>
2021-03-25 21:13     ` Mark Wielaard
2021-03-26  1:11       ` Mark Wielaard
2021-03-29  8:21         ` Panu Matilainen
2021-03-29  8:31       ` Panu Matilainen
2021-03-29 11:00       ` Dmitry V. Levin
2021-06-18  8:37   ` Panu Matilainen

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).