Hi Adolfo,

One thing I just noticed after applying one of Petr's test patches.  If 
you don't have a global cache directory (as in the case in the 
regression tests), darcs will complain about not being able to reach it.

This sounds like it may be an easy exception to account for.  Could you 
investigate and see what needs to be done?  I think you only need to 
handle the case of the default global cache dir.

Argh, I meant to say this is a minor regression introduced with your 
issue1599 work

This is actually a major regression, since I am seeing this, if the 
global cache does not exist (running cabal test get-http -- you need 
lighttpd for that, and you need to run *only* that -- an earlier test 
would have created the global cache...).

+ darcs get http://localhost:23032/R S
Hash failure in 
http://localhost:23032/R/_darcs/pristine.hashed/87428fc522803d31065e7bce
3cf03fe475096631e5e07bbd7a0fde60c4cf25c7

darcs failed:  Couldn't fetch 
`87428fc522803d31065e7bce3cf03fe475096631e5e07bbd7a0fde60c4cf25c7'
in subdir pristine.hashed from sources:

For all I can tell, this is because the code tries to check cache 
reachability *before* trying to create it, which consequently leads it 
to to forget to write the actual file it intended to write.

Well, seems like an easy fix, submitting now... please review ASAP.

The following patch updated issue issue1908 with status=resolved;resolvedin=2.8.0 HEAD

* Resolve issue1908: try to create a global cache before checking its availability. 
Ignore-this: a93e6f5d4a1272fc49341236820a9833

Rebased to resolve conflict & removed Setup.hs

1 patch for repository http://darcs.net/screened:

patch cfe1a7106c414f6518da1e47f4f9bb9f2d75cd6b
Author: Ben Franksen <ben.franksen@online.de>
Date:   Sat Jan 25 13:09:59 CET 2020
  * WIP: drop custom Setup.hs

Attachments

• patch-preview.txt
• unnamed
• wip_-drop-custom-setup_hs_0.dpatch

Sorry, please ignore, I messed up the subject.

This one was accidentally reset to open.