cabal-head fails to build openapi3-3.2.4 "dist/build/example/example: copyFile: does not exist (No such file or directory)"

[tchoutri]

Describe the bug

Compiling openapi3-3.2.4 with a "recent" cabal-head (installed through ghcup as said in the README) gives:

To Reproduce

$ ghcup install cabal --force -u https://github.com/haskell/cabal/releases/download/cabal-head/cabal-head-Linux-x86_64.tar.gz head
$ git clone https://github.com/flora-pm/flora-server
$ cd flora-server
$ cabal build
[…] # pour yourself a cup
Installing library in /home/tchoutri/.cabal/store/
  ghc-9.4.7/incoming/new-3485596/home/tchoutri/.cabal/
    store/ghc-9.4.7/openapi3-3.2.4-10ab5f1c59bbb45dbd67f02e0bbc49fff86fce693481f1e870150b3d6fa049d1/lib
Installing executable example in /home/tchoutri/.cabal/
  store/ghc-9.4.7/incoming/new-3485596/home/tchoutri/.cabal/store/ghc-9.4.7
    /openapi3-3.2.4-10ab5f1c59bbb45dbd67f02e0bbc49fff86fce693481f1e870150b3d6fa049d1/bin
Warning: The directory
/home/tchoutri/.cabal/store/ghc-9.4.7/incoming/new-3485596/home/tchoutri/
  .cabal/store/ghc-9.4.7/openapi3-3.2.4-10ab5f1c59bbb45dbd67f02e0bbc49fff86fce693481f1e870150b3d6fa049d1/bin
    is not in the system search path.
dist/build/example/example: copyFile: does not exist (No such file or directory)
Error: [Cabal-7125]
Failed to build openapi3-3.2.4 (which is required by test:flora-test from flora-1.0.14, exe:flora-server from flora-1.0.14 and others).
See the build log above for details.

Expected behavior
Not throw an error.

System information

• Operating system: Fedora 38
• cabal: cabal-head
• ghc: 9.4.7

Additional context
I got my hands on a cabal-head from December 10th, that works well: cabal-head-dec-10.tar.gz.

Not too sure what to do with this information. :/

[Bodigrim]

dist/build/example/example: copyFile: does not exist (No such file or directory)

dist instead of dist-newstyle is very suspicious here. Could anything go via v1-* code path?..

[geekosaur]

It also seems suspicious that an executable is being installed for a library dependency.

[geekosaur]

Never mind, building it locally I see all, legacy fallback. I also reproduce the install error. And also reproduce the weird-looking install paths (both dist and the duplication in the store path).

[geekosaur]

So for what it's worth, the store path shown is indeed invalid; incoming exists but contains only lock files, and in particular not tmp-NNNNN. The correct store path is the rest of the path, restarting from /.

"Legacy fallback" is because openapi3-3.2.4 uses custom setup, but only for cabal-doctests. In particular it doesn't mess with the install.

[tchoutri]

@geekosaur thank you for reproducing, I feel less like a crazy person! :D I put the blame automatically on the latest cabal-head because it's the only part of my toolchain that I regularly change. I was pretty lucky that @mau5mat hadn't updated his cabal-head since last December.

[TeofilC]

A colleague and I have also been able to reproduce this when trying to build pretty-simple, which also uses cabal-doctests

[Benjamin-McRae-Tracsis]

The build log emitted for this bit is attached.
pretty-simple-4.1.2.0-d493aee511e73506dcc2cc921e2fdbf5d1ebc2e65ff6b5237e4a2cc57d544fcc.log

EDIT: deleting .cabal/packages and .cabal/store and rebuilding results in the same issue

[mpickering]

I will try and bisect this.

[mpickering]

I have identified a good and bad commit, commencing bisecting.

[mpickering]

The bad commit is f70fc98

[ulysses4ever]

/cc @alt-romes I guess

[alt-romes]

Indeed, I'm on it. Fix incoming. Thanks @mpickering for marking this commit.