linux/poky.git/meta/classes/useradd.bbclass, branch krogoth-enea

useradd: Fix infinite build loop

2016-09-29T10:00:51+00:00

http://git.openembedded.org/openembedded-core-contrib/commit/?id=642c6cf0b6a0371de476513162bd0cefa9c438b3 introduces a problem if the USERADD_PARAM variable has trailing whitespace as the code infinitely loops causing build hangs. Add a similar sed expression to $remaining to avoid this. (From OE-Core rev: d6241e4c94a0a72acfc57e96a59918c0b2146d65) (From OE-Core rev: 0900fed3fb6eec62e9e25f6d03af934f9776d105) Signed-off-by: Richard Purdie Signed-off-by: Denys Dmytriyenko Signed-off-by: Richard Purdie

useradd.bbclass: Strip trailing ';' in cmd params

2016-09-27T08:05:57+00:00

When there are more than 1 packages in a recipe requiring useradd services, they are concatnated and a ';' is inserted just after each of the users being added by the packages. A situation arises in cases where this is controlled by PACKAGECONFIG then we add a ';' separator in the USERADD_PARAM value itself for each packagecofig since we do not know which one will be picked, we end up in situation where the final string returned from get_all_cmd_params() appears to be a; ; b; c; and then the logic which uses these cmds triggers with ';' as separator but in this case it will fail after executing useradd 'a' because the next cmd it will call will be just a whitespace This is highlighted by the systemd patch to add more users as needed by systemd 229 components. (From OE-Core rev: e8d4356c38e3c2aacd6dc49231c73bcb7d597308) (From OE-Core rev: 4f69a4be79e17ef009351c447694e46b5cb517c2) Signed-off-by: Khem Raj Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

useradd: use bindir_native for pseudo PATH

2016-09-27T08:05:57+00:00

* useradd/userdel functions will fail for recipes which override their target prefix (e.g. to /opt/foo), because it will try to use pseudo from native-sysroot/opt/foo/bin/pseudo (From OE-Core rev: 96189e71a86c0f4833e8e51d678208fd908bfe30) (From OE-Core rev: fe20ce64de7a3d8bcd21bb1fc2cfd65563b82767) Signed-off-by: Martin Jansa Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

useradd.bbclass: remove user/group created by the package in clean* task

2016-04-06T21:57:25+00:00

At present, if a recipe is built which creates users/groups via useradd.bbclass, those users/groups are not removed from sysroot when the recipe/package is cleaned using clean/cleansstate/cleanall or when a recipe is rebuild and 'unstaged' from the the sysroot. The "userdel_sysroot_sstate()" provides that functionality. [YOCTO #9262] (From OE-Core rev: b5304ce438666a7418746f4ddd32703ae3188089) Signed-off-by: Maxin B. John Signed-off-by: Richard Purdie

useradd_base.bbclass: replace retry logic with flock

2016-03-20T23:12:27+00:00

When perform useradd during populate sysroot, it locks files passwd.lock and group.lock at same time. And then it meets a dead lock issue randomly. Use flock to reslove it by using an universal lock directory for all the user and group related operations. [YOCTO #9022] (From OE-Core rev: 2ebf697b46c42cee8bfa6d2e6087397f8cce385c) Signed-off-by: Kai Kang Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

classes/useradd: handle whitespace only USERADD/GROUPADD/GROUPMEMS

2016-02-11T12:27:44+00:00

Useradd attempts to add users/groups even when {USERADD,GROUPADD,GROUPMEMS}_PARAM is whitespace only. This scenario is possible when variables and modified using one of +=, =+ operator, yet the content being added is conditional (i.e. may depend on PACKAGECONFIG flags). (From OE-Core rev: 466288d528cce5f9887d765a757af64c9cc6be03) Signed-off-by: Maciej Borzecki Signed-off-by: Richard Purdie

classes/useradd: don't read bbnote/bbwarn/bbfatal values

2015-07-16T14:09:23+00:00

Since these functions now log through BitBake's message logging system we must have standalone implementations here. (From OE-Core rev: dd7449114a33c92a2877b1a6f875d812b10856ff) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie

meta: Add explict getVar param for (non) expansion

2015-06-23T10:57:25+00:00

Rather than just use d.getVar(X), use the more explict d.getVar(X, False) since at some point in the future, having the default of expansion would be nice. This is the first step towards that. This patch was mostly made using the command: sed -e 's:$getVar([^,()]*$\s*):\1, False):g' -i `grep -ril getVar *` (From OE-Core rev: ab7c1d239b122c8e549e8112c88fd46c9e2b061b) Signed-off-by: Richard Purdie

useradd.bbclass: Remove base-passwd dependency

2015-05-16T21:31:51+00:00

shadow-sysroot (another useradd dependency) recipe already includes base-passwd dependency, so removing it from useradd class. This fixes the compilation issue observed when a recipe depends on another where the latter inherits from useradd as in the following scenario: https://bugzilla.yoctoproject.org/show_bug.cgi?id=7724#c0 [Yocto #7724] (From OE-Core rev: a68a797c7aec607a0720ec5421baf6be821803b8) Signed-off-by: Leonardo Sandoval Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

useradd.bbclass: avoid do_rootfs error for debian package backend

2015-02-17T22:35:03+00:00

If /etc/login.defs is treated as a configuration file, then we would meet errors at do_rootfs time telling us that useradd/groupadd cannot execute correctly. This is because the dpkg handles config file specially, the login.defs is temporarily renamed as login.defs.dpkg-new. How ubuntu deals the user/group adding problem? They do it at postinst of the package. And, the postinst script of a package would possibly do `chown' of its files or directories. The above strategy is not suitable for OE. Because we do chown in do_install and add user/group in preinst scripts of the packages. That's why we need this patch so that do_rootfs don't fail. (From OE-Core rev: d98e5ec575f542b3afaabd96b07ae9a21e1c22f4) Signed-off-by: Chen Qi Signed-off-by: Richard Purdie