commit | 6968d7b33455ce2f7b9606a0b49b3c3c08b79df2 | [log] [tgz] |
---|---|---|
author | Stephen Barber <smbarber@chromium.org> | Fri Apr 10 14:16:37 2020 -0700 |
committer | Commit Bot <commit-bot@chromium.org> | Mon Apr 13 23:11:34 2020 +0000 |
tree | 6e3b6d419097188a3c4865ef886bdd0b87b2c24a | |
parent | 61d9c12064b16aa9b3cdb45735d2bde1b087dfaa [diff] |
cros-guest-tools: add xz-utils to recommends xz archives are pretty commonplace now. Add xz-utils so .tar.xz archives can be extracted on default crostini installs. BUG=chromium:1070406 TEST=kokoro Change-Id: I3461a1e3fb1942c511eb4813413b454eb4f48d21 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/containers/cros-container-guest-tools/+/2145972 Commit-Queue: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Auto-Submit: Stephen Barber <smbarber@chromium.org> Reviewed-by: David Munro <davidmunro@google.com>
These are the guest packages for setting up a container to integrate with Chrome OS. This includes build scripts that are run in Google's internal continuous integration service.
The guest packages can be built with Bazel.
bazel build //cros-debs:debs --host_force_python=py2
promote\_apt.sh MILESTONE
and promote\_container.sh MILESTONE
in scripts are used to promote containers from staging to live. NOTE: Whatever is the latest in staging is what gets promoted to live so make sure it's what was tested.