simonpj wrote: > darcs failed: user error (Error applying patch to working dir: > ./darcs-all-0: renameFile: permission denied (Permission > denied))
I've seen the same issue rather a lot, normally caused by a patch trying to update a locked binary, like an executable that's currently running. That's on Windows, of course.
It results in pristine (in _darcs) containing all of the pulled patches/changes but the working tree containing only the changes up to the failed one. I've generally found that unrecording back to the patch that failed to apply gives the closest thing to a correct state and doesn't lose the local changes.
The main caveat is that the patch that failed will have had some parts applied and some parts not. Also, if you don't know which patch caused the issue, then this doesn't help. You can normally guess, though, as the message does give a filename.
G. _______________________________________________ darcs-devel mailing list [email protected] http://www.abridgegame.org/cgi-bin/mailman/listinfo/darcs-devel
