The rationale for this is that old filesystems have recieved little scrutiny
wrt. security relevant bugs.
Lifted from OpenSUSE[1].
[1]: 8cb42fb665
Co-Authored-By: Renaud <c0bw3b@users.noreply.github.com>
* pivx: 3.2.0 -> 3.2.2
* altcoins.pivx: 3.2.2 -> 3.3.0
Furthermore, this fixes 2542928
* pivx: 3.3.0 -> 3.4.0
Added `test_pivx` as test ran by nixpkgs
* Update pkgs/applications/blockchains/pivx.nix
Thanks to @lassulus for fixing this typo!
Co-Authored-By: Lassulus <github@lassul.us>
Default getfacl behavior is to remove leading slash on absolute
paths in its header printed to stdout.
Before the header it will also print a message about it...
Switches -p -or --absolute-names can turn this off
and remove some noise from our tests logs.
This partially reverts commit
f45798e544.
cc @ivan I'd like to have that left in, because it's very useful for
gcc compiles, when necessary patches often span multiple releases,
i.e. for aarch64 builds
CVE-2019-13693 CVE-2019-13694 CVE-2019-13695 CVE-2019-13696
CVE-2019-13697
Disable jumbo mode because upstream dropped support for it.
(See chromium-dev "We're removing support for the jumbo build")
This makes builds take about 3x as long, but we have no alternative.
We need rst2man to build manpages.
I also removed revert-create-dirs-on-install.patch, as it doesn't apply
cleanly anymore, and is purely cosmetic anyway.
+ building from gitlab source
+ reorderd dependencies to be in logical/alphabetical order
+ replaced patches with substituteInPlace, as patches broke the installChecks
and substituteInPlace may be more robust than making new patches for each
release. Also the compiled source is now closer to upstream than
before.
+ added installChecks
+ added all supported devices as listed on epson.net
Rather than using autodiscovery, the checkPhase should import
`__init__.py` from `diff_match_patch.tests to execute all relevant
tests. Otherwise several python2-related tests are executed in a py3 env
and break the build.
See also: https://hydra.nixos.org/build/102482273
