ffaf1

We don't shaft users, this has to make next `cabal-install` release.

PR template is missing @sheaf , is this a user-visible (cabal/API) change or not?

> @ffaf1 This is a change to how cabal-install invokes Cabal. There should be no visible change. This is fixing a bug (https://github.com/haskell/cabal/issues/9940) where cabal-install was passing too-recent flags to...

> This is pretty much always a mistake Is there any reasonable case where this is *not* a mistake?

If `$(which happy)` works, then executable is in `PATH`. I would consider this a bug, not a user question. @yaitskov, we need your help to diagnose this, `cabal build -v3`...

Problem with “Known issues” lists is that they get stale easily. E.g. GHC known issues section lists #12971 but that has been closed since then. I don't know whether github...

Judging from the ticket and the error line (34 vs. 35), the two runs are slightly different: ``` Up to date terminated ``` vs. ``` about to sleep done sleeping...

Small gain with an increase of stuff that can break CI, not a fan.

Do you know whether the config data was already present? It would be [failure to *write*](https://gitlab.haskell.org/ghc/ghc/-/issues/7593) rathern than read. It would be lovely if some Win users could replicate this.

I suspect 46987a928ddee7ca1310d1eeee2cbc46eecab615 https://github.com/haskell/cabal/blob/d53b4d46c51f5162e84765fd69d9c8806eea15b1/cabal-install/src/Distribution/Client/ScriptUtils.hs#L182-L186 Does this ring a bell, @bacchanalia?