Since 445371f309
(which added `strictDeps = true;`) the build of PostgreSQL is broken if
python support is enabled (via argument `pythonSupport = true`). The
problem seems to be that PostgreSQL’s build system is unable to find
the supplied Python installation.
This commit fixes the build by setting the `PYTHON` environment variable
within the build environment, as document here:
https://www.postgresql.org/docs/current/install-make.html#CONFIGURE-ENVVARS-PYTHONCloses#372333
Building postgresql_14 currently fails with this on master:
error: derivation contains an illegal reference specifier 'man'
The reason seems to be a bug in nix, where outputChecks are run
improperly when one of the outputs can already be substituted. Why the
man output can be substituted from hydra is unknown, but adding more
outputChecks for the the man and doc outputs should work around the
problem until nix is fixed.
It doesn't matter whether the hostPlatform could execute stuff from the
buildPlatform - we need it the other way around: Certain things during a
build process can only happen when, as part of the build, the
**buildPlatform** can execute the code it just created for the
**hostPlatform**.
Unless we are talking about compilation at run-time, as in the case of
PostgreSQL. Extend the comment there to make it clear that this is on
purpose. Another case that's OK is vlc, where luac can't cross-compile
at build time, thus the bytecode is actually build for the buildPlatform
and the sources must be interpreted at runtime instead.
This has been added in #22166 in 2017.
Upstream has archived the repo in 2020:
https://github.com/zulip/tsearch_extras/issues/7
This dependency is unused, abandoned and r-ryantm tries to "downgrade"
it: Let's remove it!
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build a08b3a4d19.tar.gz \
--argstr baseRev b32a094368
result/bin/apply-formatting $NIXPKGS_PATH
After final improvements to the official formatter implementation,
this commit now performs the first treewide reformat of Nix files using it.
This is part of the implementation of RFC 166.
Only "inactive" files are reformatted, meaning only files that
aren't being touched by any PR with activity in the past 2 months.
This is to avoid conflicts for PRs that might soon be merged.
Later we can do a full treewide reformat to get the rest,
which should not cause as many conflicts.
A CI check has already been running for some time to ensure that new and
already-formatted files are formatted, so the files being reformatted here
should also stay formatted.
This commit was automatically created and can be verified using
nix-build a08b3a4d19.tar.gz \
--argstr baseRev 78e9caf153
result/bin/apply-formatting $NIXPKGS_PATH
