It's from Gentoo commit 3d3624f4ebb26b9fc9c9ecbff7ff0c67b3f9aa4f.
We used to have it as a fork to replace cmake-based build system with
an autotools-based one. The reason was that we didn't provide cmake in
SDK, which is not true any more.
I seem to have problems with getting a network connectivity inside
QEMU vm when running the tests in the azure machine. I don't know
what's the cause, but for the dev container tests these problems can
be worked around by using the locally provided dev container
image. Make it possible by specifying QEMU_DEVCONTAINER_FILE in the
environment.
The mountpoint for the OEM partition got moved from /usr/share/oem to
/oem to avoid complications when applying a OEM sysext image in the
OEM partition - systemd was unmounting all the mountpoints under /usr
before applying the sysext, which made our OEM images unavailable.
There's still the /usr/share/oem symlink for compatibility, but it's
better to use the new location right away.
Use Go 1.19 as Go 1.12 does not exist.
Update amazon-ssm-agent to 3.2.985.0, because 2.3.1319.0 does not work
with Go 1.19.
Clean up unnecessary patches.
Update dev-lang/go-bootstrap to 1.18.6, by syncing with Gentoo commit
1b3154a4473deedaf3d1deb978f9a19739ac03af.
This is necessary because Go >= 1.20 requires go-bootstrap to be at
least 1.17.13.
Drop unnecessary Flatcar patches from go-bootstrap, and move the ebuild
from coreos-overlay to portage-stable.
Go 1.18 is already EOL, so no security update at all. Since
upstream docker projects already have Go 1.19, Flatcar should also have
that.
See also
5d6db84223/Dockerfile (L6).
Since Go 1.20 stopped shipping pre-compiled package archives for the
standard library in $GOROOT/pkg, it became impossible to install
pkg/linux_{amd64,arm64} for every version. To avoid build failure,
install the library if the Go slot number is 1.19 or older.
Also depend on go-bootstrap 1.17.13 or newer.
See also https://go.dev/doc/go1.20.
Update the default Go version from 1.19 to the latest 1.20.
Note, we still keep setting COREOS_GO_VERSION="go1.19" for
containerd, cri-tools, docker, docker-cli, docker-proxy, docker-runc,
following the default version of upstream projects.
Without DRM configured in the Linux kernel, the VNC console will show a
screen with the message: "Display output is not active".
Although the on QEMU-KVM AMD64 the issue is not presented, I have
enabled the same flags for consistency.
Fixes: https://github.com/flatcar/Flatcar/issues/1030
This change includes 2 unrelated small fixes to the "PR comment command"
build+test feature:
1. The concurrency group now contains the PR number, ensuring that
builds for multiple PRs can run in parallel. This addresses an issue
in which starting a build on a PR would cancel a running build of
another PR.
2. Post test results to the PR where the build command was issued on.
The add-pr-comment step's condition was not updated when switching
to PR comment commands for starting builds, so the step would only
run if the action was triggered by a PR change event. Since we now
trigger on issue_comment, the step never ran.
Signed-off-by: Thilo Fromm <thilofromm@microsoft.com>
- Fix the snapshot name, it is not "portage-${VERSION}", but rather
"gentoo-${VERSION}".
- After building the snapshot, remove all the similar files from the
snapshots directory - Catalyst gets easily confused by them and
bails out.
- Extend the `build_snapshot` function to optionally accept the config
path and the snapshot name, so SDK's stage1 code can use this
function instead of duplicating parts of it.
