Due to the old root certificate used by letsencrypt expiring, arcanist
could not connect anymore to servers using letsencrypt (like
reviews.llvm.org).
Fix it by using the default nix certificates.
(cherry picked from commit 93eb7786c9365981854a98e508d5b1cae5ee2fcf)
GHC 8.10.7 is only in 21.05 for bootstrapping GHCJS, so it shouldn't be
included in the hls wrapper. This change was a result of an overeager
backport and we'll revert it here.
Also rollback some unnecessary change to release-haskell.nix, so it can
be used for testing evaluation still.
* chromedriver: add dbus to libraries
It is apparently required since version 94.
Fixes issue #139547
(cherry picked from commit 433b2bc44487c90c33cb58d87434a287e6d43b15)
* chromedriver: remove extraneous LD_LIBRARY_PATH in wrapProgram
wrapProgram already prepends passed value to the specified environment
variable; no need to specify it explicitly.
(cherry picked from commit 38ddfe7f3ff206888806302539def70b80ef427b)
* chromedriver: add a package test checking the reported version
(cherry picked from commit 1106f4bafc0b444384c171c63ca78b8b6676842e)
* Update pkgs/development/tools/selenium/chromedriver/default.nix
(cherry picked from commit 852612eac99dc403c0ea09a5daca9b65b5b7e123)
Co-authored-by: Ivan Timokhin <nixpkgs@ivan.timokhin.name>
Co-authored-by: Sandro <sandro.jaeckel@gmail.com>
`pkgs.fetchgit` uses `fetchSubmodules = true;` by default, however
`nix-prefetch-git` doesn't. This means that hashes for a Git repository
with fetched submodules will be wrong in `yarn.nix`.
Considering that this got unnoticed before, it seems as if this case is
an exception to a certain degree.
An exemplary problem is the last `hedgedoc` update[1] where
`js-sequence-diagrams` - a Git repo with submodules - from upstream's
package.json caused a hash mismatch. This got unnoticed because
`nix-build --check` doesn't seem to reveal these issues for fixed-output
derivations.
[1] https://github.com/NixOS/nixpkgs/pull/139238
(cherry picked from commit 46c98ae1327b7d14af1927fda971762e5ee53dfe)
Backport which adds, rather than updates, the GHC release.
----
The only big change is required for darwin since GHC 8.10.5 now
runs xattr in the install phase on darwin:
* 11e1dcde0d
* ec451cac39
Unfortunately, it uses the host /usr/bin/xattr by default which is
present in the build due to a lack of sandboxing on darwin. That xattr
version however still requires Python 2.7 whereas Python 3.8 is in PATH
in our build. We solve this by setting the XATTR environment variable.
We can't use python3Packages.xattr since GHC expects Apple's fork of
xattr which provides some extra flags to utilize.
Co-authored-by: Cheng Shao <cheng.shao@tweag.io>
(Adapted from cb330ce4f05f5a6e2da3021e9cbf4ea2eb592631)
As of yet, a patch caused the runner to discard update messages.
Unfortunately, GitHub keeps sending update messages to outdated runners
causing them to no longer pick up jobs.
This commit causes the runner to send a high version to GitHub which
should be more recent for quite a time. That way, GitHub does not send
update message and keeps scheduling jobs even for outdated runners.
Naturally, an oudated runner can still break at any time as GitHub's
current approach assumes that all runners are always up-to-date. We
should still strive for quick nixpkgs updates but this patch should give
us some time.
(cherry picked from commit e8bbcc79fd07014b146835dfd7f5eba2079d9a55)
The runner only references `GitInfoCommitHash`/`CommitHash` to print
informational log entries. To allow for just referencing the tag of a
version instead of the commit hash, this commit sets the value of the
`GitInfoCommitHash` to a static dummy value.
(cherry picked from commit cc5c902fdf94b798c3b68e55ebb7e1a1185113a1)