Upstream nix-serve-ng has switched to Lix as its supported Nix
implementation, so follow upstream and build the Lix-backed variant
by default. Add a release-notes entry since this changes pkgs.nix-serve-ng.
Use the upstream release with relaxed dependency bounds and declared
test build tools. Fetch it without IFD and keep the built executable on
PATH during checkPhase.
IHP needs hasql >= 1.10 via hasql-mapping. Use overrideScope to pin
IHP to the newer hasql versions which are already available as
version-suffixed extra-packages, keeping the Stackage LTS 24 defaults
for the rest of the package set.
The scope renames the hasql-stack attributes for IHP and unmarks
hasql-mapping (which is version-resolution-specific, mirroring the
hasql-notifications entry in the postgrest scope). hasql-mapping
stays in broken.yaml because it genuinely fails against the default
hasql 1.9.3.1 from Stackage LTS 24. dontCheck for the scoped deps
lives in the top-level overlay so it can apply to the versioned
attributes; tests are disabled because they connect to PostgreSQL /
docker at runtime.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Supposedly, Mercury are going to release a new version of this package
soon™ after they have been granted maintainership, so there is probably
some value in keeping this around despite the package being broken at
the moment.
The only test suite requires testcontainers-postgresql (docker); skip
it with dontCheck. Also drops postgresql-simple-postgresql-types from
transitive-broken.yaml now that postgresql-types is unbroken.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
postgresql-types ships a second `integration-tests` suite that requires
testcontainers-postgresql and Docker; select just `unit-tests` via
testTargets so Hydra can still run the hspec suite.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This embeds the data files into the pandoc library instead of referencing
the data output. This is not exactly desireable since it doesn't (necessarily)
make the executable relocatable or anything, but is required for pandoc-server
to work correctly (when built against pandoc) since it can't do I/O, i.e. can't
read from the data output.
The data files are still installed, but into $out, so that the reference can
more easily be removed when desired. (It is incurred even with a separate
data output.)
Previously, this was just enabled in pkgs.pandoc, but since that is no longer
the same as haskellPackages.pandoc, the flag has no effect.
Resolves#377637.
cabal-add and fourmolu (ab)use build-tool-depends in order to have the
package's executable in PATH during test suite _execution_. This feature
was introduced in Cabal 3.14, so we can stop modifying PATH for GHC >=
9.12.
whispers