- Jul 29, 2022
-
-
Dylan Aïssi authored
These patches are specific to Apertis because a new version of meson has been backported to Apertis. Signed-off-by:
Dylan Aïssi <dylan.aissi@collabora.com>
-
- Jan 26, 2022
-
-
Detlev Casanova authored
https://phabricator.apertis.org/T7904 Signed-off-by:
Detlev Casanova <detlev.casanova@collabora.com>
-
- Jan 13, 2022
-
-
Ryan Gonzalez authored
https://phabricator.apertis.org/T8162 Signed-off-by:
Ryan Gonzalez <ryan.gonzalez@collabora.com>
-
- May 04, 2021
-
-
Denis Pynkin authored
`stat` doesn't work well due `coreutils-gplv2` created by Debos returning "?" instead of mount point. Fall back to the provided directory, since we have separate partition for "/boot/efi". This change allow to use correct paths for kernel and initrd for entry generation. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- May 03, 2021
-
-
Denis Pynkin authored
Update names for entry directories variables and fix options count. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
Denis Pynkin authored
Fix parameters assignment in `kernel-install` while calling from `update-initramfs` or any package update except kernel. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
Denis Pynkin authored
Commit [cf73f650890](https://github.com/systemd/systemd/commit/cf73f650890 ) provides script `00-entry-directory.install` which creates the entry directory only if `$BOOT/$MACHINE_ID` folder exists. This part was moved out of `kernel-install` script and may introduce the problem during upgrade since before Apertis v2022dev2 we do kernel install with `$MACHINE_ID` generated in a build time. Later we remove `/etc/machine-id` file allowing to generate an unique machine ID during first boot, so there will be no directory `$BOOT/$MACHINE_ID` with a new ID preventing from new entry generation during kernel upgrade in runtime. Hence remove the part checking the `$BOOT/$MACHINE_ID` existence and allow to create the proper entry in any case, returning the previous `kernel-install` behaviour. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
Denis Pynkin authored
Remove negotiation from `-z` to test for non-emptiness instead of previously added version reversing those tests logic. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Apr 26, 2021
-
-
Denis Pynkin authored
- Use [ not [[ and -n to test for non-emptiness Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
Denis Pynkin authored
Fixed syntax of kernel-install script introduced during the merge with newer version from bullseye. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Mar 16, 2021
-
-
Sjoerd Simons authored
- Drop patches from upstream - Refresh remainder Signed-off-by:
Sjoerd Simons <sjoerd@collabora.com>
-
- Mar 12, 2021
-
-
Denis Pynkin authored
Debian's systemd has split-usr enabled as both Debian and in principle Apertis support both a split and a merged-usr setup. This mostly adds search paths to system (e.g. to look at both `/bin/` and `/usr/bin`) however it also means that if `/usr` is a mountpoint system will try to unmount it. Unfortunately this causes issues at shutdown for systems with a merged-usr layout as basic libraries (e.g. libc) are located in `/usr` making it impossible to unmount. For Apertis we don't support `/usr` being a seperate partition, the only time `/usr` is on a mountpoint is when using ostree images (where it is a bind mount and which use a merged-usr layout). So also add `/usr` to the list of paths that are considered unmountable even with split-usr support enabled in systemd. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Mar 09, 2021
-
-
Ritesh Raj Sarraf authored
Drop below patch which is now part of this upstream release apertis/0101-basic-cap-list-parse-print-numerical-capabilities.patch Dropped the below mentioned patches as they are not needed any more apertis/0103-basic-cap-list-reduce-scope-of-variables.patch apertis/0102-basic-capability-util-let-cap_last_cap-return-unsign.patch Signed-off-by:
Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
-
- Nov 17, 2020
-
-
Denis Pynkin authored
The problem with failed `/var` unmount placed on separate partition have a long story: https://github.com/systemd/systemd/issues/867 According messages after the fix integrated into upstream -- there are some corner cases which aren't fully fixed by patches adding [relinquish options](pkg/systemd!26 ) In case of ostree-based images we have a similar issue since `/var` is bind-mounted in initramfs. Systemd is trying to unmount `/var` on shutdown, however `ExecStop=` command from `systemd-journal-flush` service is not executed during shutdown. By adding `PartOf=var.mount` into service file we force the `systemd-journal-flush.service` to be called prior the `/var` unmount. This allow to unlock the bind-mount, since `journald` have a chance to re-link it's journal into `/run` with `journalctl --smart-relinquish-var` call. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Nov 01, 2020
-
-
Denis Pynkin authored
Backported PR 16424 to avoid message 'Failed to parse bus message: Invalid argument' with an updated kernel using new capabilities. Signed-off-by:
Denis Pynkin <denis.pynkin@collabora.com>
-
- Sep 03, 2020
-
-
Martyn Welch authored
Newer version of systemd-journald support the --relinquish and --smart-relinquish options that enable cleaner handling of mounts at shutdown as journald can be told to close any logging under /var/log/journal so that the /var filesystem can be unmounted should it be on a separate partition. Backport this feature as it enables shutdown without failures, a highly desirable trait in embedded products using systemd. The significant changes from the upstream patches are: * Including `util.h` rather than `errno-util.h`, as the functionality hasn't been split out into a separate header file in our version. https://gitlab.apertis.org/pkg/target/systemd/-/merge_requests/26/diffs#10b30dfe96faf3663f42076bdb4984ccdea14817_0_88 - Adding `ERRNO_IS_ACCEPT_AGAIN` to `varlink.c` (the header file it's expected to be in doesn't exist in our version) https://gitlab.apertis.org/pkg/target/systemd/-/merge_requests/26/diffs#10b30dfe96faf3663f42076bdb4984ccdea14817_0_93 - Working around the changed parameters for `JSON_VARIANT_OBJECT_FOREACH`, adding a call to `json_variant_string()`, based on how upstream was modified when the macro changed https://gitlab.apertis.org/pkg/target/systemd/-/merge_requests/26/diffs#10b30dfe96faf3663f42076bdb4984ccdea14817_0_772 - Expanding the code around `inotify_add_watch()` which got factored out to a function in newer versions of systemd https://gitlab.apertis.org/pkg/target/systemd/-/merge_requests/26/diffs#f4174ac09c9ebd5278fe22a02b6207223a00f92e_0_74 Signed-off-by:
Martyn Welch <martyn.welch@collabora.com>
-
- Aug 15, 2019
-
-
Frédéric Dalleau authored
Signed-off-by:
Frédéric Dalleau <frederic.dalleau@collabora.com>
-
- Aug 12, 2019
-
-
Ritesh Raj Sarraf authored
Signed-off-by:
Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
-
- Aug 08, 2019
-
-
Ritesh Raj Sarraf authored
Refresh patches against the latest bashism changes from Buster. Also, ignore some additional code related to INITRD_OPTIONS Signed-off-by:
Ritesh Raj Sarraf <ritesh.sarraf@collabora.com>
-
- Jun 01, 2019
-
-
Ritesh Raj Sarraf authored
-