linux/poky.git/meta/classes/rootfs-postcommands.bbclass, branch yocto-3.4.3

rootfs-postcommands: amend systemd_create_users add user to group check

2022-03-10T16:39:50+00:00

Currently when adding a user to a group ('m' type), the conditional check to only create a user/group if it does not exist always resolves to true. This causes a build exit failure if the user and/or group defined in the sysusers configuration file were already created prior to the execution of systemd_create_users(). This logic has been updated to instead fail silently (consistent with 'u' and 'g' type). Additionally, if a user doesn't exist it will be created without the default group. (From OE-Core rev: 5f53e232f92011e131abff6128fa25812c3744ac) Signed-off-by: Tean Cunningham Signed-off-by: Richard Purdie (cherry picked from commit 65649be6b2196ab964c69605d0306bfc2481da33) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

rootfs-postcommands.bbclass: Make two comments use the new variable syntax

2022-01-19T11:11:58+00:00

(From OE-Core rev: 5293916ac660c4cfd6304826fb10de1454a40bf5) Signed-off-by: Peter Kjellerstedt Signed-off-by: Richard Purdie (cherry picked from commit cb17cccaf2f51558bd1d320559bd792d5869688e) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

rootfs-postcommands: update systemd_create_users

2021-12-13T23:02:49+00:00

Process all systemd-sysusers configuration files in order to create users/groups at build time. systemd-sysusers would try to create them at run-time, but for read-only rootfs that's not possible and results in warnings from different services: systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:39 Unknown group 'render', ignoring systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:40 Unknown group 'render', ignoring systemd-udevd[166]: /lib/udev/rules.d/50-udev-default.rules:42 Unknown group 'sgx', ignoring (From OE-Core rev: c25d9d2dae45805fa985f1c541cacfb0230f9522) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Richard Purdie (cherry picked from commit f86ffdb1b77c6ba32ec250545a40c1c54f983f21) Signed-off-by: Anuj Mittal Signed-off-by: Richard Purdie

systemd: '${systemd_unitdir}/system' => '${systemd_system_unitdir}'

2021-09-07T20:54:11+00:00

Repo-wide replacement to use newer variable to represent systemd system unitdir directory. (From OE-Core rev: 5ace3ada5c54500c71becc8e0c6eddeb8bc053e3) Signed-off-by: Robert P. J. Day Signed-off-by: Alexandre Belloni Signed-off-by: Richard Purdie

rootfs-postcommands: add QA check for overlayfs

2021-08-12T05:26:15+00:00

The check is conditional and only enabled when overlayfs is set in DISTRO_FEATURES (From OE-Core rev: 4734799bacf0a5d2487e1cde3ae1c00223b032b2) Signed-off-by: Vyacheslav Yurkov Signed-off-by: Richard Purdie

Convert to new override syntax

2021-08-02T14:44:10+00:00

This is the result of automated script conversion: scripts/contrib/convert-overrides.py converting the metadata to use ":" as the override character instead of "_". (From OE-Core rev: 42344347be29f0997cc2f7636d9603b1fe1875ae) Signed-off-by: Richard Purdie

rootfs-postcommands: correctly set systemd target for weston images

2021-03-06T22:39:04+00:00

Otherwise, weston wouldn't actually start when systemd is in use. (From OE-Core rev: 6b6287b7e5190d1af2e3aefddb2f72a8d0d79968) Signed-off-by: Alexander Kanavin Signed-off-by: Richard Purdie

image-artifact-names: introduce new bbclass and move some variables into it

2020-09-17T08:47:45+00:00

* similar to kernel-artifact-names for other recipes/bbclasses which need to use some deployed artifacts * bitbake.conf: move IMAGE_BASENAME, IMAGE_VERSION_SUFFIX, IMAGE_NAME, IMAGE_LINK_NAME variables * image_types.bbclass: move IMAGE_NAME_SUFFIX variable * currently IMAGE_NAME_SUFFIX is used only by image.bbclass, image_types.bbclass and meta/recipes-core/images/build-appliance-image_15.0.0.bb but if it's needed by some recipe which isn't itself an image, then it's useful in bitbake.conf, e.g. we have a recipe for creating VirtualBox appliances which combines .wic.vmdk with .ovf file to create .zip with appliance, but for that we need the filename of .wic.vmdk which now contains IMAGE_NAME_SUFFIX https://github.com/webOS-ports/meta-webos-ports/blob/4980ce52a43ac6897657602810313af359f0b839/meta-luneos/recipes-core/images/luneos-emulator-appliance.inc#L24 * we were hardcoding .rootfs suffix where needed, but for quite long time it's configurable with IMAGE_NAME_SUFFIX since: commit 380ee36811939d947024bf78de907e3c071b834f Author: Patrick Ohly Date: Mon Mar 7 18:07:52 2016 +0100 image creation: allow overriding .rootfs suffix and might not match with hardcoded .rootfs, so make it easier to use IMAGE_NAME_SUFFIX where needed even without inheritting whole image_types.bbclass [YOCTO #12937] (From OE-Core rev: 456b700d51a5052a285a8477304f902c335223be) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie

rootfs-post: remove traling blanks from tasks

2020-07-27T09:37:57+00:00

remove the traling blanks before the ;-delimiter, so one could use "_remove" to avoid running tasks like 'rootfs_update_timestamp', which are currently hardcoded and not bound to any configurable feature flag (From OE-Core rev: 8c835f63c2bca0a66385eb7ea5ec021d86265777) Signed-off-by: Konrad Weihmann Signed-off-by: Richard Purdie

rootfs-postcommands: Improve/fix rootfs_check_host_user_contaminated

2020-07-03T19:17:29+00:00

Currently if the find command finds /home it stops checking the other files. Tweak the find expression to fix this. Also, from Alex Kiernan , generate output for each contaminated path so it's visible in the main log file. When matches are found, dump the data from the group and passwd files so useful debugging can be done based on the results. (From OE-Core rev: 504f1d158bf7c6ad08fbce755021db2b14565231) Signed-off-by: Richard Purdie