'bzr rm' leaves directories behind?

[Marius Kruger]

Hi,

The is a bug out: [bzr rm should remove clean subtrees], which is
similar if not the same as your problem:
https://bugs.launchpad.net/bzr/+bug/111665

I have done some work on fixing this,
but am awaiting feedback on a patch which fixes a related and IMO more
serious bug, before continuing.
(http://bundlebuggy.aaronbentley.com/request/%3C418c22640705062115x34c0f1fcl91c82a9d2d0659fb@mail.gmail.com%3E)
I submitted a patch for this on 02 May 2007, but nobody has bothered
to review this.

regards
marius


On 6/15/07, Sebastian Kuzminsky <seb at highlab.com> wrote:
> Hi folks, looks like 'bzr rm' removed files but leaves directories behind
> when asked to remove a subtree.  This behavior contradicts the manpage.
> Bug?
>
>
> 0 seb at dub /home/seb>  bzr init bzr-rm-test
>
> 0 seb at dub /home/seb>  cd bzr-rm-test/
>
> 0 seb at dub /home/seb/bzr-rm-test>  mkdir dir{1,2}{,/subdir{1,2,3}}
>
> 0 seb at dub /home/seb/bzr-rm-test>  touch dir{1,2}{,/subdir{1,2,3}}/file
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr add dir?
> added dir1
> added dir2
> added dir1/file
> added dir1/subdir1
> added dir1/subdir2
> added dir1/subdir3
> added dir2/file
> added dir2/subdir1
> added dir2/subdir2
> added dir2/subdir3
> added dir1/subdir1/file
> added dir1/subdir2/file
> added dir1/subdir3/file
> added dir2/subdir1/file
> added dir2/subdir2/file
> added dir2/subdir3/file
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr commit -m 'some dir structure'
> added dir1
> added dir1/file
> added dir1/subdir1
> added dir1/subdir1/file
> added dir1/subdir2
> added dir1/subdir2/file
> added dir1/subdir3
> added dir1/subdir3/file
> added dir2
> added dir2/file
> added dir2/subdir1
> added dir2/subdir1/file
> added dir2/subdir2
> added dir2/subdir2/file
> added dir2/subdir3
> added dir2/subdir3/file
> Committed revision 1.
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr rm dir1
> deleted dir1/subdir3/file
> deleted dir1/subdir2/file
> deleted dir1/subdir1/file
> deleted dir1/file
> dir1 is not empty directory and won't be deleted.
>
> 0 seb at dub /home/seb/bzr-rm-test>  find dir1
> dir1
> dir1/subdir1
> dir1/subdir2
> dir1/subdir3
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr st
> removed:
>   dir1/
>   dir1/file
>   dir1/subdir1/
>   dir1/subdir1/file
>   dir1/subdir2/
>   dir1/subdir2/file
>   dir1/subdir3/
>   dir1/subdir3/file
> unknown:
>   dir1/
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr commit -m 'tried to remove a subtree'
> deleted dir1
> deleted dir1/file
> deleted dir1/subdir1
> deleted dir1/subdir1/file
> deleted dir1/subdir2
> deleted dir1/subdir2/file
> deleted dir1/subdir3
> deleted dir1/subdir3/file
> Committed revision 2.
>
> 0 seb at dub /home/seb/bzr-rm-test>  bzr st
> unknown:
>   dir1/
>
> 0 seb at dub /home/seb/bzr-rm-test>  find dir1
> dir1
> dir1/subdir1
> dir1/subdir2
> dir1/subdir3
>
> 0 seb at dub /home/seb/bzr-rm-test>
>
> --
> Sebastian Kuzminsky
> "We're building a machine that will be proud of us."
> -- Danny Hillis, Thinking Machines Corporation, 1982
>
>



-- 
bazaar-vcs.org
Because I don't trust Version Control Systems with less than 6350 unit tests.