Thanks Raj. We are looking at using `sudo` but this may have a ripple effect in our other build scripts. I was hoping there was a more elegant way to handle this.
We are using version Yocto v1.7 ~Ian On Fri, Jun 2, 2017 at 3:14 PM, Khem Raj <raj.k...@gmail.com> wrote: > On Fri, Jun 2, 2017 at 1:57 PM, Ian Welch <ian_we...@trimble.com> wrote: > > Hello, > > We are using the package_ipk.bbclass to create packages for opkg > that > > will be installed on our embedded hardware (target). We are also using > > Jenkins as a CI server to run bitbake. We have discovered that when we > > install packages built on Jenkins we get all kinds of file permissions > > errors after installing the ipks on our target system. I have tracked the > > issue down to bitbake being run by a user called "jenkins" on our Jenkins > > system. The permissions of the files are all "jenkins:jenkins" prior to > the > > do_package task running which results in these permissions getting > packaged > > into the .ipk files. > > > > Is there a way to change the ownership of the files prior to being > packaged? > > I'm thinking of something like a package_ipk.bbappend file or environment > > variable? > > > > pseudo should have taken care of this. > what release are you on ? > > > Cheers, > > > > -- > > > > Ian Welch > > Trimble Navigation > > 10368 Westmoor Drive | Westminster, CO 80021 > > > > > > -- > > _______________________________________________ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > -- Ian Welch Engineering Manager, Civil Engineering & Construction 10368 Westmoor Drive | Westminster, CO 80021 +1-303-635-8750 Direct | +1-720-320-5181 Mobile
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
