ghost revs/inconsistent parents/missing revs in bzr check

[Jelmer Vernooij]

Hi Tom,


Tom Cato Amundsen wrote:
> It can get worse. I also have problems with branching other than the
> head of the branch. I have to checkout -r revno, then convert to a
> branch.
>   
Isn't that just a specific bug in Bazaar related to ghosts? This sort of
thing shouldn't be a problem in general with ghosts AFAIU. It also seems
somewhat specific to your situation; I have several branches with
ghosts, and none of them has had this problem.

Cheers,

Jelmer
> My repo was converter from baz:
>
> tom at tomsin-laptop:~/src/solfege.dev$ bzr check
> Checking working tree at 'file:///home/tom/src/solfege.dev/'.
> Checking repository at 'file:///home/tom/src/solfege.repo/'.
> checked repository <bzrlib.transport.local.LocalTransport
> url=file:///home/tom/src/solfege.repo/> format
> <RepositoryFormatKnitPack1>
>   1429 revisions
>   1451 file-ids
>   7550 unique file texts
> 1432846 repeated file texts
>      0 unreferenced text versions
>      3 ghost revisions
>      3 revisions missing parents in ancestry
>    814 inconsistent parents
> Checking branch at 'file:///home/tom/src/solfege.repo/solfege.dev/'.
> bzr: ERROR: exceptions.KeyError:
> 'Arch-1:tca at gnu.org--solfege-2005%solfege--unstable--3.1--version-0'
>
> Traceback (most recent call last):
>   File "/home/tom/lib/python/bzrlib/commands.py", line 716, in
> exception_to_return_code
>     return the_callable(*args, **kwargs)
>   File "/home/tom/lib/python/bzrlib/commands.py", line 911, in run_bzr
>     ret = run(*run_argv)
>   File "/home/tom/lib/python/bzrlib/commands.py", line 547, in run_argv_aliases
>     return self.run(**all_cmd_args)
>   File "/home/tom/lib/python/bzrlib/builtins.py", line 2867, in run
>     check_dwim(path, verbose, do_branch=branch, do_repo=repo, do_tree=tree)
>   File "/home/tom/lib/python/bzrlib/check.py", line 317, in check_dwim
>     check_branch(branch, verbose)
>   File "/home/tom/lib/python/bzrlib/check.py", line 272, in check_branch
>     branch_result = branch.check()
>   File "/home/tom/lib/python/bzrlib/decorators.py", line 138, in read_locked
>     result = unbound(self, *args, **kwargs)
>   File "/home/tom/lib/python/bzrlib/branch.py", line 1017, in check
>     last_revision_id))
>   File "/home/tom/lib/python/bzrlib/repository.py", line 1800, in
> iter_reverse_revision_history
>     parents = graph.get_parent_map([next_id])[next_id]
> KeyError: 'Arch-1:tca at gnu.org--solfege-2005%solfege--unstable--3.1--version-0'
>
> bzr 1.13.1 on python 2.5.2 (linux2)
> arguments: ['/home/tom/bin/bzr', 'check']
> encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'nb_NO.UTF-8'
> plugins:
>   cia                  /home/tom/.bazaar/plugins/cia [1.0dev]
>   launchpad            /home/tom/lib/python/bzrlib/plugins/launchpad [unknown]
>   netrc_credential_store
> /home/tom/lib/python/bzrlib/plugins/netrc_credential_store [unknown]
>   upload               /home/tom/.bazaar/plugins/upload [1.0dev]
> *** Bazaar has encountered an internal error.
>     Please report a bug at https://bugs.launchpad.net/bzr/+filebug
>     including this traceback, and a description of what you
>     were doing when the error occurred.
> tom at tomsin-laptop:~/src/solfege.dev$
>
>
> On Tue, Apr 7, 2009 at 3:15 PM, Jelmer Vernooij <jelmer at vernstok.nl> wrote:
>   
>> Parth Malwankar wrote:
>>     
>>> Hello,
>>>
>>> I just ran "bzr check" on a branch I am using. This
>>> gave the following numbers.
>>>
>>>   1497 revisions
>>>   3260 file-ids
>>>   7318 unique file texts
>>> 942118 repeated file texts
>>>      0 unreferenced text versions
>>>    122 ghost revisions
>>>    122 revisions missing parents in ancestry
>>>     55 inconsistent parents
>>>
>>> If I understand "bzr check help" correctly, I need
>>> not worry about the first 5.
>>>
>>> Should I be concerned about the last 3?
>>>
>>> What are ghost revisions? I couldn't find any info on
>>> it (might have missed it).
>>>
>>> I am using bzr 1.13 (format 1.9-rich-root).
>>>
>>>       
>> Ghost revisions are revisions to which references exist, but which don't
>> actually exist in your repository. They are usually created by imports
>> from baz or Subversion and generally shouldn't be a problem, unless of
>> course you expected to have all revisions in your repository.
>>
>> Cheers,
>>
>> Jelmer
>>
>>
>>     
>
>
>
>