summary refs log tree commit diff
path: root/pkgs/os-specific/linux/chromium-os/modp_b64
diff options
context:
space:
mode:
authorAlyssa Ross <hi@alyssa.is>2019-12-17 17:07:40 +0000
committerAlyssa Ross <hi@alyssa.is>2019-12-17 17:07:40 +0000
commita769353d5fd4ccd70be3b196c945c9c25e3493be (patch)
treec1cfc655d0cb88d8bf11e5ee20be0b22c766765a /pkgs/os-specific/linux/chromium-os/modp_b64
parent752c156cab8604d0491f266cfb30020713ec4cbc (diff)
downloadnixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar.gz
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar.bz2
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar.lz
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar.xz
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.tar.zst
nixpkgs-a769353d5fd4ccd70be3b196c945c9c25e3493be.zip
chromiumOSPackages: use more stable update source
It has been explained to me that cros-omahaproxy reports which
versions are available to users, while cros-updates-serving reports
the latest builds available for each channel.  The latter is probably
better for our use case anyway, and apparently, while both aren't
officially supported, is less likely to randomly break.

So let's use that instead, even if it is much more annoying to parse.
Diffstat (limited to 'pkgs/os-specific/linux/chromium-os/modp_b64')
0 files changed, 0 insertions, 0 deletions