This reverts commit 65a333600d.
This wasn't tested for correctness with something like fodwatch [0],
and should not have been (self-)merged so quickly, especially without
further review.
It also resulted in the breakage of at least one package [1] (and that's
the one we know of and was caught).
A few packages that were updated in between this commit and this revert
were not reverted back to using `rev`, but other than that, this is a
1:1 revert.
[0]: https://codeberg.org/raphaelr/fodwatch
[1]: https://github.com/NixOS/nixpkgs/pull/396904 / 758551e458
Format all Nix files using the officially approved formatter,
making the CI check introduced in the previous commit succeed:
nix-build ci -A fmt.check
This is the next step of the of the [implementation](https://github.com/NixOS/nixfmt/issues/153)
of the accepted [RFC 166](https://github.com/NixOS/rfcs/pull/166).
This commit will lead to merge conflicts for a number of PRs,
up to an estimated ~1100 (~33%) among the PRs with activity in the past 2
months, but that should be lower than what it would be without the previous
[partial treewide format](https://github.com/NixOS/nixpkgs/pull/322537).
Merge conflicts caused by this commit can now automatically be resolved while rebasing using the
[auto-rebase script](8616af08d9/maintainers/scripts/auto-rebase).
If you run into any problems regarding any of this, please reach out to the
[formatting team](https://nixos.org/community/teams/formatting/) by
pinging @NixOS/nix-formatting.
5dfa2d6f55 missed the fact that pandoc 3.6
newly requests non Stackage LTS 22 versions of some packages. Since
pandoc_3_6 wasn't actually tested in CI, this was missed.
The new version typst uses its Paths_ for determining its version,
so we need to remove the incorrectly generated references. See
<9707b74ce6>.
On haskell-updates, no pandoc_3_* exists anymore, so we don't need to
do anything. We may want to add quarto to the jobset, but it's quite
heavy…
Resolves#375884.
Quoting the patch:
> Previously, OFD locking was broken on 32-bit, because it would somehow
> end up using the 64-bit fcntl() function, but pass it 32-bit off_t
> values in struct flock. To fix this, tell libc to use always use
> 64-bit file offsets.
>
> This is the same fix that was applied for a similar issue in GHC.
lzma-static is deprecated in favor of xz which can finally be built
against the system library instead of vendoring and statically linking
xz in the Hackage package.
I've set all packages that vendor lzma somehow related to these packages
to dontDistribute since we don't really want to redistribute potentially
outdated versions of xz (maybe we should mark these as broken,
actually).
Upstream has fixed the implicit declarations in a new release. That
release also includes the test suite in the default package which
unfortunately segfaults, so the build is failing again.
As of [this PR](https://github.com/NixOS/cabal2nix/pull/630)
opencascade-hs does not require the dependency on opencascade-occt to be
manually specified. It does however still require the include path to be
defined.
Co-authored-by: sternenseemann <sternenseemann@systemli.org>
I've contacted the maintainer of libxml-sax directly as the package does
not seem to have a public issue tracker.
(cherry picked from commit 1ad0cb4d35)
This is another gcc 14 workaround.
haskellPackages.HsOpenSSL: don't silence incompatible-pointer-types
Disabling the error is a better option than silencing the warning which
still applies…
(cherry picked from commit 9c577069d9)
This is another gcc 14 workaround.
haskellPackages.HsOpenSSL: don't silence incompatible-pointer-types
Disabling the error is a better option than silencing the warning which
still applies…
Upstream tries to do something clever with restricting tls
directly (even though it is an indirect dependency). We could easily
provide crypton-connection >= 0.4 and tls >= 2.0.6, but it only wants
that for GHC >= 9.8 claiming it is not possible for earlier versions.
