flatpak build-commit-fromflatpakDeveloperAlexanderLarssonalexl@redhat.comflatpak build-commit-from1flatpak-build-commit-fromCreate new commits based on existing one (possibly from another repository)flatpak build-commit-fromOPTIONDST-REPODST-REFDescription
Creates new commits on the DST-REF
branch in the DST-REPO, with the
contents (and most of the metadata) taken from another
branch, either from another repo, or from another branch in
the same repository.
The collection ID set on
DST-REPO (if set) will be used for the
newly created commits.
This command is very useful when you want to maintain a branch
with a clean history that has no unsigned or broken commits.
For instance, you can import the head from a different repository
from an automatic builder when you've verified that it worked.
The new commit will have no parents or signatures from the
autobuilder, and can be properly signed with the official
key.
Any deltas that affect the original commit and that match parent
commits in the destination repository are copied and rewritten
for the new commit id.
OptionsThe following options are understood:
Show help options and exit.
The (local) repository to pull the source branch from. Defaults to the
destination repository.
The branch to use as the source for the new commit. Defaults to the same
as the destination ref, which is useful only if a different source repo
has been specified.
Add an extra collection-ref binding for this collection, in addition to whatever
would normally be added due to the destination repository collection id.
This option can be used multiple times.
The source repostory is not trusted, all objects are copied (not hardlinked) and
all checksums are verified.
One line subject for the commit message. If not specified, will be taken from the source commit.
Full description for the commit message. If not specified, will be taken from the source commit.
Update the appstream branch after the build.
Don't update the summary file after the new commit is added. This means
the repository will not be useful for serving over http until build-update-repo
has been run. This is useful is you want to do multiple repo operations before
finally updating the summary.
Create new commit even if the content didn't change from the existing branch head.
Don't fsync when writing to the repository. This can result in data loss in exceptional situations, but can improve performance when
working with temporary or test repositories.
Sign the commit with this GPG key.
This option can be used multiple times.
GPG Homedir to use when looking for keyrings
Mark build as end-of-life
Mark new refs as end-of-life. Unlike ,
this one takes an ID that supercedes the current one. By the user's
request, the application data may be preserved for the new application.
Note, this is actually a prefix match, so if you say org.the.app=org.new.app,
then something like org.the.app.Locale will be rebased to org.new.app.Locale.
Override the timestamp of the commit. Use an ISO 8601 formatted
date, or NOW for the current time
Don't fsync when writing to the repository. This can result in data loss in exceptional situations, but can improve performance when
working with temporary or test repositories.
Print debug information during command processing.
Print OSTree debug information during command processing.
Examples
To revert a commit to the commit before:
$ flatpak build-commit-from --timestamp=NOW --src-ref=app/org.gnome.gedit/x86_64/master^ repo app/org.gnome.gedit/x86_64/masterSee alsoostree1,
flatpak1,
flatpak-build-init1,
flatpak-build1,
flatpak-build-finish1,
flatpak-build-sign1,
flatpak-build-update-repo1