From: Arjan van de Ven <arjan@linux.intel.com>
To: Mark Wielaard <mark@klomp.org>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
elfutils-devel@sourceware.org, patrick.mccarty@intel.com
Subject: Re: contrasting elfutils debuginfod and clr-debug-info server
Date: Sun, 09 Feb 2020 17:43:00 -0000 [thread overview]
Message-ID: <5dd8da0f-1c39-1783-273c-5429f246bf69@linux.intel.com> (raw)
In-Reply-To: <6105803d9aab87535b94e39d65de82021a532eb9.camel@klomp.org>
On 2/7/2020 3:47 PM, Mark Wielaard wrote:
> Hi Arjan,
>
> I assumed that the buildid.tar files on
> https://download.clearlinux.org/debuginfo/lib/.build-id/ would contain
> the ELF image corresponding to the build-id. Just like the
> buildid.debug.tar contains the separate .debug image. At least, that
> would be how I would handle it. But it seems those files contain
> symlinks. How do those symlinks get resolved?
I think you just found a bug, and I'll take that up with the current maintainer ;-)
we used to "resolve" symlinks on the server by replacing them at the time of content
preparation with their target, so that they become permanently the right content
seems some shuffle broke that; we'll get that fixed
next prev parent reply other threads:[~2020-02-09 17:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 17:33 Frank Ch. Eigler
2020-02-05 19:11 ` Arjan van de Ven
2020-02-05 19:14 ` Frank Ch. Eigler
2020-02-05 22:05 ` Arjan van de Ven
2020-02-07 9:13 ` Mark Wielaard
2020-02-07 14:47 ` Arjan van de Ven
2020-02-07 23:47 ` Mark Wielaard
2020-02-09 17:43 ` Arjan van de Ven [this message]
2020-02-07 9:06 ` Mark Wielaard
2020-02-07 14:46 ` Arjan van de Ven
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=5dd8da0f-1c39-1783-273c-5429f246bf69@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=elfutils-devel@sourceware.org \
--cc=fche@redhat.com \
--cc=mark@klomp.org \
--cc=patrick.mccarty@intel.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).