Eric Kow <[EMAIL PROTECTED]> added the comment: Summarising: 1. darcs get fails because of case insensitivity on an old fashioned repository 2. getting a hashed copy of this works fine [I've tried] 3. surprisingly, darcs 1.0.9 succeeds in this case
Since hashed repositories work, I don't think it would be a good investment of our time trying to make the old-fashioned repositories work better. On the other hand, I do need a volunteer to investigate the following: Why does darcs 1.0.9 succeed here and 2.x fail? One path could be that 1.0.9 applies from the checkpoint and 2.x (presumably) tries to apply all patches. Why does it do this? Once we know the answer to this, I think we can close the bug. Interestingly, getting from hashed copy of the GHC repository is much faster because it allows for lazy fetching of patches (this is like partial repositories but a good deal more robust), and also lets you take advantage of the global cache. There should perhaps be a hashed mirror of the GHC repository on darcs.haskell.org. Things can be set up so that the hashed and old-fashioned repositories push to each other. [1] http://darcs.net/manual/node6.html#SECTION00640000000000000000 [2] http://wiki.darcs.net/index.html/DarcsTwo ---------- nosy: +eivuokko, jaredj, wglozer priority: -> bug status: chatting -> need-volunteer title: darcs 2.0.2 (+ 76 patches) fails where darcs 1.0.9(release) succeeds (windows, ghc repo, get) -> get => Unapplicable patch (2.0.2+76) (ok with 1.0.9; case sensitivity) topic: +Windows __________________________________ Darcs bug tracker <[EMAIL PROTECTED]> <http://bugs.darcs.net/issue1067> __________________________________ _______________________________________________ Cvs-ghc mailing list [email protected] http://www.haskell.org/mailman/listinfo/cvs-ghc
