Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: NixOS/nixpkgs
base: 826d61e5d960
Choose a base ref
...
head repository: NixOS/nixpkgs
compare: c76deaef9caa
Choose a head ref
  • 3 commits
  • 4 files changed
  • 1 contributor

Commits on Dec 24, 2019

  1. 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.
    @alyssais
    alyssais committed Dec 24, 2019
    Copy the full SHA
    7e683f6 View commit details
    Browse the repository at this point in the history

  2. crosvm: add myself as maintainer

    @alyssais
    alyssais committed Dec 24, 2019
    Copy the full SHA
    0c62e73 View commit details
    Browse the repository at this point in the history

  3. crosvm: 77.12371.0.0-rc1 -> 79.12607.0.0-rc4 

    Replaced src munging with a custom unpackPhase because the previous
approach couldn't handle a newly introduced path with a space, and
this is cleaner anyway (but was impossible at the time due to
unpackPhase not being forwarded to fetchcargo).
    @alyssais
    alyssais committed Dec 24, 2019
    Copy the full SHA
    c76deae View commit details
    Browse the repository at this point in the history