On Sun, Sep 07, 2008 at 09:07:09PM +0200, Matthias Kilian wrote:
>
> Someone with the time (and write access to darcs.haskell.org) should
> probably roll new repository tarballs to let this problem disappear
> once and forall.
I've put 2008-09-07 tarballs up, although downloading them will be
pai
On Sun, Aug 24, 2008 at 09:52:49PM +0100, Claus Reinke wrote:
> Ian: this might actually be an issue with ghc's "darcs-all" script: it
> probably comes about because "darcs-all" is reading _incrementally_
>from "packages",
>interfering with "darcs pull" trying to update "packages"
Ah, good point, thanks. I tend to push to Windows, which is why I
haven't seen this. I've applied your fix, from another of your messages.
Thanks. Incidentally, adding "$| = 1;" to autoflush stdout after each
print avoids having extra output after a "die" message, and I also
want to see the su
On Sun, Aug 24, 2008 at 09:52:49PM +0100, Claus Reinke wrote:
>
> Ian: this might actually be an issue with ghc's "darcs-all" script: it
> probably comes about because "darcs-all" is reading _incrementally_
>from "packages",
>interfering with "darcs pull" trying to update "packag
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 usuall
Eric Kow <[EMAIL PROTECTED]> added the comment:
On Sun, Aug 24, 2008 at 20:53:21 -, Claus Reinke wrote:
> 1. I have a local copy of ghc head + corelibs + extralibs repos,
> obtained a while ago by the usual hack of downloading tar-file,
> then ./darcs-all pull and get from the main
