bzr check help out of date / confusing output
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Low
|
Unassigned |
Bug Description
Mats writes:
Seems like the help text for "check" has gone a bit out of sync with
what the command is doing. As can be seen below, the "Output fields"
claimed in help don't match what the command now (0.92) reports.
I'm not quite sure what to make of this information, either.
25 inconsistent parents? not referenced by their inventory?
$ bzr help check
Purpose: Validate consistency of branch history.
Usage: bzr check [BRANCH]
Options:
-v, --verbose Display more information.
-q, --quiet Only display errors and warnings.
-h, --help Show help message.
Description:
This command checks various invariants about the branch storage to
detect data corruption or bzr bugs.
Output fields:
revisions: This is just the number of revisions checked. It doesn't
indicate a problem.
versionedf
doesn't indicate a problem.
unreferenced ancestors: Texts that are ancestors of other texts, but
are not properly referenced by the revision ancestry. This is a
subtle problem that Bazaar can work around.
unique file texts: This is the total number of unique file contents
seen in the checked revisions. It does not indicate a problem.
repeated file texts: This is the total number of repeated texts seen
in the checked revisions. Texts can be repeated when their file
entries are modified, but the file contents are not. It does not
indicate a problem.
See also: reconcile
$ bzr check
checked branch ///home/
5
checked repository <bzrlib.
url=///
14 revisions
5 file-ids
40 unique file texts
25 repeated file texts
0 unreferenced text ancestors
25 inconsistent parents
25 file versions are not referenced by their inventory
$
Changed in bzr: | |
importance: | Undecided → Low |
status: | New → Confirmed |
tags: | added: check-for-breezy |