This is the error I'm having when I try to get a repository who lacks
some pristine files:
darcs failed: Couldn't fetch
in subdir pristine.hashed from sources:
There are two problems with that:
- this is really unfriendly, the user does not know what is a pristine
file and why it is useful. The hash is scary.
- this suggests that getting the repository is impossible, but that's
not true! darcs get *could* work around it by proposing the user to get
the patches and reconstruct the pristine tree afterwards.
So I propose this interface when a "missing pristine file" problem
Darcs tried to fetch a file from the _darcs/pristine.hashed/ remote
directory of could not find it.
This file is called:
Maybe you should report this problem to the repository owner, and tell
them to run ``darcs repair`` on their repository. Also, check for file
permissions, maybe the file is here but is just unreadable.
This makes lazy getting impossible, so getting the repository is going
to be slower but still possible. Do you want to do that? [Y/n]
Or maybe darcs should try to read again the ``hashed_inventory`` file
and detect whether a ``record`` has been made in the meantine, and start
getting again if yes. If not, go back to "failsafe get" as proposed