summary refs log tree commit diff
path: root/pkgs/applications/networking/browsers/chromium
diff options
context:
space:
mode:
authoraszlig <aszlig@redmoonstudios.org>2016-10-09 13:41:24 +0200
committeraszlig <aszlig@redmoonstudios.org>2016-10-09 13:43:04 +0200
commitbc6caeabccf7de07c46d86edefa2583302b9c11f (patch)
tree2e0db955813432e4f4791309733e38348e221b99 /pkgs/applications/networking/browsers/chromium
parentda5c0220aa42e8bde1664463d8b1d2bebc861714 (diff)
downloadnixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar.gz
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar.bz2
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar.lz
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar.xz
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.tar.zst
nixlib-bc6caeabccf7de07c46d86edefa2583302b9c11f.zip
chromium: Fix wrong hash for beta channel
It seems that upstream has re-uploaded the tarball again (see
0c2683cc110659d57e36329585469d5d653a0817).

I've verified the new hash from two different hosts.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Diffstat (limited to 'pkgs/applications/networking/browsers/chromium')
-rw-r--r--pkgs/applications/networking/browsers/chromium/upstream-info.nix2
1 files changed, 1 insertions, 1 deletions
diff --git a/pkgs/applications/networking/browsers/chromium/upstream-info.nix b/pkgs/applications/networking/browsers/chromium/upstream-info.nix
index 1ed53c0500f0..dfac55a18b6f 100644
--- a/pkgs/applications/networking/browsers/chromium/upstream-info.nix
+++ b/pkgs/applications/networking/browsers/chromium/upstream-info.nix
@@ -1,7 +1,7 @@
 # This file is autogenerated from update.sh in the same directory.
 {
   beta = {
-    sha256 = "1lix5wzcwf666vsdbdzz071rynswlxg5414k3nsrmlxwxhyh6qi4";
+    sha256 = "0f6cqvhlg06lrf4bzaiwzm9yi3fi1dk5jrzvjcg7alw3mzrmh2wv";
     sha256bin64 = "02cv9vc1l2nlwa4a0lc7cj9c9czrwp1jd8d024bq16a5fvmhl01l";
     version = "54.0.2840.50";
   };