1FLATPAK BUILD-COMMI(1) flatpak build-commit-from FLATPAK BUILD-COMMI(1)
2
3
4
6 flatpak-build-commit-from - Create new commits based on existing one
7 (possibly from another repository)
8
10 flatpak build-commit-from [OPTION...] DST-REPO DST-REF...
11
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
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 --untrusted
52 The source repostory is not trusted, all objects are copied (not
53 hardlinked) and all checksums are verified.
54
55 -s, --subject=SUBJECT
56 One line subject for the commit message. If not specified, will be
57 taken from the source commit.
58
59 -b, --body=BODY
60 Full description for the commit message. If not specified, will be
61 taken from the source commit.
62
63 --update-appstream
64 Update the appstream branch after the build.
65
66 --no-update-summary
67 Don't update the summary file after the new commit is added. This
68 means the repository will not be useful for serving over http until
69 build-update-repo has been run. This is useful is you want to do
70 multiple repo operations before finally updating the summary.
71
72 --force
73 Create new commit even if the content didn't change from the
74 existing branch head.
75
76 --disable-fsync
77 Don't fsync when writing to the repository. This can result in data
78 loss in exceptional situations, but can improve performance when
79 working with temporary or test repositories.
80
81 --gpg-sign=KEYID
82 Sign the commit with this GPG key. This option can be used multiple
83 times.
84
85 --gpg-homedir=PATH
86 GPG Homedir to use when looking for keyrings
87
88 --end-of-life=REASON
89 Mark build as end-of-life
90
91 --timestamp=TIMESTAMP
92 Override the timestamp of the commit. Use an ISO 8601 formatted
93 date, or NOW for the current time
94
95 --disable-fsync
96 Don't fsync when writing to the repository. This can result in data
97 loss in exceptional situations, but can improve performance when
98 working with temporary or test repositories.
99
100 -v, --verbose
101 Print debug information during command processing.
102
103 --ostree-verbose
104 Print OSTree debug information during command processing.
105
107 To revert a commit to the commit before:
108
109 $ flatpak build-commit-from --timestamp=NOW
110 --src-ref=app/org.gnome.gedit/x86_64/master^ repo
111 app/org.gnome.gedit/x86_64/master
112
114 ostree(1), flatpak(1), flatpak-build-init(1), flatpak-build(1),
115 flatpak-build-finish(1), flatpak-build-sign(1), flatpak-build-update-
116 repo(1)
117
118
119
120flatpak FLATPAK BUILD-COMMI(1)