public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: elfutils-devel@sourceware.org
Subject: Re: debuginfod & Debian source packages
Date: Thu, 02 Jun 2022 15:32:48 -0400	[thread overview]
Message-ID: <87mteukgin.fsf@sergiodj.net> (raw)
In-Reply-To: <20220602182627.GA8520@redhat.com> (Frank Ch. Eigler's message of "Thu, 2 Jun 2022 14:26:27 -0400")

On Thursday, June 02 2022, Frank Ch. Eigler wrote:

> Hi -

Hi Frank,

>> I'm the maintainer of debuginfod.debian.net (currently offline due to a
>> hardware issue :-/).
>
> O no.  (And also, please consider upgrading your elfutils version, as
> later ones have less pessimal behavior with long grooming ops.)

I have to backport the new version to Debian bullseye, but yeah, this is
on my TODO list.

>> [...]
>> I'm now thinking about an alternative solution to this problem.  Debian
>> source packages already contain everything needed to be indexed and
>> served to debuginfo consumers; it has the full source code + all the
>> downstream patches.  It's represented by a .dsc file that can be fed to
>> dget(1) which will download the source tarball and apply all the patches
>> automatically.
>> 
>> Do you think we can teach debuginfod to consume these files and do the
>> right thing when indexing the source code of each package? [...]
>
> Interesting idea, but I'd throw it back at you thusly: does debuginfod
> need to this itself on the fly?  Other than perhaps a time/storage
> tradeoff, is there some reason an auxiliary program couldn't do this
> in the background?  Take designated .dsc's, download, apply patches,
> and assemble the patched sources into, well, any old random tarball
> format?  If someone(tm) were to write such a script, we could ship it
> alongside debuginfod if desired.

Sure, I believe an external script/program could do things behind the
scenes without problem.

> As long as the archive file name was a close match to the binary deb
> file names, and as long as the constituent files were named with the
> same paths as mentioned in the binary dwarf, debuginfod would gladly
> take the result and serve from it.

OK, this was going to be my next question.  Out of curiosity, how would
debuginfod invoke this external program?

Thanks,

-- 
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/

  reply	other threads:[~2022-06-02 19:32 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 [this message]
2022-06-02 19:34     ` Frank Ch. Eigler
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=87mteukgin.fsf@sergiodj.net \
    --to=sergiodj@sergiodj.net \
    --cc=elfutils-devel@sourceware.org \
    --cc=fche@redhat.com \
    /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).