kernelPatches.grsecurity: 4.5.4-201605122039 -> 4.5.4-201605131918
Also revert to using the grsecurity-scrape mirror; relying on upstream just isn't viable. Lately, updates have been so frequent that a new version is released before Hydra even gets around to building the previous one.
This commit is contained in:
parent
cd5dd9f82e
commit
6194e9d801
1 changed files with 6 additions and 3 deletions
|
@ -22,8 +22,11 @@ let
|
||||||
assert kversion == kernel.version;
|
assert kversion == kernel.version;
|
||||||
{ name = "grsecurity-${grversion}-${kversion}";
|
{ name = "grsecurity-${grversion}-${kversion}";
|
||||||
inherit grversion kernel patches kversion revision;
|
inherit grversion kernel patches kversion revision;
|
||||||
|
# When updating versions/hashes, ALWAYS use the official version; we use
|
||||||
|
# this mirror only because upstream removes sources files immediately upon
|
||||||
|
# releasing a new version ...
|
||||||
patch = fetchurl {
|
patch = fetchurl {
|
||||||
url = "https://grsecurity.net/${branch}/grsecurity-${grversion}-${kversion}-${revision}.patch";
|
url = "https://raw.githubusercontent.com/slashbeast/grsecurity-scrape/master/test/grsecurity-${grversion}-${kversion}-${revision}.patch";
|
||||||
inherit sha256;
|
inherit sha256;
|
||||||
};
|
};
|
||||||
features.grsecurity = true;
|
features.grsecurity = true;
|
||||||
|
@ -106,8 +109,8 @@ rec {
|
||||||
{ kernel = pkgs.grsecurity_base_linux_4_5;
|
{ kernel = pkgs.grsecurity_base_linux_4_5;
|
||||||
patches = [ grsecurity_fix_path_4_5 ];
|
patches = [ grsecurity_fix_path_4_5 ];
|
||||||
kversion = "4.5.4";
|
kversion = "4.5.4";
|
||||||
revision = "201605122039";
|
revision = "201605131918";
|
||||||
sha256 = "10jcwz9lxb4w2p0g6mjsq515s3p0m81rr1a9mw0hqwvm23dba3fs";
|
sha256 = "0f5s8lj6zc4jp2cpxm7r891px3dmb6m3ximfigwq809yydg5aimv";
|
||||||
};
|
};
|
||||||
|
|
||||||
grsecurity_latest = grsecurity_4_5;
|
grsecurity_latest = grsecurity_4_5;
|
||||||
|
|
Loading…
Reference in a new issue