On Mon, Jan 05, 2009 at 13:46:26 +1100, S. Günther wrote: > yes, I did receive the response, I just didn't have time to > try to reproduce the error during the weekend. > I tried today and wasn't able to. As I explained before > pulling into a fresh repository fixed the error. Even worse, > creating a tarball and working in a copy of the old repository > didn't reproduce the error, too. That made me suspicious and > it turns out that I don't even get the error in the repo which > was the offending one to start with. And I swear I didn't touch > it. > So I think there really must have been something messed up > on my box and I'm incredibly sorry for the unnecessary noise.
No problem! (I didn't see your name in the CC list, which is why I asked) It's possible that darcs did something wrong, although I sure hope it didn'!. For what it's worth, it's taken us a while to get a handle on the case sensitivity situation (gsom, Gsom). The best thing you can do to avoid trouble is to use a hashed format, either --hashed (which is the darcs 1 hashed format) or --darcs-2 (the darcs 2 format is always hashed). This uses internal filenames in the pristine cache and keeps an index mapping the internal filenames to their expected external filenames... much more robust than trusting the filesystem. -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
