bzr: ERROR: bzrlib.errors.BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing chk node(s) for id_to_entry maps

Bug #884449 reported by Jean-Paul Calderone
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
New
Undecided
Unassigned

Bug Description

bzr: ERROR: bzrlib.errors.BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing chk node(s) for id_to_entry maps

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 946, in exception_to_return_code
  File "bzrlib\commands.pyo", line 1150, in run_bzr
  File "bzrlib\commands.pyo", line 699, in run_argv_aliases
  File "bzrlib\commands.pyo", line 721, in run
  File "bzrlib\cleanup.pyo", line 135, in run_simple
  File "bzrlib\cleanup.pyo", line 165, in _do_with_cleanups
  File "bzrlib\builtins.pyo", line 1408, in run
  File "bzrlib\branch.pyo", line 1450, in create_checkout
  File "bzrlib\branch.pyo", line 1109, in pull
  File "bzrlib\decorators.pyo", line 217, in write_locked
  File "bzrlib\branch.pyo", line 3376, in pull
  File "bzrlib\branch.pyo", line 3506, in _pull
  File "bzrlib\decorators.pyo", line 217, in write_locked
  File "bzrlib\branch.pyo", line 3319, in _update_revisions
  File "bzrlib\decorators.pyo", line 217, in write_locked
  File "bzrlib\branch.pyo", line 3296, in fetch
  File "bzrlib\repository.pyo", line 724, in fetch
  File "bzrlib\decorators.pyo", line 217, in write_locked
  File "bzrlib\vf_repository.pyo", line 2499, in fetch
  File "bzrlib\fetch.pyo", line 75, in __init__
  File "bzrlib\fetch.pyo", line 102, in __fetch
  File "bzrlib\fetch.pyo", line 136, in _fetch_everything_for_search
  File "bzrlib\vf_repository.pyo", line 1970, in insert_stream
  File "bzrlib\repository.pyo", line 641, in commit_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 1711, in _commit_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 1591, in _commit_write_group
BzrCheckError: Internal check failed: Cannot add revision(s) to repository: missing chk node(s) for id_to_entry maps

bzr 2.4.1 on python 2.6.6 (Windows-XP-5.1.2600-SP3)
arguments: ['C:\\Program Files\\Bazaar\\bzr.EXE', 'checkout',
    'http://svn.twistedmatrix.com/bzr/Twisted//branches/iocp-win64-4669',
    'Twisted']
plugins: bzrtools[2.4.0], changelog_merge[2.4.1], colo[0.3.1dev],
    explorer[1.2.1], fastimport[0.12.0dev], launchpad[2.4.1], loom[2.2.1dev],
    netrc_credential_store[2.4.1], news_merge[2.4.1], pipeline[1.1.0],
    qbzr[0.21.1], rewrite[0.6.3dev], svn[1.1.0], upload[1.0.1dev],
    xmloutput[0.8.7]
encoding: 'cp1252', fsenc: 'mbcs', lang: None

*** Bazaar has encountered an internal error. This probably indicates a
    bug in Bazaar. You can help us fix it by filing a bug report at
        https://bugs.launchpad.net/bzr/+filebug
    including this traceback and a description of the problem.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

I can clone this branch fine with current versions of bzr-svn. Are you cloning into an existing repository (with revisions made with older versions of bzr-svn affected by bug 485601)?

affects: bzr → bzr-svn
Revision history for this message
Jean-Paul Calderone (exarkun) wrote :

Probably? I don't know how to check what version of bzr a repository was created with.

Revision history for this message
Jelmer Vernooij (jelmer) wrote :

20:24 < jelmer> now that bzr-svn passes all the main bzr tests I'm pretty sure it no longmer creates revisions with this issue
20:24 < jelmer> but there are probably still revisions out there in the wild that were created with older versions of bzr-svn
20:33 < jelmer> glyph: there are two things - 1) updating your mirror to have the right representation of those svn revisions (created with bzr-svn 1.1.1) will make sure you don't hit this bug, and 2) bzr should be able to cope with this situation (perhaps
                warn, because it is after all slightly different metadata) but not fail

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.