public inbox for
 help / color / mirror / Atom feed
From: "rgoldber at redhat dot com" <>
Subject: [Bug debuginfod/29472] Support querying the debuginfod-server for metadata
Date: Mon, 22 Aug 2022 18:24:57 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

--- Comment #2 from Ryan Goldberg <rgoldber at redhat dot com> ---
Created attachment 14289
Submit A Patch for 29472

Here is patch which is simpler than the above proposal. It allows for querying
by source path and will return a JSON array of metadata (where the metadata for
each file is its own JSON object).

The patch was tested using the elfutils try-buildbots on branch

There is a need for this patch as currently, even with work like PR 28284, a
user is unable to check what files are accessible with debuginfod, they can
only at most try and query by buildid and see if they can get a result. This
feature will be used in systemtap PR 27410

You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-22 18:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 14:43 [Bug debuginfod/29472] New: " rgoldber at redhat dot com
2022-08-12  9:05 ` [Bug debuginfod/29472] " mliska at suse dot cz
2022-08-12  9:05 ` mliska at suse dot cz
2022-08-22 18:24 ` rgoldber at redhat dot com [this message]
2022-08-31 14:52 ` rgoldber at redhat dot com
2022-09-02 17:25 ` rgoldber at redhat dot com
2022-11-01 14:23 ` PATCH: Bug debuginfod/29472 followup Frank Ch. Eigler
2022-11-01 22:20   ` Mark Wielaard
2022-11-10 17:12     ` Frank Ch. Eigler
2023-03-01 23:32       ` Mark Wielaard
2023-02-28 22:21 ` [Bug debuginfod/29472] Support querying the debuginfod-server for metadata mark at klomp dot org

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