The contribution guidelines require an unstable version to be leading
with a real version, or if none is available with `0-`.
This is because certain Nix operations split a package's full name into
name and version component starting with the first section starting with
a digit.
say has test failures with GHC 9.10.2 (upstream issue [fpco/say#5]).
Since say is only a test dependency of conduit-concurrent-map, the
latter's output is unaffected by this workaround.
[fpco/say#5]: https://github.com/fpco/say/issues/5
Some packages have stopped evaluating because libsoup_2_4 got marked insecure.
Some other packages have migrated away from old webkits and do eval now.
They don’t necessarily build now, but we have to deal with that differently.
`text-builder` had a major release v1, with many breaking changes. We
already pin an older version of `hasql`, which is not going to be
updated anymore, thus pinning older versions of `text-builder` as well.
text-builder 0.6.10 needs text-builder-dev < 0.4, so pinning that as
well.
all-cabal-hashes: 2025-08-06T11:20:02Z -> 2025-08-21T20:39:52Z
(generated by maintainers/scripts/haskell/update-package-set.sh)
haskellPackages.commonmark-simple: drop obsolete upstream
Upstream doesn't seem to have any upper bounds that affect us and
the patch has been released.
all-cabal-hashes: 2025-08-12T16:41:08Z -> 2025-08-12T21:33:00Z
(generated by maintainers/scripts/haskell/update-package-set.sh)
Need to upgrade os-string to fix eval. Note that the older GHCs have a
newer os-string compared to the 9.10.2 core package, but should only
include non-breaking changes…
Bounds issue with statistics has been resolved by a Hackage revision.
We can now force terminfo to be built, making the
configuration-ghc-*.nix file for ghcHEAD free of conditionals. Of
course, certain packages won't exist on every platform, e.g. terminfo
won't be available when cross-compiling to Windows. In such situations,
however, depending on the package doesn't make sense anyways so having
it set to `null` should be fine.
Fix version number for the ghc specific configuration. We'll have to
create a new one upon release of GHC 9.14, but there aren't any
overrides beyond core packages in there anyways.
