I am not screening this one quite yet. Let's the final decision between this
one and patch2392 when directory-1.3.8.5 appears on hackage.

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

patch 48b4d37e2d3ae4773260f7c7afd823bd1fa78024
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon May 20 08:28:04 CEST 2024
  * resolve issue2721 by excluding certain versions of directory package

  Versions 1.3.8 up to 1.3.8.4 of the directory package have a bug in their
  implementation of copyFile on Windows.

Attachments

• patch-preview.txt
• resolve-issue2721-by-excluding-certain-versions-of-directory-package.dpatch

Apparently it has already appeared on hackage. And it looks as if it 
builds against 1.3.8.5 with all our supported ghc versions. So we could 
even simplify the constraint to just >= 1.3.8.5 && < 1.4. I am not sure 
if this is wise though.

I'm also not sure it's wise, directory is a "boot" package so I think
there are scenarios where it could cause trouble. Anyway, we could
consider that in a separate patch, your current approach is a more
minimal fix.

I'm in favour of this rather than patch2392, as I'd hope the whole
ecosystem will pick up the directory fix asap.

Building with stack now requires a few more extra-deps, at least with the 
latest lts (or with the latest nightly):
- directory-1.3.8.5
- Cabal-3.10.3.0
- Cabal-syntax-3.10.3.0
- haskeline-0.8.2.1
- process-1.6.20.0
in addition to the three we already need.

The alternative is to downgrade (for the time being) to lts-21.25 (the 
latest that uses ghc-9.4) and change the conditional (introduced to solve 
the tls issue) in darcs.cabal from

    if impl(ghc >= 8.8)

to

    if impl(ghc >= 9.6)

This works with just two extra-deps:

resolver: lts-21.25

packages:
- .

extra-deps:
- strict-identity-0.1.0.0
- safe-0.3.21

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

patch 0b6de928211f1a23ea88b38bcc9127f0e74c5af3
Author: Ben Franksen <ben.franksen@online.de>
Date:   Mon May 20 11:06:37 CEST 2024
  * downgrade stack.yaml to use lts-21.25

  Otherwise we would have to add quite a number of extra-deps, even with
  nightly-2024-05-20. This also changes the conditional for depending on
  crypton-connection-0.4.0 in the cabal file to ghc >= 9.6.

Attachments

• downgrade-stack_yaml-to-use-lts_21_25.dpatch
• patch-preview.txt

CI says this works well
https://github.com/bfrk/darcs-ci/actions/runs/9156271541

Screening this now (including the follow-up change in stack.yaml)

Looks good