fix(glittershark/kernel): Ensure kernel changes cachebust linux-ck
Previously changed kernel versions would not cachebust the patch download, because it would still be using the same SHA hash. Forcing a different store path (by adding the version to the name) also forces a redownload of the patch (and in turn cause the hash to mismatch), avoiding this as a silent cause of failures in channel updates. Change-Id: I81a136ee2401126795cf042b0aadf2a1e7a707b4 Reviewed-on: https://cl.tvl.fyi/c/depot/+/2114 Tested-by: BuildkiteCI Reviewed-by: glittershark <grfn@gws.fyi>
This commit is contained in:
parent
cd652b3b22
commit
e908882610
1 changed files with 1 additions and 0 deletions
|
@ -8,6 +8,7 @@ let
|
||||||
patched-linux-ck = stdenvNoCC.mkDerivation {
|
patched-linux-ck = stdenvNoCC.mkDerivation {
|
||||||
name = "linux-ck";
|
name = "linux-ck";
|
||||||
src = builtins.fetchurl {
|
src = builtins.fetchurl {
|
||||||
|
name = "linux-ck-patch-${mm}-ck1.xz";
|
||||||
# example: http://ck.kolivas.org/patches/5.0/5.4/5.4-ck1/patch-5.4-ck1.xz
|
# example: http://ck.kolivas.org/patches/5.0/5.4/5.4-ck1/patch-5.4-ck1.xz
|
||||||
url = "http://ck.kolivas.org/patches/${mj}.0/${mm}/${mm}-ck1/patch-${mm}-ck1.xz";
|
url = "http://ck.kolivas.org/patches/${mj}.0/${mm}/${mm}-ck1/patch-${mm}-ck1.xz";
|
||||||
sha256 = "01jyg9x2ligr0gjic8lg4f7hw3isz94kqwdbzdk9n8nghklh38p4";
|
sha256 = "01jyg9x2ligr0gjic8lg4f7hw3isz94kqwdbzdk9n8nghklh38p4";
|
||||||
|
|
Loading…
Reference in a new issue