Hello, Antoni Villalonga <frikimas...@gmail.com> writes: > Then, I try to repair it with a new darcs version: > $ darcs -v > 2.4.4 (release) <-- From Debian Sid > $ darcs check --debug-verbose > Beginning identifying repository . > Done identifying repository . > Identified darcs-1 repo: /path/to/code > Checking that patch names are unique... > Beginning reading inventory of repository /path/to/code > Done reading inventory of repository /path/to/code > Reading recorded state... > Applying patches... > Beginning reading inventory of repository /path/to/code > Done reading inventory of repository /path/to/code > Fixing any broken patches... > Beginning replaying patch > Beginning identifying repository . > Done identifying repository . > > darcs failed: No such file AnchoredPath [Name "app",Name "misc",Name > "file.php"]
This is likely a bogus rename patch. This is not hard to correct manually by editing the patches, although I do not recommend you to do that unless you really know what you are doing. I think that darcs will eventually grow a feature to repair such repositories automatically, since there are quite a few in the wild. In the meantime, you shouldn't need to worry too much about it. Unfortunately, you won't be able to do check or repair in the meantime. If you broke your repository today, restoring from the previous-day backup and re-recording any patches that are missing is the best course of action, I think. The alternative is to share the repo with us and we could look into repairing it. However, personally I won't have time until next week, since I am hiking over the weekend and leave tomorrow morning. :)) Yours, Petr. _______________________________________________ darcs-users mailing list darcs-users@darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users
