Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

crosvm: 104.0 -> 107.1 #193746

Merged
merged 4 commits into from Nov 18, 2022
Merged

crosvm: 104.0 -> 107.1 #193746

merged 4 commits into from Nov 18, 2022

Commits on Nov 18, 2022

  1. crosvm: switch back to old git repo URL 

    Despite having moved the main repo to crosvm/crosvm, release branches
are still only being created on chromiumos/platform/crosvm.  So we
should have crosvm/crosvm as the homepage, but fetch from
chromiumos/platform/crosvm.

Link: NixOS#193746
    @alyssais
    alyssais committed Nov 18, 2022
    Copy the full SHA
    87105d4 View commit details
    Browse the repository at this point in the history

  2. crosvm.updateScript: update release branch format 

    For R106 and onwards, upstream has gone back to not having a
separation between chromeos and not.
    @alyssais
    alyssais committed Nov 18, 2022
    Copy the full SHA
    278a896 View commit details
    Browse the repository at this point in the history

  3. crosvm: 104.0 -> 107.1 

    crosvm now includes a Cargo.lock again, so we don't need to vendor it
into Nixpkgs.

Its build system now compiles the seccomp policies into the binary, so
we don't need to build and install those ourselves any more.
    @alyssais
    alyssais committed Nov 18, 2022
    Copy the full SHA
    131a026 View commit details
    Browse the repository at this point in the history

  4. crosvm.updateScript: don't vendor Cargo.lock 

    This is no longer required as crosvm now includes a Cargo.lock in-tree
again.
    @alyssais
    alyssais committed Nov 18, 2022
    Copy the full SHA
    8f2fe0d View commit details
    Browse the repository at this point in the history