IF YOU WOULD LIKE TO GET AN ACCOUNT, please write an
email to Administrator. User accounts are meant only to access repo
and report issues and/or generate pull requests.
This is a purpose-specific Git hosting for
BaseALT
projects. Thank you for your understanding!
Только зарегистрированные пользователи имеют доступ к сервису!
Для получения аккаунта, обратитесь к администратору.
The key has moved to a different location and mkosi needs an update
that we cannot do due to dependency on repart.
(cherry picked from commit 9c9630bfea7cf25d2fe7ba9f7216dc747ba196a5)
It's not required as per comment - https://github.com/systemd/systemd/pull/27110#issuecomment-1499653913
(cherry picked from commit 19cdda7c3a37362df602b3bfd1d2b949cc1f3598)
(cherry picked from commit 7102925d1a9b08cb25e5d8de031c75f29cff0d68)
(cherry picked from commit 77f5c9773379019a6d929b3da95617a75a58e71f)
(cherry picked from commit 9718afd194290228e225a81126988394d167bf7a)
(cherry picked from commit 167c01688f80b97b9f148276b1fb2b601dff6706)
(cherry picked from commit 4857bc61d28f06df373272b73f7c1b4432bffa8b)
follow-up to https://github.com/systemd/systemd/pull/27071
in order to create Github Releases, the job needs permissions to write
contents
also:
- pinned the `softprops/action-gh-release` action to a specific commit
- made it only active on the `systemd` organization repos (so not on
forks)
(cherry picked from commit 7b411cf8421ef3bf6c05edcf131f63b8e7bae8ac)
(cherry picked from commit dc2facf61d80cbb45421d024b56b93fb70e363aa)
(cherry picked from commit 24c3212eaeb48ceb052c66f178da471383c94438)
We have some missing coverage in the CI, all builds enable these features,
but there are often changes and they cover a lot of code. Do one build
without them to ensure we don't break builds.
(cherry picked from commit b7b48b389c5e68154f72133ec5d12ca2412aa406)
(cherry picked from commit 64ef6ccd4fc161159720b5e8db0ba54557df313d)
(cherry picked from commit 01ca822462e8ce6a0fc27c3eebcd509ab5ad8641)
make a github release for every tag that starts with `v*`,
and a pre-release if the tag contains "-rc".
on the 'systemd/systemd' repo, the "Release" will be draft, so that the
release manager can fill up the notes manually.
on 'systemd/systemd-stable' the release will be created immediately.
info about the action used:
https://github.com/softprops/action-gh-release
(cherry picked from commit 86c20937c29da637878a1282444b057bc1a519fb)
(cherry picked from commit a3f2884ef29dee2ace12afe74b9d8d539237a10a)
(cherry picked from commit eae1851b12b727149362570b3d0e62250c59419b)
since the current version of super-linter doesn't recognize
ubuntu-22.04 as a valid runner specification. This should
be fixed once https://github.com/github/super-linter/pull/2897
is merged, which includes
09a60b0f57
(cherry picked from commit 6c0259e50203a9a8851cd4bc6f8e8f8f21361049)
Required to fix Debian testing/unstable builds, as resolved is
now in its own package
(cherry picked from commit 31ed4b91475b5c110dc3e6a50046745be79edbfe)
It's still failing in Ubuntu:
● isc-dhcp-server.service loaded failed failed ISC DHCP IPv4 server
● isc-dhcp-server6.service loaded failed failed ISC DHCP IPv6 server
Just disable them via the kernel command line masking.
(cherry picked from commit 255963ec3a092a3e8b8b0896b45b1ad3ec60f988)
Explicitly enable all features/components in the mkosi build to
ensure they all get built and we get an error if they can't be built.
We also rework the packages sections of all mkosi configs to reduce
duplication and cover all the dependencies necessary to build/use all
systemd features.
Note that for the final image, since systemd is installed by default
in base images, we rely on that to install the base library dependencies
and we only list extra optional dependencies and tools that aren't already
installed by default into the base image.
We also drop the centos stream 8 mkosi build as dependencies on that
distro are too out-of-date to be able to build all systemd features.
Since centos stream 9 has been out for a while, let's focus on that
and leave it to downstream to keep systemd building on centos stream 8.
Finally, there's a few additions to the mkosi scripts to make sure
services don't start by default on boot.
(cherry picked from commit 37d35150cbb5db063aaa8e5878ec03258414b0e5)
The warning isn't that serious and mostly there to inform the user that
lld/mold cannot build efi binaries. It is also better to build test with
fatal meson warnings.
(cherry picked from commit 4fb6506debb851ac062b3b46b46aaa3ac1a17321)
Introduces a more reliable mirror for Arch which should reduce the
number of mkosi Arch CI failures due to unreliable mirror selection.
(cherry picked from commit 599884bd9a3cfb376572e44935174939e0dab776)
With this update, Arch Linux keyring updates will be automatically
pulled in instead of having to update to a new mkosi commit every
time the keyring gets outdated.
(cherry picked from commit 859614439a77da2a69118235a0e78c94c8449aaa)
Fixes an issue with Arch builds failing by updating the archlinux
keyring package.
(cherry picked from commit a41940ed0efc786f60404c5940a664adf047eaab)
This is what's most likely used to build systemd with clang in
practice so let's test it as well.
Preparation for reverting 0bd292567a
(which replaced bogus buffer overflow found with _FORTIFY_SOURCE=3
with actual segfaults).
(cherry picked from commit 36cb69fc43cbce6d883b3a0da4f793c81dbf4b2e)
Allows to 'meson install --tags systemd-boot --no-rebuild' to install only the EFI
binaries, skipping the rest, for a very quick build:
$ ninja src/boot/efi/linuxx64.efi.stub
[21/21] Generating src/boot/efi/linuxx64.efi.stub with a custom command
$ ninja src/boot/efi/systemd-bootx64.efi
[10/10] Generating src/boot/efi/systemd-bootx64.efi with a custom command
$ DESTDIR=/tmp/foo meson install --tags systemd-boot --no-rebuild
Installing src/boot/efi/systemd-bootx64.efi to /tmp/foo/usr/lib/systemd/boot/efi
Requires Meson 0.60 to be used, prints a warning for unknown keyword
in earlier versions, but there's no failure
https://mesonbuild.com/Installing.html#installation-tags
The idea was to catch CFLite regressions but since the action itself
pulls the latest docker images it can't be pinned properly and issues
like https://github.com/google/clusterfuzzlite/issues/91 are going to
pop up anyway. Let's unpin it by analogy with CIFuzz and hope it doesn't
break very often.
