Hi all,
I'm looking for some advice about the following darcs behaviour. I
haven't found it reported in the issue tracker, but some issues seems
similar enough so that I'm wondering if I should report it.
$ darcs initialize
$ touch foo bar
$ darcs record -lam first
Finished recording patch 'first'
$ rm foo ; ln -s bar foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am second
No changes!
Note that it would succeed (record the file removal) if I used either
`darcs remove' or `darcs record -l'. Anyway this is only triggered by
the presence of the symbolic link:
$ rm foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am second
Finished recording patch 'second'
What really hurts is the case in which the link addresses a not-existent
file:
$ touch foo
$ darcs record -lam third
Finished recording patch 'third'
$ rm foo ; ln -s qux foo
$ darcs whatsnew -ls
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such
file or directory)
$ darcs record -am fourth
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such
file or directory)
$ darcs remove foo
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such
file or directory)
$ darcs record -lam fourth
darcs: /home/gpiero/tmp/darcs/repo/foo: openBinaryFile: does not exist (No such
file or directory)
The last two command would have 'fixed' the repository had the link
addressed an existent file. In this case however the only solution seems
to be removing the link:
$ rm foo
$ darcs whatsnew -ls
R ./foo
$ darcs record -am fourth
Finished recording patch 'fourth'
Any thoughts ? Is it someway expected (read: dependant on some already
reported issue) ?
Thanks,
Gian Piero.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
