aszlig 0c2683cc11 chromium: Fix wrong/missing hash for beta channel ... The hash provided in commit 072917ea5d is faulty, either because the upstream tarball has changed or because it was wrong in the first place, no matter what happened we can't really verify if we don't have the tarball with the old hash. To double-check I've verified the hash against the one from Gentoo[1], which has the following SHA256: b46c26a9e773b2c620acd2f96d69408f14a279aefaedfefed002ecf898a1ecf2 After being converted into base 32 the hash does match with ours. Note that I haven't tested building all Chromium channels (yet), but we can fix upcoming issues later because right now it doesn't build anyway because of the failing hash check. [1]: https://gitweb.gentoo.org/repo/gentoo.git/tree/www-client/chromium/Manifest?id=2de0f5e4ffeb46a478c589b21d5bbcfd5736e57b Signed-off-by: aszlig <aszlig@redmoonstudios.org>		2016-09-25 20:58:03 +02:00
..
patches	chromium: fix "Aw, snap!" after glibc 2.24 upgrade	2016-08-23 11:56:11 +01:00
browser.nix	chromium: split the sandbox into a seperate output (take 2)	2016-08-06 14:42:13 +01:00
common.nix	treewide: explicitly specify gtk and related package versions	2016-09-12 18:26:06 +03:00
default.nix	treewide: explicitly specify gtk version	2016-09-13 21:09:24 +03:00
plugins.nix
update.nix	lib/fetchers.nix: factor out impure proxy vars (#18702)	2016-09-17 21:50:01 +02:00
update.sh
upstream-info.nix	chromium: Fix wrong/missing hash for beta channel	2016-09-25 20:58:03 +02:00