This adds an extra case to the function withSignalHandled of the module
Darcs.Signalhandler .
This function is responsible for catching exceptions and printing
"darcs failed" followed by the exception string.

I am not sure whether this is the best place to fix the problem, because
essentially the "error opening" comes from somewhere precise (a hashed-storage
function probably) and it would be more robust to attach this message earlier.

1 patch for repository http://darcs.net:

Mon Nov  1 15:53:24 CET 2010  Guillaume Hoffmann <guillaumh@gmail.com>
  * resolve issue1981 by inviting the user to run darcs repair when an exception related to pristin occurs

Attachments

• resolve-issue1981-by-inviting-the-user-to-run-darcs-repair-when-an-exception-related-to-pristin-occurs.dpatch
• unnamed

This sounds like an ersatz solution. Do you think you can come up with a 
cleaner solution, or should we apply this? Even if we can get the most 
detailed view of the path leading to the error, will we ever have better 
advice to offer.