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.
This ensures CI tests the nano variant. It also makes it easier to use
with `libc = "newlib-nano";` in a platform description.
(cherry picked from commit e3ff6189f6aa641e108876de32ad83a542259b60)
Discourse normally overrides the default notification email setting,
which makes the `notificationEmailAddress` setting ineffective. Add a
patch to remove this override.
Fixes#140114.
(cherry picked from commit 917a0cfe47bad420a894fe8ca35d7dd95ebb5a7c)
The version update has been cherrypicked from master where bundle has
been updated to 2.2.20. It was then failing to run with:
./result/bin/foreman
Warning: the running version of Bundler (2.1.4) is older than the version that created the lockfile (2.2.20). We suggest you to upgrade to the version that created the lockfile by running `gem install bundler:2.2.20`.
Traceback (most recent call last):
2: from ./result/bin/foreman:20:in `<main>'
1: from /nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:413:in `block in replace_bin_path'
/nix/store/ggqacj06n6qfm1iww0bih9ph0j89wcna-bundler-2.1.4/lib/ruby/gems/2.7.0/gems/bundler-2.1.4/lib/bundler/rubygems_integration.rb:374:in `block in replace_bin_path': can't find executable foreman for gem foreman. foreman is not currently included in the bundle, perhaps you meant to add it to your Gemfile? (Gem::Exception)
In $out/share it is NOT picked up into /etc/systemd/... when psi-notify is
added to configuration.systemd.packages .
(Originally put in $out/share b/c a hook copies from $out/lib into there
... so why not just put there? This is why.)
(cherry picked from commit a774af3605a86719f813ccb80e9f8a5bdef2ee0a)
The MariaDB version 10.6 doesn't seem supported with current Nextcloud
versions and the test fails with the following error[1]:
nextcloud # [ 14.950034] nextcloud-setup-start[1001]: Error while trying to initialise the database: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 4047 InnoDB refuses to write tables with ROW_FORMAT=COMPRESSED or KEY_BLOCK_SIZE.
According to a support-thread in upstream's Discourse[2] this is because
of a missing support so far.
Considering that we haven't received any bugreports so far - even though
the issue already exists on master - and the workaround[3] appears to
work fine, an evaluation warning for administrators should be
sufficient.
[1] https://hydra.nixos.org/build/155015223
[2] https://help.nextcloud.com/t/update-to-next-cloud-21-0-2-has-get-an-error/117028/15
[3] setting `innodb_read_only_compressed=0`
(cherry picked from commit 675e262f5a03eb9aa6b0500434ee30a9d6b882a0)
sternenseemann
John Ericson
Lara
John Ericson
Kim Lindberger
Bobby Rong
ajs124
Maximilian Bosch
Sandro
Janne Heß
Antoine Eiche
figsoda
Eduard Bachmakov
José Romildo
Michael Weiss
Lassulus
maxine [they]
github-actions[bot]
Vladimír Čunát
nixpkgs-upkeep-bot
TredwellGit
Michele Guerini Rocco
Guillaume Girol
Artturin
Bernardo Meurer