Comment 6 for bug 350615

Revision history for this message
Andrew Johnson (anj) wrote : Re: Loggerhead generates bad link then writes Exception in place of filename

The instructions in the original report don't seem to work now, but I'm seeing this exception in my project at http://bazaar.launchpad.net/~epics-core/epics-base/3.14/changes?filter_file_id=recaai.c-19941025185436-63xdujwxw18vn1oh-1 which shows the log of a file that was deleted from the epics-base repository as part of a rename (from recAai.c to aaiRecord.c) done using the CVS delete + add technique long before the Bazaar conversion.

I am trying to follow the file's history through the rename. Using loggerhead I find the revision where it was added with the new name http://bazaar.launchpad.net/~epics-core/epics-base/3.14/revision/1997 Then click "Older" and "browse files at revision 1996" at which point I have to click through the directory hierarchy to find the file with its old name. That takes me to http://bazaar.launchpad.net/~epics-core/epics-base/3.14/files/1996/src/rec/?start_revid=12049 where I click the file recAai.c and then "View changes to this file."

The line which should contain the filename actually says this:

~epics-core/epics-base/3.14 : changes to Exception: The file id "recaai.c-19941025185436-63xdujwxw18vn1oh-1" is not present in the tree <bzrlib.inventory.CHKInventory object at 0x11a6eed0>. from revision 12049