Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-20 Thread Andersen, Christian
Hi Laurent, > In pyro the creation of users and group (using the useradd class) is done > during > the package pre-installation. > > So my best guess is that you could move the owner/group change in the package > post-installation as follows: thanks for your advice. Currently it seems - as

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-20 Thread Andersen, Christian
Hi Maxin, > > Do I have to add shadow-native in all these recipes or is it a bug / > > regression in > pyro? > > It is one of those "known" limitations which fell through the cracks. > https://bugzilla.yoctoproject.org/show_bug.cgi?id=8078 > > Thanks for bringing this up. We need to address

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-15 Thread Maxin B. John
Hi Christian, On Wed, Jun 14, 2017 at 04:13:04PM +, Andersen, Christian wrote: > Hi Maxin, > > > Here, could you try to build again with an additional DEPENDENCY on shadow- > > native: > > ie: instead of > > >DEPENDS = "puck-base" > > DEPENDS = "puck-base shadow-native" > > > > To be sure,

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-14 Thread Leonardo Sandoval
On Wed, 2017-06-14 at 18:12 +0200, Laurent Gauthier wrote: > Hi Christian, > > In pyro the creation of users and group (using the useradd class) is > done during the package pre-installation. > > So my best guess is that you could move the owner/group change in the > package post-installation as

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-14 Thread Laurent Gauthier
Hi Christian, In pyro the creation of users and group (using the useradd class) is done during the package pre-installation. So my best guess is that you could move the owner/group change in the package post-installation as follows: do_install () { (…) install -d

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-14 Thread Andersen, Christian
Hi Maxin, > Here, could you try to build again with an additional DEPENDENCY on shadow- > native: > ie: instead of > >DEPENDS = "puck-base" > DEPENDS = "puck-base shadow-native" > > To be sure, please cleansstate the puck-base and test before build. Thanks! I tried as you suggested (cleansstate

[yocto] useradd and one sysroot per recipe in pyro

2017-06-14 Thread Andersen, Christian
Any ideas how to use "useradd" bbclass with pyro? If I move useradd to my recipe my-appl.bb, it works. But there are more recipes depending on the added user, so I want to add this user in a base-recipe and just depend on it using (DEPENDS/RDEPENDS). Regards Christian Von: Andersen, Christian

Re: [yocto] useradd and one sysroot per recipe in pyro

2017-06-14 Thread Maxin B. John
Hi Andersen, On Tue, Jun 13, 2017 at 04:10:10PM +, Andersen, Christian wrote: > >Hello, >currently I am trying the newest Yocto release (pyro). It seems I have a >problem >with useradd and the new concept of one sysroot per recipe. > >I have a base recipe (let’s call it my-base.bb) which

[yocto] useradd and one sysroot per recipe in pyro

2017-06-13 Thread Andersen, Christian
Hello, currently I am trying the newest Yocto release (pyro). It seems I have a problem with useradd and the new concept of one sysroot per recipe. I have a base recipe (let's call it my-base.bb) which inherits useradd and creates a new user (let's call him myuser): inherit useradd