packaging/ostree
1
0 Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

bin/fsck: Make ref binding verification optional

Browse Source 
Today the rpm-ostree test suite uses `refs --create` to save
commits.  I think this is a legitimate use case, and other
people may be doing something similar.

On the other hand, I think we should probably be changing the rpm-ostree test
suite to create "unbound" commits. But let's be maximially compatible here since
we hit a real-world case where something needed to change.

Closes: #1379
Approved by: pwithnall
This commit is contained in:
Colin Walters authored and Atomic Bot committed 2017-12-14 18:41:00 +00:00
1 parent 7935b881bf
commit d340fe4060
4 files changed
+35 -14
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

man/ostree-fsck.xml
+15 -5
View File
@@ -86,14 +86,24 @@ Boston, MA 02111-1307, USA.
</para></listitem>
</varlistentry>
<varlistentry>
<term><option>--verify-bindings</option></term>
<listitem><para>
Verify that the commits pointed to by each ref have that
ref in the binding set. You should usually add this
option; it only defaults to off for backwards compatibility.
</para></listitem>
</varlistentry>
<varlistentry>
<term><option>--verify-back-refs</option></term>
<listitem><para>
Verify that all the refs listed in a commit’s ref-bindings
point to that commit. This cannot be used in repositories
where the target of refs is changed over time as new commits
are added, but can be used in repositories which are
regenerated from scratch for each commit.
Verify that all the refs listed in a commit’s ref-bindings
point to that commit. This cannot be used in repositories
where the target of refs is changed over time as new commits
are added, but can be used in repositories which are
regenerated from scratch for each commit.
Implies <literal>--verify-bindings</literal> as well.
</para></listitem>
</varlistentry>
</variablelist>