Qemu-guest-agent gets activated using a udev rule, and so will only run
when the correct virtio-port name is detected. Qemu-guest-agent is used
across several oems so we include it in the usr partition.
Disable ARCH_QCOM, ARCH_ZYNQMP, ARCH_MEDIATEK which enable other options that
are only relevant on the respective boards, none of which are supported targets
for Flatcar. Since the arm64 kernel does not support compression, these
settings have a significant impact on kernel size. The boot partition size is
only 128MB and needs to fit 2 kernels, so we have set ourselves a target of
60MB per kernel. This commit brings down the arm64 kernel size by 3MB.
At the same time, enable the settings that are actually relevant: ARCH_BCM,
because that one is relevant for Raspberry Pi 4 that runs Linux.
No point in setting UPDATE_NEEDED to zero if we exit the script
without doing anything with the just set variable.
Also to avoid mismatches in branch names, export the branch name as a
github workflow step output, so the follow-up steps can pick it up and
use.
No point in setting UPDATE_NEEDED to zero if we exit the script
without doing anything with the just set variable.
Also fix the mismatch in branch names - we normally create a branch
like "cacerts-${NSS_VERSION}-${BRANCH}" in the last workflow step
whereas we were checking if a branch like "${NSS_VERSION}-${BRANCH}"
existed in the script. To avoid repetition, export the branch name as
a github workflow step output, so the follow-up steps can pick it up
and use.
This sets up the coreos-overlay submodule inside the SDK container to
use the remote of the fork and the base branch from that fork. That
way, we can test the workflows in the forks too.
It is quite a bit of data to download for no real reason. We are
trying to update packages here, so we will be grabbing them from the
most recent commit that made the changes to the package. With the
advancement the package updates effort, we possibly can later lower
the number of the fetched commits even further.
Packages (and eclasses) in Gentoo are sometimes moved around or
completely removed. It's good to know about this when it happens,
because such package won't be updated any more, so print a warning.
Packages in the list are not necessarily packages only, which are
represented as directories (like sys-apps/systemd), but also, in case
of eclasses, plain files. The check was checking for the path to be a
directory and emitted the warning if it was not, which resulted in
eclasses being kept not updated. Just check if the path exists.
The workflow was inconsistent with usage of actions/checkout. The
first checkout used v3, whereas the next two - v2. These are the same,
but v3 runs on currently supported node 16. Using v2 emits
warnings. To avoid them, update the action versions to v3.
