Timestamp and user/group information are out, in are device ID and
inode number. That way, the file can be used for accounting size
differences of files/image.
This pulls in the motdgen change
https://github.com/flatcar/init/pull/88
to not create a broken symlink in the symlinked /run/flatcar/ directory
if the directory symlink /run/coreos already exists.
This reverts commit 285f0646e6dfb3381d2ac5555e991cc482a4d91c.
Now that the ebuild dev-lang/rust does not have a manual check for
versions, it is possible to clean up the sed commands in Github
Actions.
Configure with --without=rust-docs-json-preview to avoid failures.
Remove unnecessary checks for package versions like upstream.
Clean up unnecessary patch, add new patch for 1.67.0.
This was a place I missed where /etc/portage is set up. Because of it,
user patches for sys-devel/gcc were not picked up.
Also stop using deprecated PORTDIR and PORTDIR_OVERLAY getters. We
still set those variables, but we will drop them eventually.
Normally `ln -sf path/to/target at/name` will create a symlink at
`at/name` that points to `path/to/target`. But if `at/name` already
exists and is a directory or a symlink to some other directory, then
this command will create a symlink at `at/name/target` pointing to
`path/to/target`. There is an ambiguity between 1st and 3rd form of
`ln` (please refer to `man ln` for the available invocation forms). It
can be disambiguated by using the `-T` flag to force the 1st form.
In our case, if `/etc/portage/patches` symlink already existed and was
pointing to `<coreos-overlay>/coreos/user-patches`, we ended up with a
useless symlink at `<coreos-overlay>/coreos/user-patches/user-patches`
pointing to `<coreos-overlay>/coreos/user-patches`.
Make use of the existing helpers provided by `coreos-go.eclass`.
To optimize the binary size of crictl, add "-X" to GO_LDFLAGS,
like "-X $(PROJECT)/pkg/version.Version=$(VERSION)" in the original
Makefile of cri-tools. We cannot follow way of Gentoo ebuilds like
`emake`, because Makefile of cri-tools does not allow users to pass in
${GOARCH}.
Add `arm64` to ACCEPTED_KEYWORDS.
Remove unnecessary files from installation, as well as the shell
completion eclass.
This pulls in
https://github.com/flatcar/bootengine/pull/52
to reduce the size of the unified kernel image by starting Ignition/
Afterburn from the /usr partition.
This also requires to install the Ignition binary to /usr.
This pulls in
https://github.com/flatcar/baselayout/pull/26
to fix the regression in Alpha/Beta (itself a fix for another
regression) where systemd-tmpfiles bailed if /etc/passwd|group didn't
have the core user, now solved by always copying missing entries over
to the databases, not only if the files didn't exist.
We do specify -split-usr in make.defaults for the USE variable but
it's not enough - the base profile in portage-stable forces this flag
and this overrides our defaults. As a workaround, we were using
package.use.force to force-disable split-usr for selected
packages. Now, with addition of more split-usr-using packages in
app-alternatives the list in package.use.force would grow. Instead of
listing all the packages having split-usr in their IUSE, use the
use.force and use.mask file to unforce and mask split-usr for all
packages in generic images.
As a bonus, this also allows us to drop a customization we did in
sys-apps/policycoreutils package.
This is to fix the following error during stage2 SDK build:
[[ (3/3) Emerging packages ]]
!!! The ebuild selected to satisfy "app-alternatives/yacc" has unmet requirements.
- app-alternatives/yacc-1-r2::portage-stable USE="-bison -byacc -reference"
The following REQUIRED_USE flag constraints are unsatisfied:
exactly-one-of ( bison byacc reference )
(dependency required by "sys-devel/binutils-2.39-r4::portage-stable" [ebuild])
(dependency required by "sys-devel/gcc-11.3.1_p20221209::portage-stable" [ebuild])
(dependency required by "sys-libs/glibc-2.36-r5::coreos" [ebuild])
(dependency required by "sys-libs/glibc:2.2" [argument])
