gcc has been stabilized for arm64 for 11.3.1_p20230120-r1 so we can drop
our profile change for the same.
Signed-off-by: Sayan Chowdhury <schowdhury@microsoft.com>
curl has been stabilized for arm64 for 7.87.0-r2 so we can drop
our profile change for the same.
Signed-off-by: Sayan Chowdhury <schowdhury@microsoft.com>
glib has been stabilized for arm64 for 2.74.4 so we can drop
our profile change for the same.
Signed-off-by: Sayan Chowdhury <schowdhury@microsoft.com>
This pulls in
https://github.com/flatcar/init/pull/90
to fix the dummy interface exclusion rule in the default networkd unit.
It was supposed to work before but didn't. With it we wouldn't have
needed the special exclusions for Kubernetes interfaces.
This pulls in
https://github.com/flatcar/init/pull/89
to set the Kubernetes interfaces nodelocaldns and kube-ipvs0 as
Unmanaged in networkd to prevent configuration conflicts.
The ebuild uses python eclasses, which dropped support for EAPI 6
after the update. Updating EAPI required replacing the use of the
versionator eclass as it's banned in EAPI 7 or later. Fortunately,
nothing in the ebuild seemed to use anything from the eclass.
I changed the way we modify the ebuild by keeping the modifications as
minimal as possible, leaving disabling whatever that can be disabled
to the USE flags.
This is a thing that needs to be done just this once. The necessary
modifications to the python-oem ebuild will be done in follow-up
commit, that can be later cherry-picked if we update the package
again.
This is a thing that needs to be done just this once. The necessary
modifications to the python-oem ebuild will be done in follow-up
commit, that can be later cherry-picked if we update the package
again.
- Drop the init.d files.
- Remove the socket unit's rate limiting.
- Mark the package as stable.
Signed-off-by: Sayan Chowdhury <schowdhury@microsoft.com>
Signed-off-by: Dongsu Park <dpark@linux.microsoft.com>
Since the new USE flag `cet` became the default in profiles of
portage-stable, SDK bootstrap using gcc 11.3.1_p20221209 started
to fail at `sys-libs/glibc`.
```
in function `dl_open_worker_begin':
dl-open.c:(.text+0xab4c): undefined reference to `_dl_cet_open_check'
```
That is because gcc is not correctly configured for CET.
That issue was fixed in recent upstream GCC versions,
e.g. 11.3.1_p20221209-r1 or 11.3.1_p20230120-r1.
https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=016184c289f2cc6c6ade496a700a12f135fbae07https://gitweb.gentoo.org/proj/gcc-patches.git/commit/?id=15daf0510a5fab17cd556261d688a6618391a0c1
However, gcc of Flatcar, 11.3.1_p20221209, does not have the fix.
Update sys-devel/gcc to 11.3.1_p20230120-r1 to fix that issue.
Also accept ~arm64 to keep the same version for both arches.
- remove unecessary files
- drop `pkg_postint`
- create `/etc/ssl` with tmpfiles
- mark openssl as stable for arm64 and amd64
- continue shipping app-misc/c_rehash
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Dongsu Park <dpark@linux.microsoft.com>
The boot log only showed the unit descriptions which made it hard to
know what unit was meant.
Switch to the combined unit status reporting that includes the unit
name.
