the gnome2 namespace nebulously refers to an gnome 2, a desktop we never
properly packaged. now it holds a bunch of gtk2 or otherwise unused
packages. its contents were handled in previous commits, and now that it
is empty except for aliases, we drop the namespace entirely. aliases
were added only for the recent additions to the list, as the ones from
before 2024 seem to have little use and are no longer kept in
aliases.nix.
The lua and server Cabal flags are expected to be on by default. Assert
they actually made it into the built binary via a `pandoc --version`
check in postInstall, so a future toolchain change can't silently drop
them without failing the build.
https://github.com/NixOS/nixpkgs/issues/540900
Co-authored-by: Lukas Epple <sternenseemann@systemli.org>
Assisted-by: Claude Code <noreply@anthropic.com>
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.
Previously the user-supplied package list was passed directly through
`lib.closePropagation` and an `isHaskellLibrary`-attribute filter, so
mistakes such as `[ dontCheck hp.foo ]` (forgetting parentheses around
the override) silently produced a GHC environment with the affected
package missing instead of failing.
Validate each top-level entry up front. We deliberately accept any
derivation (not just Haskell libraries), because shellFor passes
mixed inputs like `libraryFrameworkDepends` through here on Darwin;
those are still silently dropped by the existing closure-side filter.
The user-error case the issue is about -- non-derivation values like
functions or strings -- is now rejected with a helpful message that
points at the canonical fix.
Fixes#30304
Assisted-by: claude-code with claude-opus-4-8[1m]-high
We are dropping libsoup 2.4 due to it having been long insecure. There
are two remaining dependents in the Hackage set:
- spike is a 15 year old "experimental web browser"
- gi-soup2 is autogenerated bindings for libsoup 2.4
Neither of these justify being kept around, so we mark them broken so
the package set can continue to evaluate.
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.
Warp has been failing to build in the darwin sandbox for a long time,
because of some failing tests, even with local networking enabled. This
does not surface when using it from the cache, because hydra builds
without sandbox. But for development / nixpkgs-review, this is heavily
annoying. Disabling these two tests makes the build pass on the
community builder for me.
cabal-fmt now builds well without the override for `Cabal-syntax` ([but
with jailbreaking for other dependencies][cabal-fmt#98]) on GHC versions
9.6 and up (and possibly on earlier versions; I did not test it).
[cabal-fmt#98]: https://github.com/phadej/cabal-fmt/issues/98
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>
