Problem with log on specified directory using bzr.dev

[Neil Martinsen-Burrell]

I'm getting the following traceback with my newly pulled version of bzr.dev:

nmb at guttle[~/src/bzr/bzr.dev]$ bzr log -r 3365 bzrlib
bzr: ERROR: exceptions.KeyError:
'john at arbash-meinel.com-20050711051006-2d11704675600e95'

Traceback (most recent call last):
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/commands.py", line 846, in
run_bzr_catch_errors
    return run_bzr(argv)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/commands.py", line 802, in run_bzr
    ret = run(*run_argv)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/commands.py", line 504, in
run_argv_aliases
    return self.run(**all_cmd_args)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/commands.py", line 812, in ignore_pipe
    result = func(*args, **kwargs)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/builtins.py", line 1791, in run
    limit=limit)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/log.py", line 185, in show_log
    start_revision, end_revision, search, limit)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/log.py", line 215, in _show_log
    allow_single_merge_revision)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/log.py", line 282, in
calculate_view_revisions
    view_revisions)
  File "/Users/nmb/src/bzr/bzr.dev/bzrlib/log.py", line 482, in
_filter_revisions_touching_file_id
    rev_ancestry = rev_ancestry.union(ancestry[parent])
KeyError: 'john at arbash-meinel.com-20050711051006-2d11704675600e95'

bzr 1.4dev on python 2.5.1 (darwin)
arguments: ['/Users/nmb/usr/bin/bzr', 'log', '-r', '3365', 'bzrlib']
encoding: 'US-ASCII', fsenc: 'utf-8', lang: None
plugins:
  bzr_xmloutput        /Users/nmb/.bazaar/plugins/bzr_xmloutput [0.4.0]
  latex_version_info   /Users/nmb/.bazaar/plugins/latex_version_info [0.0.2]
  launchpad            /Users/nmb/src/bzr/bzr.dev/bzrlib/plugins/launchpad [unknown]
  multiparent          /Users/nmb/src/bzr/bzr.dev/bzrlib/plugins/multiparent.pyc
[unknown]
  qbzr                 /Users/nmb/.bazaar/plugins/qbzr [0.8.0]
*** 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.

``bzr log -r 3365`` in the branch works fine:

nmb at guttle[~/src/bzr/bzr.dev]$ bzr log -r 3365
------------------------------------------------------------
revno: 3365
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: +trunk
timestamp: Sun 2008-04-13 20:44:29 +0100
message:
  Use mail-user-agent for Emacs mail clients (xma)
    ------------------------------------------------------------
    revno: 3364.1.2
    committer: Aaron Bentley <aaron at aaronbentley.com>
    branch nick: bzr.ab.integration
    timestamp: Sun 2008-04-13 13:41:14 -0400
    message:
      Update NEWS for 1.5 cycle
    ------------------------------------------------------------
    revno: 3364.1.1
    committer: Aaron Bentley <aaron at aaronbentley.com>
    branch nick: bzr.ab.integration
    timestamp: Sun 2008-04-13 13:38:34 -0400
    message:
      Merge Emacs mail-user-agent patch
    ------------------------------------------------------------
    revno: 3324.4.1
    committer: Xavier Maillard <xma at gnu.org>
    branch nick: xma-emacsclient
    timestamp: Sun 2008-04-13 13:48:00 +0200
    message:
      Replace mail-mode call with compose-mail from GNU Emacs.
      
      This patch is a modified version of the current revno 3323.
      
      It overloads it by:
      
      1. defining a different python class EmacsMail "MUA agnostic".
      
         To use this option, just put these lines into ~/.bazaar/bazaar.conf
          
      [DEFAULT]
      mail_client = emacsclient
      
      2. supporting any mail client of GNU Emacs family (mail-mode,
         message-mode, ...) The right tool will be called according to the
         value of the variable ``mail-user-agent``. So Virtually any Emacs
         mail client will work transparently if registered against
         ``mail-user-agent``.
      
      3. adding a wrapper function around MIME attachment. This allow us not
         to have many different functions/classes to attach a file but one.
      
      4. tests have been updated to follow the changes.

Did something change recently that broke this or should I not do ``bzr log`` on
directories where nothing changed in that revision?