bzr check reports about inconsistent parents. What this means?

Alexander Belchenko bialix at ukr.net
Thu Nov 15 12:07:55 GMT 2007


bzr 0.92

bzr init 1
cd 1
bzr mkdir bar
bzr ci -m 1
bzr check

checked branch file:///C:/work/Temp/1/ format Bazaar Branch Format 6 
(bzr 0.15)
checked repository <bzrlib.transport.local.LocalTransport 
url=file:///C:/work/Temp/1/> format <RepositoryFormatKnit1>
      1 revisions
      1 file-ids
      0 unique file texts
      0 repeated file texts
      0 unreferenced text ancestors

bzr mkdir foo
bzr ci -m 2
bzr check

checked branch file:///C:/work/Temp/1/ format Bazaar Branch Format 6 
(bzr 0.15)
checked repository <bzrlib.transport.local.LocalTransport 
url=file:///C:/work/Temp/1/> format <RepositoryFormatKnit1>
      2 revisions
      2 file-ids
      0 unique file texts
      0 repeated file texts
      0 unreferenced text ancestors
      1 inconsistent parents
      1 file versions are not referenced by their inventory

^-- something really wrong here. Why parents are inconsistent?
It's the fresh branch! What it means? Why file versions are
not versioned by their inventory? What kind of check 'bzr check' does?
How to interpeter their output? Help say nothing about this:

C:\work\Temp\1>bzr check -h
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.
       versionedfiles: This is just the number of versionedfiles 
checked.  It
           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


So, this messages say that history inconsistent? But if this branch is 
freshly minted, it means that bzr during commit destroy branch history?

Really-really weird.



More information about the bazaar mailing list