Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Mark Hatle <mark.hatle@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Handling of users in multiple recipes.
Date: Fri, 14 Apr 2017 13:20:41 -0500	[thread overview]
Message-ID: <1492194041.27873.4.camel@linux.intel.com> (raw)
In-Reply-To: <7b44de40-fe30-474b-620f-4efec4bf5cac@windriver.com>

On Fri, 2017-04-14 at 12:52 -0500, Mark Hatle wrote:
> On 4/14/17 11:49 AM, Davis, Michael wrote:
> > I have a user that is added in a recipe using inherit useradd.
> > 
> > Previously in Morty I was able to include that recipe as a dependency to other
> > recipes and chown files to that user during do_install.
> > 
> > In checking at master in prep for 2.3 I noticed those recipes no longer work
> > stating the user is invalid.
> > 
> 
> A patch for this issue was added yesterday to oe-core.  I'm not sure if it has
> been merged to master, but should be soon if it has not already been.
> 
> Search the list archives for "base-passwd/useradd: Various improvements to
> useradd with RSS".

Right, in the other hand, the scenario  you are indicating is basically
the same as described in bug 7724
(https://bugzilla.yoctoproject.org/show_bug.cgi?id=7724)

and confirmed that the patch worked.

Leo



> 
> --Mark
> 
> > 
> > Is there a new mechanism in place to handle this use case or am I going to have
> > to find some sort of other work around?
> > 
> >  
> > 
> > Thanks,
> > 
> > Mike
> > 
> >  
> > 
> >  
> > 
> >  
> > 
> > 
> > 
> 




      reply	other threads:[~2017-04-14 18:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-14 16:49 Handling of users in multiple recipes Davis, Michael
2017-04-14 17:52 ` Mark Hatle
2017-04-14 18:20   ` Leonardo Sandoval [this message]

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=1492194041.27873.4.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=mark.hatle@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