From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27867] Support ostree archive format (.filez)
Date: Tue, 25 May 2021 14:26:59 +0000 [thread overview]
Message-ID: <bug-27867-10460-OclA0FnnnJ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27867-10460@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27867
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
Last reconfirmed| |2021-05-25
--- Comment #5 from Frank Ch. Eigler <fche at redhat dot com> ---
By the way, debuginfod's knowledge of archives is practically entirely based on
that of libarchive (= bsdtar). Have you considered reaching out upstream, to
have them learn to recognize these '.filez' directly? Then no code changes
would be needed for debuginfod.
Also: where would debuginfod find dwarf/source content for files packaged in
these archives? Is there a -debuginfod.filez type of archive that's also
available somewhere?
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2021-05-25 14:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 10:31 [Bug debuginfod/27867] New: " akitouni at gnome dot org
2021-05-15 10:34 ` [Bug debuginfod/27867] " fche at redhat dot com
2021-05-15 17:24 ` akitouni at gnome dot org
2021-05-15 17:24 ` akitouni at gnome dot org
2021-05-15 17:25 ` akitouni at gnome dot org
2021-05-25 14:26 ` fche at redhat dot com [this message]
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=bug-27867-10460-OclA0FnnnJ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=elfutils-devel@sourceware.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).