Getting darcs.net repo caused this:

[owen@OWEN-LTL code]$ darcs get http://darcs.net
Welcome to the darcs unstable repository.

If you would like to contribute, please read our guide for contributors:
http://wiki.darcs.net/Development/GettingStarted

Thanks and happy hacking!
**********************
Copying patches, to get lazy repository hit ctrl-C...                  
       
Finished getting.                                                      
        
darcs:
/home/owen/.darcs/cache/patches/0000000847-4b429e5ab403e152ee66bc4a00ddb2a0444a322a9208b81672ce892e361811ae-new_3da69d4db93d5af09a8cf9dee1c2d8b6:
getSymbolicLinkStatus: does not exist (No such file or directory)

So I did a tiny bit of ls-investigation:

[owen@OWEN-LTL code]$ ls
/home/owen/.darcs/cache/patches/0000000847-4b429e5ab403e152ee66bc4a00ddb2a0444a322a9208b81672ce892e361811ae-new_3da69d4db93d5af09a8cf9dee1c2d8b6
ls: cannot access
/home/owen/.darcs/cache/patches/0000000847-4b429e5ab403e152ee66bc4a00ddb2a0444a322a9208b81672ce892e361811ae-new_3da69d4db93d5af09a8cf9dee1c2d8b6:
No such file or directory

[owen@OWEN-LTL code]$ ls
/home/owen/.darcs/cache/patches/0000000847-4b429e5ab403e152ee66bc4a00ddb2a0444a322a9208b81672ce892e361811ae

/home/owen/.darcs/cache/patches/0000000847-4b429e5ab403e152ee66bc4a00ddb2a0444a322a9208b81672ce892e361811ae

the -new_*junk* is a temp file of some sort, created by curl, I think.

This seems to be related with curl and HTTP pipelining. Here is what I
get with latest reviewed branch. I created a repo with more than 400
files in the working copy (hence pristine) and put it on my university's
web server.

The following regularly throws the error (probability > 0.6) :

    rm  ./issue2061 -rf &&  time darcs get
http://www.cs.famaf.unc.edu.ar/~hoffmann/issue2061  --lazy --verbose
--no-packs --disable-patch-index    --no-cache

While with --no-http-pipelining, the probability falls to less than 0.1
(I've seen it happen twice).