After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 759250 - teach 'ostree remote refs' to show contents of summary file
teach 'ostree remote refs' to show contents of summary file
Status: RESOLVED FIXED
Product: ostree
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: OSTree maintainer(s)
OSTree maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-12-09 14:24 UTC by Micah Abbott
Modified: 2015-12-17 20:54 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Micah Abbott 2015-12-09 14:24:11 UTC 
While debugging a problem retrieving an ostree update from Red Hat's CDN, I asked about downloading the ostree summary file and reading its contents via the 'ostree' cli.

Colin suggested we should teach 'ostree remote refs' to display the info from the summary file.

<micah> walters: if i download the summary file, is it possible to read it with 'ostree' cli?
<walters> micah, unfortunately not, but what we should do is teach `ostree remote refs` to show this
Comment 1 Matthew Barnes 2015-12-09 14:44:55 UTC 
Definitely agree with the feature, but "ostree remote refs" doesn't strike me as the best place for it.

We do already have "ostree summary --update".

I think "ostree summary --show" or even just "ostree summary" would be a better fit.  It could take a --file option to explicitly point to a downloaded summary file, instead of the one for --repo.
Comment 2 Micah Abbott 2015-12-09 16:02:37 UTC 
+1 to the --file option

I don't really have a preference to where this feature lives in the CLI; I'll leave it up to the implementer.
Comment 3 Colin Walters 2015-12-09 18:16:00 UTC 
Inspecting the downloaded file wasn't too hard, but if the remote is protected by e.g. client certificates one needs to resort to something like:

curl -v --cacert /etc/rhsm/ca/redhat-uep.pem --cert /etc/pki/entitlement/8311524499068446497.pem --key /etc/pki/entitlement/8311524499068446497-key.pem https://cdn.redhat.com/content/dist/rhel/atomic/7/7Server/x86_64/ostree/repo/summary > summary

Since we already fetch the summary file in `remote refs` that's why I was thinking something like

`ostree remote refs -v` to show full details (maybe things like availability of static deltas too?)
Comment 4 Matthew Barnes 2015-12-09 18:36:51 UTC 
Okay, that makes sense.  I was thinking this was for local inspection.

Could also do something like "ostree remote summary" since we'd need a completely separate code branch for the -v option anyway.
Comment 5 Matthew Barnes 2015-12-17 00:12:12 UTC 
https://github.com/GNOME/ostree/pull/163