Thanks for the details! That will be helpful for our attempts to
reproduce this.
I haven't been able to reproduce this myself yet (using only the
Cabal repo), but it was the best info I had.
Perhaps 'darcs pull' should report the ids of the first and last
patch it pulled, by default (I usually do pull -av and record the
output for the main repos, but tend to forget that for the validate
repos, as in this case), to improve chances of getting more accurate
error reports? Otherwise, guessing what happened from the
"pending" file looks like the best chance.
Presumably the libraries/Cabal repository had no local changes
before doing the pull. Is that correct?
Correct. Though I didn't check that there were no darcs issues
in the target repos before pulling, and with darcs' current
warn-once-then-pretend-nothing-happened strategy (Issue1010),
it is just possible that the Cabal repo I pulled into already had
leftover stuff in pending or other issues.
Claus
_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
