From: Panu Matilainen <pmatilai@redhat.com>
To: debugedit@sourceware.org, rpm-ecosystem@lists.rpm.org,
Mark Wielaard <mark@klomp.org>
Cc: "Dmitry V. Levin" <ldv@sourceware.org>,
Martin Liska <mliska@suse.cz>, Matthias Klose <doko@debian.org>,
christian.morales.vega@gmail.com,
Alexander Larsson <alexl@redhat.com>
Subject: Re: [Rpm-ecosystem] debugedit project setup
Date: Tue, 23 Mar 2021 14:29:03 +0200 [thread overview]
Message-ID: <fbeba40d-cb68-113c-2db7-9789e27426c5@redhat.com> (raw)
In-Reply-To: <7bdd564bae323bf300ddeba40cba5313e3eaa22d.camel@klomp.org>
On 3/22/21 7:42 PM, Mark Wielaard wrote:
> Hi,
>
> As discussed I setup a separate debugedit project:
> https://sourceware.org/debugedit/
>
> It contains the debugedit and sepdebugcrcfix programs and the find-
> debuginfo.sh script and the debugedit.at 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.
Awesome. I'll make it a priority to see that we transition, if at all
possible, to the external debugedit in rpm 4.17 already. Stay tuned...
>
> Please join the debugedit mailinglist for discussions:
> https://sourceware.org/mailman/listinfo/debugedit
>
> File bugs or feature requests:
> https://sourceware.org/bugzilla/enter_bug.cgi?product=debugedit
>
> Checkout the git repo:
> git clone git://sourceware.org/git/debugedit.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.
I for one far prefer patches by email over Pagure...
- Panu -
>
> Cheers,
>
> Mark
> _______________________________________________
> Rpm-ecosystem mailing list
> Rpm-ecosystem@lists.rpm.org
> http://lists.rpm.org/mailman/listinfo/rpm-ecosystem
>
next prev parent reply other threads:[~2021-03-23 12:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 17:42 Mark Wielaard
2021-03-23 12:29 ` Panu Matilainen [this message]
[not found] ` <5c1d49ba-5a01-e6b2-dbc7-3cd64d552688@redhat.com>
2021-03-25 21:13 ` [Rpm-ecosystem] " 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:
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=fbeba40d-cb68-113c-2db7-9789e27426c5@redhat.com \
--to=pmatilai@redhat.com \
--cc=alexl@redhat.com \
--cc=christian.morales.vega@gmail.com \
--cc=debugedit@sourceware.org \
--cc=doko@debian.org \
--cc=ldv@sourceware.org \
--cc=mark@klomp.org \
--cc=mliska@suse.cz \
--cc=rpm-ecosystem@lists.rpm.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).