From: Randy MacLeod <randy.macleod@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] useradd: do not delete users and groups during configure
Date: Wed, 24 Aug 2016 11:29:23 -0400 [thread overview]
Message-ID: <7d4ba06b-e9d5-a518-68b8-1d5f01ea34bf@windriver.com> (raw)
In-Reply-To: <1471371380-21952-1-git-send-email-jslater@windriver.com>
On 2016-08-16 02:16 PM, Joe Slater wrote:
> If two recipes both create the same users and groups, the
> second recipe can delete items created by the first causing
> things like "chown" to fail for the first recipe.
>
> Signed-off-by: Joe Slater <jslater@windriver.com>
> ---
> meta/classes/useradd.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/useradd.bbclass b/meta/classes/useradd.bbclass
> index 8d51fb5..6df9822 100644
> --- a/meta/classes/useradd.bbclass
> +++ b/meta/classes/useradd.bbclass
> @@ -129,7 +129,7 @@ useradd_sysroot_sstate () {
>
> userdel_sysroot_sstate () {
> if test "x${STAGING_DIR_TARGET}" != "x"; then
> - if [ "${BB_CURRENTTASK}" = "configure" -o "${BB_CURRENTTASK}" = "clean" ]; then
> + if [ "${BB_CURRENTTASK}" = "clean" ]; then
> export PSEUDO="${FAKEROOTENV} PSEUDO_LOCALSTATEDIR=${STAGING_DIR_TARGET}${localstatedir}/pseudo ${STAGING_DIR_NATIVE}${bindir_native}/pseudo"
> OPT="--root ${STAGING_DIR_TARGET}"
>
>
I don't see this in oe-core/master[-next] yet.
Is there a better solution or should the recipes
that create the user (ftp in this case), be modified some how?
--
# Randy MacLeod. SMTS, Linux, Wind River
Direct: 613.963.1350 | 350 Terry Fox Drive, Suite 200, Ottawa, ON,
Canada, K2K 2W5
next prev parent reply other threads:[~2016-08-24 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 18:16 [PATCH 1/1] useradd: do not delete users and groups during configure Joe Slater
2016-08-24 15:29 ` Randy MacLeod [this message]
2016-08-24 21:54 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7d4ba06b-e9d5-a518-68b8-1d5f01ea34bf@windriver.com \
--to=randy.macleod@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox