When used as a global override, it breaks most of the options in the
mysql module, such as ensureDatabases, ensureUsers, initialDatabases,
initialScript.
We could use `.client` there, but if the reasoning behind this was
closure size reduction, we now end up with the same (or a bigger)
runtime closure and more complexity.
Apart from the options exposed by the mysql module, the client is also
likely to be required for local backups or DBA tasks anyways.
Instead of dealing with all the increased complexity of this for no
arguable benefit, let's just remove the `withoutClient` argument.
Storage space on mysql servers shouldn't be that much of an issue.
Closes#82428.
The following error was printed every second:
Can't exec "clear": Not a directory at /nix/store/.../bin/.mytop-wrapped line 110.
Use of uninitialized value $CLEAR in string at /nix/store/.../bin/.mytop-wrapped line 781.
Therefore the mytop output was repeatedly displayed instead of updating itself "in-place".
We want to disable `PLUGIN_AUTH_PAM` when building:
1. `mariadb` on macOS.
2. `mariadb-client` on any platform
Unfortunately, the interaction of these two commits
6c97b0486c7e43b4d0ae
created a situation where we disable it *twice* when building on macOS.
Once in a darwin-specific `prePatch` script, and again in the `patches`
section for client builds.
This removes the redundant `prePatch` script and conditionally applies
the patch to `mariadb` server builds on darwin.
Fixes#70835
The contents of `clang-isfinite.patch` are no longer necessary after
upstream revision 031fa6d4258574379ca3c1cbe912d235e9581982, which
includes a similar change.
Building in c++11 mode removes support for the GCC `typeof` extension
in favor of the standardized `__typeof__`. This causes errors when
using the `strmake_buf` macro, which relies on `typeof`.
He prefers to contribute to his own nixpkgs fork triton.
Since he is still marked as maintainer in many packages
this leaves the wrong impression he still maintains those.
Bump to latest stable version of the 10.2.x branch. Besides many bug fixes the
following security related issues have been fixed:
- CVE-2018-3060
- CVE-2018-3064
- CVE-2018-3063
- CVE-2018-3058
- CVE-2018-3066
Release notes: https://mariadb.com/kb/en/library/mariadb-10217-release-notes/
Both mariadb.com and mariadb.org appear to be canonical upstream sources, and
have identical sha256 hashes at these URLs.
For the third-party mirrors, if we are just going to provide one URL, it should
be an HTTPS url instead of FTP or SSH, which many users may not be able to
access due to network security configurations.
