Neil Mitchell <[email protected]> writes: >> I say this was a silly remark on my part, because now I realise the >> point about Neil's comment about darcs init/pull and darcs get having >> the same result was about the network error... which you probably >> rightly point out was just due to transient network failure. Darcs >> get a second time would probably have had the same effect. > > This isn't (or really really doesn't seem) to be a transient network > failure. I replicated the behaviour with 3 different repos, on > different machines, about 15 times in total. Network error was my > first guess too.
OK, thanks for establishing that it's not a transient network error. (That bit of information got lost somewhere between your initial bug report and my brain.) Can you try with --debug and --verbose and attach the transcripts? Do you have any HTTP proxying or other funky networking set up? > Has anyone tried replicating this problem on Windows? All my machines > were running the same latest semi-official build. Not me. I can do that if you'll supply me with the necessary software licenses, hadrware, and remote access... PS: Can we move this onto [email protected]? _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
