1FLATPAK BUILD-COMMI(1)     flatpak build-commit-from    FLATPAK BUILD-COMMI(1)
2
3
4

NAME

6       flatpak-build-commit-from - Create new commits based on existing one
7       (possibly from another repository)
8

SYNOPSIS

10       flatpak build-commit-from [OPTION...] DST-REPO DST-REF...
11

DESCRIPTION

13       Creates new commits on the DST-REF branch in the DST-REPO, with the
14       contents (and most of the metadata) taken from another branch, either
15       from another repo, or from another branch in the same repository.
16
17       The collection ID set on DST-REPO (if set) will be used for the newly
18       created commits.
19
20       This command is very useful when you want to maintain a branch with a
21       clean history that has no unsigned or broken commits. For instance, you
22       can import the head from a different repository from an automatic
23       builder when you've verified that it worked. The new commit will have
24       no parents or signatures from the autobuilder, and can be properly
25       signed with the official key.
26
27       Any deltas that affect the original commit and that match parent
28       commits in the destination repository are copied and rewritten for the
29       new commit id.
30

OPTIONS

32       The following options are understood:
33
34       -h, --help
35           Show help options and exit.
36
37       --src-repo=SRC-REPO
38           The (local) repository to pull the source branch from. Defaults to
39           the destination repository.
40
41       --src-ref=SRC-REF
42           The branch to use as the source for the new commit. Defaults to the
43           same as the destination ref, which is useful only if a different
44           source repo has been specified.
45
46       --extra-collection-id=COLLECTION-ID
47           Add an extra collection-ref binding for this collection, in
48           addition to whatever would normally be added due to the destination
49           repository collection id. This option can be used multiple times.
50
51       --subset=SUBSET
52           Mark the commit to be included in the named subset. This will cause
53           the commit to be put in the named subset summary (in addition to
54           the main one), allowing users to see only this subset instead of
55           the whole repo.
56
57       --untrusted
58           The source repostory is not trusted, all objects are copied (not
59           hardlinked) and all checksums are verified.
60
61       -s, --subject=SUBJECT
62           One line subject for the commit message. If not specified, will be
63           taken from the source commit.
64
65       -b, --body=BODY
66           Full description for the commit message. If not specified, will be
67           taken from the source commit.
68
69       --update-appstream
70           Update the appstream branch after the build.
71
72       --no-update-summary
73           Don't update the summary file after the new commit is added. This
74           means the repository will not be useful for serving over http until
75           build-update-repo has been run. This is useful is you want to do
76           multiple repo operations before finally updating the summary.
77
78       --force
79           Create new commit even if the content didn't change from the
80           existing branch head.
81
82       --disable-fsync
83           Don't fsync when writing to the repository. This can result in data
84           loss in exceptional situations, but can improve performance when
85           working with temporary or test repositories.
86
87       --gpg-sign=KEYID
88           Sign the commit with this GPG key. This option can be used multiple
89           times.
90
91       --gpg-homedir=PATH
92           GPG Homedir to use when looking for keyrings
93
94       --end-of-life=REASON
95           Mark build as end-of-life
96
97       --end-of-life-rebase=OLDID=NEWID
98           Mark new refs as end-of-life. Unlike --end-of-life, this one takes
99           an ID that supersedes the current one. By the user's request, the
100           application data may be preserved for the new application. Note,
101           this is actually a prefix match, so if you say
102           org.the.app=org.new.app, then something like org.the.app.Locale
103           will be rebased to org.new.app.Locale.
104
105       --timestamp=TIMESTAMP
106           Override the timestamp of the commit. Use an ISO 8601 formatted
107           date, or NOW for the current time
108
109       --disable-fsync
110           Don't fsync when writing to the repository. This can result in data
111           loss in exceptional situations, but can improve performance when
112           working with temporary or test repositories.
113
114       -v, --verbose
115           Print debug information during command processing.
116
117       --ostree-verbose
118           Print OSTree debug information during command processing.
119

EXAMPLES

121       To revert a commit to the commit before:
122
123       $ flatpak build-commit-from --timestamp=NOW
124       --src-ref=app/org.gnome.gedit/x86_64/master^ repo
125       app/org.gnome.gedit/x86_64/master
126

SEE ALSO

128       ostree(1), flatpak(1), flatpak-build-init(1), flatpak-build(1),
129       flatpak-build-finish(1), flatpak-build-sign(1), flatpak-build-update-
130       repo(1)
131
132
133
134flatpak                                                 FLATPAK BUILD-COMMI(1)
Impressum