Getting compatibility with optparse-applicative >= 0.16 only required
pulling in a patch from master which is unreleased unfortunately.
The old overrides were obsolete except for the jailbreak as the test
fixes made their way into the latest release.
hegdehog-classes allows us to build these now, hgeometry-combinatorial
needs disabling of test suite since doctests cause some kind of run time
linking issue.
chatter's latest hackage release still depends on regex-tdfa-text, but
we can apply a patch from master to remove that dependency and jailbreak
to relax the bounds on cereal. Both these issues are already resolved
on master, so the override should only stand until the next release
comes around.
Additionally the test suite needs disabling as it doesn't list all
required modules in other-modules and thus fails to compile. The issue
has been reported upstream.
haskellPackages.fullstop: unbreak
Unfortunately fullstop is practically unmaintained and has no issue
tracker. The build failure is fortunately only affecting the test suite,
so a dontCheck resolves the issue for now.
Add an override to configuration-common.nix adding the following
features to the derivation:
* Let test suite discover the built spacecookie binary, so it doesn't
skip integration tests (which are very cheap and take just over 1s).
* Install man pages shipped in the sdist. (If someone is eager to get
rid of this override feel free to explain to me how to achieve this
without a Custom build-type which pulls in thousands of modules from
Cabal. :p)
The package is missing required files for the test suite. This fixes the
following build error:
```
Building test suite 'regression' for network-2.6.3.1..
[1 of 1] Compiling Main ( tests/Regression.hs,
dist/build/regression/regression-tmp/Main.o )
tests/Regression.hs:12:1: error:
Could not find module ‘Regression.Issue215’
Use -v (or `:set -v` in ghci) to see a list of the files searched
for.
|
12 | import qualified Regression.Issue215 as Issue215
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
```
Previously, cabal-install had a custom Setup.hs which took care of
generating and installing the cabal(1) man page. While this file was a
bit of scary sight, it is certainly nice to have a man page properly
installed. For the 3.2.0.0 release they switched to the default setup
type again, so the man page isn't installed anymore. Fortunately the
cabal cli can generate the man page as well, so the override to add the
man page back is pretty simple.
The commit that introduced this is the following:
https://github.com/haskell/cabal/commit/91ac075930c87712eeada4305727a4fa651726e7
I actually made a mental note of this a few weeks ago already, but it
slipped my mind when we updated to cabal-install 3.2.0.0 two weeks ago
unfortunately.
Malte Brandy