From: Jamie McClymont <jamie@kwiius.com>
To: devel@spectrum-os.org
Cc: Jamie McClymont <jamie@kwiius.com>
Subject: [RFC PATCH 0/8] Update chromiumPacakges
Date: Fri, 2 Apr 2021 09:04:16 +0000 [thread overview]
Message-ID: <0100017891d36f4f-0c348828-2ed6-4694-b75c-44d0d659c13c-000000@email.amazonses.com> (raw)
Hi all
Here's a nearly-complete(?) attempt at bumping chromiumOSPackages.
Everything under chromiumOSPackages and spectrumPackages builds except crosvm
(and therefore spectrum-vm). I've added platform2 as a dependency (a few rust
crates from there are now used) and bumped the cargoSha256, so the vendor FOD
now builds happily, but the actual `cargo build` fails with:
> error: the lock file /build/src/platform/crosvm/Cargo.lock needs to be updated but --frozen was passed to prevent this
> If you want to try to generate the lock file without accessing the network, use the --offline flag.
I haven't dealt with buildRustPackage before, so I'm not sure if this is a
standard thing that any frequent buildRustPackage user will know how to fix, or
if we're running in to an odd edge-case - emailing it in as-is in the hopes that
it's the former :)
Thanks!
Jamie McClymont
Jamie McClymont (8):
chromiumOSPackages: update 83->89
chromiumOSPackages.cros_linux: fix config
chromiumOSPackages.vm_protos: drop GN patch
chromiumOSPackages.common-mk: update patches
chromiumOSPackages.common-mk: disable clang-only warnings
chromiumOSPackages.sommelier: drop unneeded patches
chromiumOSPackages.crosvm: add platform2 dep
chromiumOSPackages.crosvm: bump cargoSha256
...-mk-don-t-leak-source-absolute-paths.patch | 14 +-
.../linux/chromium-os/common-mk/default.nix | 6 +-
.../linux/chromium-os/crosvm/default.nix | 3 +-
...melier-use-stable-xdg-shell-protocol.patch | 1748 -----------------
...mmelier-make-building-demos-optional.patch | 100 -
.../linux/chromium-os/sommelier/default.nix | 2 -
.../linux/chromium-os/upstream-info.json | 44 +-
...03-vm_tools-proto-fix-parallel-build.patch | 39 -
.../linux/chromium-os/vm_protos/default.nix | 2 -
pkgs/os-specific/linux/kernel/linux-cros.nix | 6 +-
10 files changed, 40 insertions(+), 1924 deletions(-)
delete mode 100644 pkgs/os-specific/linux/chromium-os/sommelier/0005-sommelier-use-stable-xdg-shell-protocol.patch
delete mode 100644 pkgs/os-specific/linux/chromium-os/sommelier/0006-sommelier-make-building-demos-optional.patch
delete mode 100644 pkgs/os-specific/linux/chromium-os/vm_protos/0003-vm_tools-proto-fix-parallel-build.patch
--
2.31.1
next reply other threads:[~2021-04-02 9:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 9:04 Jamie McClymont [this message]
2021-04-02 23:54 ` Alyssa Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0100017891d36f4f-0c348828-2ed6-4694-b75c-44d0d659c13c-000000@email.amazonses.com \
--to=jamie@kwiius.com \
--cc=devel@spectrum-os.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://spectrum-os.org/git/crosvm
https://spectrum-os.org/git/doc
https://spectrum-os.org/git/mktuntap
https://spectrum-os.org/git/nixpkgs
https://spectrum-os.org/git/spectrum
https://spectrum-os.org/git/ucspi-vsock
https://spectrum-os.org/git/www
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).