Assertion failure after renaming and deleting

Andrew King eurokang at gmail.com
Wed Jun 27 14:28:05 BST 2007


I have just hit a similar looking assertion under windows using 0.17
... did the fix mentioned above make it into 0.17?

Cheers,
Andrew

On 6/8/07, John Arbash Meinel <john at arbash-meinel.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Weeble wrote:
> > I reported what I think was the same problem earlier today, but I used
> > a different email address and it got postponed for moderation. I have
> > attempted to reproduce the bug with a minimal number of steps. Working
> > in Windows, the following batch file exhibits the problem:
> >
>
> I can reproduce this with bzr 0.16, but it seems to be fixed in bzr.dev:
>
> This is my test script:
>
> #!/bin/sh -xe
> BZR=bzr
> DIR1=spam
> DIR2=eggs
> FILE1=foo
> FILE2=bar
>
> $BZR init test
> cd test
>
> mkdir $DIR1
> echo "foo" > $DIR1/$FILE1
>
> $BZR add
> $BZR commit -m "first"
>
> cd $DIR1
> $BZR rename $FILE1 $FILE2
> rm $FILE2
>
> cd ..
> $BZR rename $DIR1 $DIR2
>
> $BZR status
>
> $BZR commit -m "2"
>
>
>
> Actually, I can think of 2 reasons for this, but if you change the "rm $FILE2"
> to "bzr rm --force $FILE2" the issue goes away.
>
> The bug has to do with how the "bzr rename" command worked when renaming the
> entire directory.
>
> I can see that it does indeed end up with an extra record which shouldn't be there.
>
> John
> =:->
>
> John
> =:->
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.7 (Darwin)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
>
> iD8DBQFGaWcbJdeBCYSNAAMRAkDJAKCiQgchnpYbwHcniqfl6vo2E3RH4ACgnpi2
> LzbklsxxEVnUYC6jPwEv8hE=
> =MAzb
> -----END PGP SIGNATURE-----
>
>



More information about the bazaar mailing list