Eric Kow <bugs@darcs.net> writes:
> +. lib # Load some portability helpers.
> +rm -rf R # Another script may have left a mess.
> +darcs init --repo R # Create our test repos.
> +
> +cd R
> +mkdir -p a
> +echo foo >a/b
> +darcs add -r a
> +darcs rec -am "add a/b"
> +rm -r a
> +darcs remove
darcs add without parameters works just as fine here... so this is
probably related to generic pending manipulation, not just darcs remove
Nevertheless, the pending that is created here is legal as far as I can
tell, so the bug is not this. To see what I mean, you can replace "rm -r
a; darcs remove" with just "darcs remove -r a" to obtain identical
pending.
> +darcs revert -a a/b
So this here triggers a sequence where "a/b" is attempted to be
reverted, which fails in the working copy as far as I can tell, since a/
does not exist anymore. Sneaking in "mkdir a" before the revert fixes
the problem, too...
The problem seems to be that something somewhere does not notice the
rmdir a/ patch and the fact it needs to be undone before the a/b patch
is...
Yours,
Petr.
|