Possible bug with removing files?

[Martin Pool]

On 9/3/07, Andrew King <eurokang at gmail.com> wrote:
> Hi,
>
> Someone complained that a file is missing from our repository. I am
> not sure if I have found a bug or not ...
>
> (aside ... is it desired behaviour that doing bzr log "myRemovedFile"
> gives no information? It is very very difficult to find out which
> revision caused a missing file).
>
> Eventually, after doing bzr diff down numerous revisions, I found a
> place where the file got removed ...
>
> bzr diff -r886.1.62..862.1.114.1.74.1.38.1.9 | grep myFileName
>
> shows file missing
>
> === removed file 'myFileName'
> --- myFileName  2007-08-28 03:59:02 +0000
> +++ myFileName  1970-01-01 00:00:00 +0000
> @@ -1,51 +0,0 @@
>

I assume the removed lines were shown here and you just omitted them
for privacy/length (which is fine)?

> However,
>
> bzr log -v -r886.1.62..862.1.114.1.74.1.38.1.9 | grep myFileName
>
> does not return anything! In other words, diff shows the file being
> removed without any commit in that area removing the file?!
>
> Can anyone explain this please, or help me fix it?

That is surprising.  A good start for fixing it would be trying to
write a smaller reproduction, either as a shell script or as a bzr
test.  My guess is that this is happening because the removal is
attributed to a merge back towards the mainline, and you'll need it to
be deleted on a merged-in revision to see this happen.

-- 
Martin