From: "Frank Ch. Eigler" <fche@redhat.com>
To: Sergio Durigan Junior <sergiodj@sergiodj.net>
Cc: elfutils-devel@sourceware.org
Subject: Re: debuginfod & Debian source packages
Date: Thu, 2 Jun 2022 15:34:20 -0400 [thread overview]
Message-ID: <20220602193420.GB8520@redhat.com> (raw)
In-Reply-To: <87mteukgin.fsf@sergiodj.net>
Hi -
> [...]
> OK, this was going to be my next question. Out of curiosity, how would
> debuginfod invoke this external program?
That's the best part. It doesn't need to. :-) Whatever program you're
using to freshen the repository of .deb's that your debuginfod
scrapes, could also run this program for any new .dsc's. i.e., keep
the problem from debuginfod entirely.
- FChE
next prev parent reply other threads:[~2022-06-02 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 2:23 Sergio Durigan Junior
2022-06-02 18:26 ` Frank Ch. Eigler
2022-06-02 19:32 ` Sergio Durigan Junior
2022-06-02 19:34 ` Frank Ch. Eigler [this message]
2022-06-02 19:38 ` Sergio Durigan Junior
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=20220602193420.GB8520@redhat.com \
--to=fche@redhat.com \
--cc=elfutils-devel@sourceware.org \
--cc=sergiodj@sergiodj.net \
/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).