pyrox.dev
Merge pull request #226396 from hzeller/20230415-update-verible
verible: 0.0.2821 -> 0.0.3179
+5
-5
pkgs/development/tools/language-servers/verible/default.nix
+5
-5
pkgs/development/tools/language-servers/verible/default.nix
···
17
17
# These environment variables are read in bazel/build-version.py to create
18
18
# a build string shown in the tools --version output.
19
19
# If env variables not set, it would attempt to extract it from .git/.
20
-
GIT_DATE = "2023-02-02";
21
-
GIT_VERSION = "v0.0-2821-gb2180bfa";
20
+
GIT_DATE = "2023-04-14";
21
+
GIT_VERSION = "v0.0-3179-g525ffaf7";
22
22
23
23
# Derive nix package version from GIT_VERSION: "v1.2-345-abcde" -> "1.2.345"
24
24
version = builtins.concatStringsSep "." (lib.take 3 (lib.drop 1 (builtins.splitVersion GIT_VERSION)));
···
27
27
owner = "chipsalliance";
28
28
repo = "verible";
29
29
rev = "${GIT_VERSION}";
30
-
sha256 = "sha256-etcimvInhebH2zRPyZnWUq6m3VnCq44w32GJrIacULo=";
30
+
sha256 = "sha256-IXS8yeyryBNpPkCpMcOUsdIlKo447d0a8aZKroFJOzM=";
31
31
};
32
32
33
33
patches = [
···
49
49
# of the output derivation ? Is there a more robust way to do this ?
50
50
# (Hashes extracted from the ofborg build logs)
51
51
sha256 = {
52
-
aarch64-linux = "sha256-dYJoae3+u+gpULHS8nteFzzL974cVJ+cJzeG/Dz2HaQ=";
53
-
x86_64-linux = "sha256-Jd99+nhqgZ2Gwd78eyXfnSSfbl8C3hoWkiUnzJG1jqM=";
52
+
aarch64-linux = "sha256-BrJyFeq3BB4sHIXMMxRIaYV+VJAfTs2bvK7pnw6faBY=";
53
+
x86_64-linux = "sha256-G6tqHWeQBi2Ph3IDFNu2sp+UU2BO93+lcyJ+kvpuRJo=";
54
54
}.${system} or (throw "No hash for system: ${system}");
55
55
};
56
56