tn23 (x86 OSX HEAD), build 778, Failure

Builder <[email protected]>
Newsgroups gmane.comp.lang.haskell.cvs.ghc
Message-ID <[email protected]>
tn23 (x86 OSX HEAD), build 778

Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/778.html

git clone          | Success
create mk/build.mk | Success
get subrepos       | Failure: Just (ExitFailure 2)

Build failed
Details: http://darcs.haskell.org/ghcBuilder/builders/tn23/778.html

_______________________________________________
Cvs-ghc mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-ghc
step.get subrepos.failed.txt (text/plain, 1.3 KB)
== running git config core.ignorecase true
== running git clone http://darcs.haskell.org/ghc-tarballs.git ghc-tarballs
Cloning into ghc-tarballs...
== ghc-tarballs: running git config core.ignorecase true
== running git clone http://darcs.haskell.org/hsc2hs.git utils/hsc2hs
Cloning into utils/hsc2hs...
== utils/hsc2hs: running git config core.ignorecase true
== running git clone http://darcs.haskell.org/haddock.git utils/haddock
Cloning into utils/haddock...
error: Failed connect to darcs.haskell.org:80; Operation timed out (curl_result = 7, http_code = 0, sha1 = 57374b1dfe4805b35634ffbb587a359e63573764)
error: Unable to find 64c6e2464fb3a9207e01b01a17c815284e49808b under http://darcs.haskell.org/haddock.git
Cannot obtain needed commit 64c6e2464fb3a9207e01b01a17c815284e49808b
while processing commit 12c7ddd2277fe0eb59356c889d2f1f099ed3342b.
error: Fetch failed.
git failed: 32768 at ./sync-all line 178.
== Checking for old haddock repo
== Checking for old binary repo
== Checking for old mtl repo
== Checking for old Cabal repo
== Checking for old time from tarball
============================
ATTENTION!

You have an old time package in your GHC tree!

Please remove it (e.g. "rm -r libraries/time"), and then run
"./sync-all get" to get the new repository.
============================
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.