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 --untrusted
47 The source repostory is not trusted, all objects are copied (not
48 hardlinked) and all checksums are verified.
49
50 -s, --subject=SUBJECT
51 One line subject for the commit message. If not specified, will be
52 taken from the source commit.
53
54 -b, --body=BODY
55 Full description for the commit message. If not specified, will be
56 taken from the source commit.
57
58 --update-appstream
59 Update the appstream branch after the build.
60
61 --no-update-summary
62 Don't update the summary file after the new commit is added. This
63 means the repository will not be useful for serving over http until
64 build-update-repo has been run. This is useful is you want to do
65 multiple repo operations before finally updating the summary.
66
67 --force
68 Create new commit even if the content didn't change from the
69 existing branch head.
70
71 --disable-fsync
72 Don't fsync when writing to the repository. This can result in data
73 loss in exceptional situations, but can improve performance when
74 working with temporary or test repositories.
75
76 --gpg-sign=KEYID
77 Sign the commit with this GPG key. This option can be used multiple
78 times.
79
80 --gpg-homedir=PATH
81 GPG Homedir to use when looking for keyrings
82
83 -v, --verbose
84 Print debug information during command processing.
85
86 --ostree-verbose
87 Print OSTree debug information during command processing.
88
90 To revert a commit to the commit before:
91
92 $ flatpak build-commit-from --timestamp=NOW
93 --src-ref=app/org.gnome.gedit/x86_64/master^ repo
94 app/org.gnome.gedit/x86_64/master
95
97 ostree(1), flatpak(1), flatpak-build-init(1), flatpak-build(1),
98 flatpak-build-finish(1), flatpak-build-sign(1), flatpak-build-update-
99 repo(1)
100
101
102
103flatpak FLATPAK BUILD-COMMI(1)