nixpkgs

cafkafk/nixpkgs

Fork 0

Commit graph

Author	SHA1	Message	Date
Alyssa Ross	56e9d1f936	chromiumOSPackages.updateScript: fix buildspec url "paladin" doesn't seem to be up to date, whereas "full" seems to match what cros-updates-serving.appspot.com reports is currently being shipped to Chromebooks.	2020-04-23 09:06:11 +00:00
Alyssa Ross	7e683f6393	crosvm.updateScript: 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.	2019-12-24 17:23:52 +00:00
Alyssa Ross	d3b0f178ef	crosvm: init at 77.12371.0.0-rc1 Co-Authored-By: hyperfekt <git@hyperfekt.net>	2019-11-06 19:35:48 +01:00

Author

SHA1

Message

Date

Alyssa Ross

56e9d1f936

chromiumOSPackages.updateScript: fix buildspec url

"paladin" doesn't seem to be up to date, whereas "full" seems to match
what cros-updates-serving.appspot.com reports is currently being
shipped to Chromebooks.

2020-04-23 09:06:11 +00:00

Alyssa Ross

7e683f6393

crosvm.updateScript: 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.

2019-12-24 17:23:52 +00:00

Alyssa Ross

d3b0f178ef

crosvm: init at 77.12371.0.0-rc1

Co-Authored-By: hyperfekt <git@hyperfekt.net>

2019-11-06 19:35:48 +01:00

3 commits