1OSTREE SUMMARY(1) ostree summary OSTREE SUMMARY(1)
2
3
4
6 ostree-summary - Regenerate or view the summary metadata file
7
9 ostree summary [--gpg-sign=KEYID] [--gpg-homedir=HOMEDIR] {--update}
10 [--add-metadata=KEY=VALUE...]
11
12 ostree summary {--view | --raw}
13
15 The summary file is an optional higher level form of repository
16 metadata that describes the available branches. It needs to be manually
17 regenerated after a series of commits. Among other things, this allows
18 atomically updating multiple commits.
19
21 --update,-u
22 Update the summary file. This option can be combined with
23 --add-metadata to add metadata fields to the summary.
24
25 If the repository has a collection ID configured, the
26 ostree-metadata branch for that collection ID will also be updated
27 with a new commit containing the given metadata, which will be
28 signed if the summary file is signed.
29
30 --add-metadata,-m=KEY=VALUE
31 Specify an additional metadata field to add to the summary. It must
32 be in the format KEY=VALUE or as two separate arguments. The keys
33 must be namespaced for your organisation or repository using a dot
34 prefix. The values must be in GVariant text format. For example,
35 exampleos.end-of-life "@t 1445385600". This option can be used
36 multiple times.
37
38 --view,-v
39 View the contents of the summary file in a human readable format.
40
41 --raw
42 View the raw bytes of the summary file.
43
44 --gpg-sign=KEYID
45 GPG Key ID to sign the summary with.
46
47 --gpg-homedir=HOMEDIR
48 GPG Homedir to use when looking for keyrings.
49
51 $ ostree summary -u
52
53 $ ostree summary -u -m key="'value'"
54
55 $ ostree summary -v
56
57 * ostree/1/1/0
58 Latest Commit (4.2 MB):
59 9828ab80f357459b4ab50f0629beab2ae3b67318fc3d161d10a89fae353afa90
60 Timestamp (ostree.commit.timestamp): 2017-11-21T01:41:10-08
61
62 Last-Modified (ostree.summary.last-modified): 2018-01-12T22:06:38-08
63
64
65
66OSTree OSTREE SUMMARY(1)