diff options
| author | Alyssa Ross <hi@alyssa.is> | 2022-07-14 15:17:22 +0000 |
|---|---|---|
| committer | Alyssa Ross <hi@alyssa.is> | 2022-07-21 16:30:56 +0000 |
| commit | c01c68bf1c2d08503ef5975da931ba9ca05a4b48 (patch) | |
| tree | 6a5ea0087bc8e12804273323f735196cd130edfe /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch | |
| parent | acdfec904d141744461a8afe93c20caa89e4fd26 (diff) | |
crosvm.updateScript: stop trying manifest-versions
manifest-versions never seems to contain the release build any more,
so we can't use it to find the version of crosvm being served to CrOS
devices.
Instead, I've changed the update script to take the latest version of
the appropriate crosvm Chrome OS release branch. This is the branch
that gets served. Every release, it is branched off from the
"chromeos" branch (which is the one that passes Chrome OS QA), and
then collects any critical fixes over the lifetime of the release.
With this change, I've introduced a new, simplified versioning
scheme, e.g. 100.0. The tip build is always 1:1 with the Chrome
version, so having both of those is redundant. The other number is
the number of commits that have been added to the release branch after
branching from the chromeos branch, so that the number will go up if
we update to include a new commit from the same release.
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions