Re: [yocto] [ptest-runner][PATCH v2 4/4] utils: ensure child can be session leader

On Wed, 26 Jun 2019 at 10:56, Randy MacLeod wrote: > On 6/25/19 9:51 PM, Anibal Limon wrote: > > > > > > On Wed, 19 Jun 2019 at 12:50, Randy MacLeod > > wrote: > > > > On 6/14/19 10:48 AM, Randy MacLeod wrote: > > > When running the run-execscript

[yocto] [PATCH 2/2] nss-pam-ldapd: add required distro feature check for pam

From: Mingli Yu As nss-pam-ldapd depends on libpam, it should do required distro feature check for pam. Signed-off-by: Mingli Yu --- recipes-support/nss-pam-ldapd/nss-pam-ldapd_0.9.8.bb | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[yocto] [PATCH 1/2] meta-cloud-services: add layer depends on networking-layer

From: Mingli Yu Since spice of meta-cloud-services depends on cyrus-sasl which comes from networking-layer, add missing layer depends back. Signed-off-by: Mingli Yu --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf b/conf/layer.conf index

Re: [yocto] bitbak command: No recipe available for

Then ensure that the oe-core or poky or whatever provides your meta/ layer is at the same version as the meta-bbb expects. Basically this should all be in the meta-bbb instructions, and if it isn't then ask them. I've never used meta-bbb. Ross On Thu, 27 Jun 2019 at 08:53, danwe wrote: > >

[yocto] bitbak command: No recipe available for

while using the command: daniel@daniel-VirtualBox:~/bbb$ MACHINE=beaglebone bitbake core-immage-full cmdline I get the following ouput: Loading cache: 100% || Time: 0:00:03 Loaded 1358 entries from dependency cache. Parsing recipes: 100%

Re: [yocto] bitbak command: No recipe available for

Set the following in some conf file, e.g. distro.conf, local.conf. BB_DANGLINGAPPENDS_WARNONLY = "true" Best Regards, Chen Qi On 06/27/2019 02:31 PM, danwe wrote: while using the command: daniel@daniel-VirtualBox:~/bbb$ MACHINE=beaglebone bitbake core-immage-full cmdline I get the following

Re: [yocto] bitbak command: No recipe available for

Hi, thank you very much. So now I don't get errors but warnings. So for what do I need those .bbappend files? Are you sure there will be no problems later? Thanks. Daniel Am Do., 27. Juni 2019 um 09:18 Uhr schrieb ChenQi : > Set the following in some conf file, e.g. distro.conf, local.conf. >

Re: [yocto] bitbak command: No recipe available for

On 06/27/2019 03:34 PM, danwe wrote: Hi, thank you very much. So now I don't get errors but warnings. So for what do I need those .bbappend files? Are you sure there will be no problems later? You need to ask the maintainer of meta-bbb. Best Regards, Chen Qi Thanks. Daniel Am Do.,

Re: [yocto] bitbak command: No recipe available for

The problem is that oe-core and meta-bbb are different releases so the versions don't match up. Ensure that oe-core and meta-bbb are on the same branch. Ross On Thu, 27 Jun 2019 at 07:33, danwe wrote: > > while using the command: > daniel@daniel-VirtualBox:~/bbb$ MACHINE=beaglebone bitbake

Re: [yocto] bitbak command: No recipe available for

Hi. Thank you. Could you tell me how I can ensure that these are on the same branch? There is just one meta-bbb I can download... Am Do., 27. Juni 2019 um 09:37 Uhr schrieb Burton, Ross < ross.bur...@intel.com>: > The problem is that oe-core and meta-bbb are different releases so the > versions

Re: [linux-yocto] [PATCH v2] features/security: Add more kernel hardening fragments

On Wed, Jun 26, 2019 at 11:02 PM wrote: > > From: He Zhe > > Signed-off-by: He Zhe > --- > v2: Add a note for people using uvesafb or other similar things. > merged. Bruce > features/security/security.cfg | 18 ++ > 1 file changed, 18 insertions(+) > > diff --git

Re: [linux-yocto] [PATCH] netfilter: Fix remainder of pseudo-header protocol 0

On Tue, Jun 25, 2019 at 11:03 PM He Zhe wrote: > > > > On 6/26/19 11:00 AM, Bruce Ashfield wrote: > > On Tue, Jun 25, 2019 at 6:15 AM wrote: > >> From: He Zhe > >> > >> Since v5.1-rc1, some types of packets do not get unreachable reply with the > >> following iptables setting. Fox example, > >