public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Luca Boccassi <bluca@debian.org>
To: "Mark Wielaard" <mark@klomp.org>,
	"Zbigniew Jędrzejewski-Szmek" <zbyszek@in.waw.pl>
Cc: devel@lists.fedoraproject.org,
	systemd-devel@lists.freedesktop.org,
	 debhelper@packages.debian.org, binutils@sourceware.org,
	Lennart Poettering <lennart@poettering.net>,
	debian-dpkg@lists.debian.org,
	 "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: Storing package metadata in ELF objects
Date: Thu, 06 May 2021 12:43:13 +0100	[thread overview]
Message-ID: <b1816df2a4e4036db77065e3d018e2df9b43497b.camel@debian.org> (raw)
In-Reply-To: <f289ad7cbd0a92d524f7467cbd048b20676155b4.camel@klomp.org>

[-- Attachment #1: Type: text/plain, Size: 1411 bytes --]

On Thu, 2021-05-06 at 03:17 +0200, Mark Wielaard wrote:
> Hi Luca,
> 
> On Tue, 2021-05-04 at 14:43 +0100, Luca Boccassi wrote:
> > On Fri, 2021-04-30 at 19:57 +0200, Mark Wielaard wrote:
> > > Is there a list of default keys (and their canonical spelling, upper-
> > > lower-Camel_Case, etc.)? If there is, could we have a "debuginfod" key
> > > with as value an URL pointing to the debuginfod server URL where the
> > > embedded build-id executable, debuginfo and sources can be found?
> > > https://sourceware.org/elfutils/Debuginfod.html
> > 
> > The "Implementation" section of the spec lists the "main" fields:
> > 
> > https://systemd.io/COREDUMP_PACKAGE_METADATA/
> > 
> > (source for that is https://github.com/systemd/systemd/blob/main/docs/COREDUMP_PACKAGE_METADATA.md )
> > 
> > Would you like to send a PR to update it and add that field?
> 
> Sorry, I don't have a github account. But attached is a patch for to
> document it and one for the package-notes generator to add an --
> debuginfod argument (maybe the distro should set a default value for
> that?) Hopefully those patches could be applied somehow.

Hi,

Thanks, opened PRs with your commits:

https://github.com/systemd/systemd/pull/19523
https://github.com/systemd/package-notes/pull/8

Yes, if the distro has a debuginfod server, it should definitely be
included.

-- 
Kind regards,
Luca Boccassi

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2021-05-06 11:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-10 12:29 Luca Boccassi
2021-04-10 12:38 ` Luca Boccassi
2021-04-10 18:44   ` Zbigniew Jędrzejewski-Szmek
2021-04-30 17:57     ` Mark Wielaard
2021-05-04 13:43       ` Luca Boccassi
2021-05-06  1:17         ` Mark Wielaard
2021-05-06 11:43           ` Luca Boccassi [this message]
2021-05-14 10:41   ` Guillem Jover
2021-05-14 13:41     ` Luca Boccassi
2021-05-19  0:19       ` Guillem Jover
2021-05-19 14:58         ` Mark Wielaard
2021-05-24 10:17           ` Luca Boccassi

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=b1816df2a4e4036db77065e3d018e2df9b43497b.camel@debian.org \
    --to=bluca@debian.org \
    --cc=binutils@sourceware.org \
    --cc=debhelper@packages.debian.org \
    --cc=debian-dpkg@lists.debian.org \
    --cc=devel@lists.fedoraproject.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=lennart@poettering.net \
    --cc=mark@klomp.org \
    --cc=systemd-devel@lists.freedesktop.org \
    --cc=zbyszek@in.waw.pl \
    /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).