[Bug debuginfod/27867] New: Support ostree archive format (.filez)

[Bug debuginfod/27867] New: Support ostree archive format (.filez)

[akitouni at gnome dot org]

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.

[Bug debuginfod/27867] Support ostree archive format (.filez)

[fche at redhat dot com]

https://sourceware.org/bugzilla/show_bug.cgi?id=27867

Frank Ch. Eigler <fche at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |fche at redhat dot com

--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
Can you link to an actual ostree archive file we can look at?

Are ostree archives usually assembled from upstream distro binaries, which
could already be looked up in a corresponding debuginfod?

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

[Bug debuginfod/27867] Support ostree archive format (.filez)

[akitouni at gnome dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27867

--- Comment #2 from Abderrahim Kitouni <akitouni at gnome dot org> ---
(In reply to Frank Ch. Eigler from comment #1)
> Can you link to an actual ostree archive file we can look at?

Here is an example: debug info for epiphany

https://dl.flathub.org/repo/objects/de/0800585350a08de5c92505e84144f18dbf7f4c74687e7a02b3ff415419bf26.filez

> Are ostree archives usually assembled from upstream distro binaries, which
> could already be looked up in a corresponding debuginfod?

It depends, in the case of Fedora Silverblue or EndlessOS they're generated
from the .rpm/.deb packages. But sometimes they're not. The main case where
ostree is the original format is for flatpak apps (although there are OSes that
generate ostree directly, for instance the GNOME OS testing images).

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

[Bug debuginfod/27867] Support ostree archive format (.filez)

[akitouni at gnome dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27867

--- Comment #3 from Abderrahim Kitouni <akitouni at gnome dot org> ---
Created attachment 13450
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13450&action=edit
The example file

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

[Bug debuginfod/27867] Support ostree archive format (.filez)

[akitouni at gnome dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27867

--- Comment #4 from Abderrahim Kitouni <akitouni at gnome dot org> ---
Created attachment 13451
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13451&action=edit
The decompressed file

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

[Bug debuginfod/27867] Support ostree archive format (.filez)

[fche at redhat dot com]

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.