KeyError when running "bzr pull" or "bzr update" using bzr-svn

Bug #516202 reported by Scott Armitage
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar
New
Undecided
Unassigned

Bug Description

At work we have an SVN repository secured via SSH. I am familiar with Bazaar and its workflows, and so I am using a hybrid system of Bazaar locally and doing feature commits to the SVN repository.

Today I made a commit from one branch (which is a checkout of a subdirectory of the SVN repository), which worked. Later I tried to update my copy of //trunk/ (a separate bzr checkout) and got the following error message. This /may/ be related to bug 423015, but I do not know.

Version information:
-------------------------
PS H:\utias-sfl\vcs\svn-CanX4+5> bzr version
Bazaar (bzr) 2.0.4
  Python interpreter: C:\Program Files\Bazaar\python25.dll 2.5.4
  Python standard library: C:\Program Files\Bazaar\lib\library.zip
  Platform: Windows-XP-5.1.2600-SP3
  bzrlib: C:\Program Files\Bazaar\lib\library.zip\bzrlib
  Bazaar configuration: C:\Documents and Settings\sarmitage\Application Data\bazaar\2.0
  Bazaar log file: C:\Documents and Settings\sarmitage\My Documents\.bzr.log

Failure:
----------
PS H:\utias-sfl\vcs\svn-trunk> bzr pull
Using saved parent location: svn+ssh://sarmitage@<hostname>/usr2/svn/repos/trunk
bzr: ERROR: exceptions.KeyError: GraphIndex('file:///H:/utias-sfl/vcs/.bzr/repository/indices/c76ab0e7baf82dcd5c2c4b60b851bb5a.rix')

Traceback (most recent call last):
  File "bzrlib\commands.pyo", line 842, in exception_to_return_code
  File "bzrlib\commands.pyo", line 1037, in run_bzr
  File "bzrlib\commands.pyo", line 654, in run_argv_aliases
  File "bzrlib\builtins.pyo", line 1028, in run
  File "bzrlib\branch.pyo", line 2164, in unlock
  File "bzrlib\repofmt\pack_repo.pyo", line 2361, in unlock
  File "bzrlib\repository.pyo", line 944, in abort_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 2254, in _abort_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 2059, in _abort_write_group
  File "bzrlib\repofmt\pack_repo.pyo", line 1831, in _remove_pack_indices
  File "bzrlib\repofmt\pack_repo.pyo", line 654, in remove_index
KeyError: GraphIndex('file:///H:/utias-sfl/vcs/.bzr/repository/indices/c76ab0e7baf82dcd5c2c4b60b851bb5a.rix')

bzr 2.0.4 on python 2.5.4 (Windows-XP-5.1.2600-SP3)
arguments: ['C:\\Program Files\\Bazaar\\bzr.exe', 'pull']
encoding: 'cp1252', fsenc: 'mbcs', lang: None
plugins:
  bzrtools C:\Program Files\Bazaar\plugins\bzrtools [2.0.1]
  explorer C:\Program Files\Bazaar\plugins\explorer [0.8.3]
  launchpad C:\Program Files\Bazaar\plugins\launchpad [2.0.4]
  netrc_credential_store C:\Program Files\Bazaar\plugins\netrc_credential_store [2.0.4]
  qbzr C:\Program Files\Bazaar\plugins\qbzr [0.14.6]
  rebase C:\Program Files\Bazaar\plugins\rebase [0.5.4]
  svn C:\Program Files\Bazaar\plugins\svn [1.0.0]
  upload C:\Program Files\Bazaar\plugins\upload [1.0.0dev]
  xmloutput C:\Program Files\Bazaar\plugins\xmloutput [0.8.5]

*** 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.

Jelmer Vernooij (jelmer)
affects: bzr-svn → bzr
Revision history for this message
Martin Pool (mbp) wrote : Re: [Bug 516202] Re: KeyError when running "bzr pull" or "bzr update" using bzr-svn

May be a duplicate.

- Martin

On 03/02/2010 2:20 AM, "Jelmer Vernooij" <email address hidden> wrote:

** Project changed: bzr-svn => bzr

--
KeyError when running "bzr pull" or "bzr update" using bzr-svn
https://bugs.launchpad.net/bugs/...
You received this bug notification because you are a member of bzr-qa,

which is subscribed to Bazaar.

Revision history for this message
Scott Armitage (scott-armitage) wrote :

This error seems to happen more or less constantly for me. I can get around it using the command "bzr pull -r -1", which updates to the latest SVN revision without error.

Revision history for this message
Martin Pool (mbp) wrote :
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.