From: "akitouni at gnome dot org" <sourceware-bugzilla@sourceware.org>
To: elfutils-devel@sourceware.org
Subject: [Bug debuginfod/27867] New: Support ostree archive format (.filez)
Date: Sat, 15 May 2021 10:31:01 +0000 [thread overview]
Message-ID: <bug-27867-10460@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=27867
Bug ID: 27867
Summary: Support ostree archive format (.filez)
Product: elfutils
Version: unspecified
Status: UNCONFIRMED
Severity: enhancement
Priority: P2
Component: debuginfod
Assignee: unassigned at sourceware dot org
Reporter: akitouni at gnome dot org
CC: elfutils-devel at sourceware dot org
Target Milestone: ---
debuginfod supports a few archive formats. It would be nice to support ostree
archive files too. ostree is used by a few
They have the .filez extension and have the following format: (I don't think it
is documented, but it is stable and can be seen in the code
https://github.com/ostreedev/ostree/blob/main/src/libostree/ostree-core.c#L475)
4 bytes header length (big endian)
4 bytes padding
header
content (deflate compressed without the zlib header)
So one should be able to read the header length, skip the padding and header
and read (and decompress) the contents.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-05-15 10:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-15 10:31 akitouni at gnome dot org [this message]
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
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@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).