"bzr: ERROR: exceptions.KeyError" during update on svn lightweight checkout

Bug #250913 reported by Wesley J. Landaker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Bazaar Subversion Plugin
Fix Released
Medium
Jelmer Vernooij

Bug Description

When doing an update in a lightweight checkout, I get a KeyError. This is different than #190843, but might have a similar fix.

This is with the very latest bzr.dev and bzr-svn updated a few minutes ago:

$ bzr up
Initialising Subversion metadata cache in /home/wjlanda/.bazaar/svn-cache-exp/5f0b351c-ae82-3948-9ce8-fa6e1d16e4f9
using experimental bzr-svn mappings; output may change between revisions
bzr: ERROR: exceptions.KeyError: u'src/examples/flash/spi_read.cpp'

Traceback (most recent call last):
  File "/home/wjlanda/lib/python/bzrlib/commands.py", line 857, in run_bzr_catch_errors
    return run_bzr(argv)
  File "/home/wjlanda/lib/python/bzrlib/commands.py", line 797, in run_bzr
    ret = run(*run_argv)
  File "/home/wjlanda/lib/python/bzrlib/commands.py", line 499, in run_argv_aliases
    return self.run(**all_cmd_args)
  File "/home/wjlanda/lib/python/bzrlib/builtins.py", line 991, in run
    tree = WorkingTree.open_containing(dir)[0]
  File "/home/wjlanda/lib/python/bzrlib/workingtree.py", line 327, in open_containing
    return control.open_workingtree(), relpath
  File "/home/wjlanda/.bazaar/plugins/svn/workingtree.py", line 804, in open_workingtree
    return SvnWorkingTree(self, self.local_path, self.open_branch())
  File "/home/wjlanda/.bazaar/plugins/svn/workingtree.py", line 101, in __init__
    self.base_tree = SvnBasisTree(self)
  File "/home/wjlanda/.bazaar/plugins/svn/tree.py", line 233, in __init__
    workingtree.branch.mapping)
  File "/home/wjlanda/.bazaar/plugins/svn/repository.py", line 352, in get_fileid_map
    return self.fileid_map.get_map(self.uuid, revnum, path, mapping)
  File "/home/wjlanda/.bazaar/plugins/svn/fileids.py", line 297, in get_map
    self.actual.update_map(map, revid, idmap, changes)
  File "/home/wjlanda/.bazaar/plugins/svn/fileids.py", line 193, in update_map
    del map[x]
KeyError: u'src/examples/flash/spi_read.cpp'

bzr 1.6b4 on python 2.5.2 (linux2)
arguments: ['/home/wjlanda/bin/bzr', 'up']
encoding: 'UTF-8', fsenc: 'UTF-8', lang: 'en_US.UTF-8'
plugins:
  bisect /home/wjlanda/.bazaar/plugins/bisect [1.1.0pre0]
  bzrtools /usr/lib/python2.5/site-packages/bzrlib/plugins/bzrtools [1.5.0]
  cvsps /home/wjlanda/.bazaar/plugins/cvsps [unknown]
  gtk /home/wjlanda/.bazaar/plugins/gtk [0.95.0dev1]
  launchpad /home/wjlanda/lib/python/bzrlib/plugins/launchpad [unknown]
  loom /home/wjlanda/.bazaar/plugins/loom [1.4.0dev0]
  rebase /home/wjlanda/.bazaar/plugins/rebase [0.4.0dev0]
  stats /home/wjlanda/.bazaar/plugins/stats [unknown]
  svn /home/wjlanda/.bazaar/plugins/svn [0.4.11exp0]
  update_mirrors /home/wjlanda/.bazaar/plugins/update_mirrors [unknown]
*** 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.

Revision history for this message
Jelmer Vernooij (jelmer) wrote : Re: [Bug 250913] [NEW] "bzr: ERROR: exceptions.KeyError" during update on svn lightweight checkout

 milestone 0.4.11
 status confirmed

There's already a test in the testsuite for this.

Changed in bzr-svn:
milestone: none → 0.4.11
status: New → Confirmed
Revision history for this message
Jelmer Vernooij (jelmer) wrote :

Fixed committed to the 0.4 branch. Please reopen if you can still reproduce this with your branch.

Changed in bzr-svn:
assignee: nobody → jelmer
status: Confirmed → Fix Committed
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
importance: Undecided → Medium
Jelmer Vernooij (jelmer)
Changed in bzr-svn:
status: Fix Committed → Fix Released
Revision history for this message
Wesley J. Landaker (wjl) wrote :

Everything seems fine in the repository where I original saw this error. I'm not seeing it anymore with bzr 1.9 and bzr 0.4.15.

But I reported a different one in #304134 that affects a different repository! =)

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.