[yocto] ptest-runner "No ptests found."

Hi, I am new to Yocto. I am working on ptest-runner. I followed the wiki https://wiki.yoctoproject.org/wiki/Ptest , but when I boot to my image and run ptest-runner I have the output : "No ptests found." Is this normal ? I thought that DISTRO_FEATURES_append = " ptest" and

Re: [yocto] [bitbake-devel] how to store a modification of a bbclass in the poky layer in my own layer.

Hi Christopher, I think I get it now. Thank you so much for your time! Davis On Fri, Aug 17, 2018, 6:57 PM Christopher Larson wrote: > Layer priority as defined by BBFILE_PRIORITY controls recipe selection, > not bbclass and config file parsing. See the bitbake reference manual for > more

Re: [yocto] [bitbake-devel] how to store a modification of a bbclass in the poky layer in my own layer.

Layer priority as defined by BBFILE_PRIORITY controls recipe selection, not bbclass and config file parsing. See the bitbake reference manual for more detail. On Fri, Aug 17, 2018 at 3:54 PM Davis Roman wrote: > Hi Christopher, > > I am very intrigued by your response. > > Initially I had

Re: [yocto] [bitbake-devel] how to store a modification of a bbclass in the poky layer in my own layer.

Your layer has to be before poky/meta in BBLAYERS, as that determines BBPATH, which is how bbclasses and config files are found (much like PATH). On Fri, Aug 17, 2018 at 12:11 PM Davis Roman wrote: > Hello! > > > I've made a modification in poky/meta/classes/libc-package.bbclass ( > shown

[yocto] how to store a modification of a bbclass in the poky layer in my own layer.

Hello! I've made a modification in poky/meta/classes/libc-package.bbclass ( shown below) However I don't want this change to be stored here long term and instead feel that it should live in my project specific layer, meta-hon-grip. After checking with bitbake-layers, I saw that my layer has a

[yocto] QA cycle report for 2.5.1 RC1

Hello All, This is the full report for 2.5.1 RC1: https://wiki.yoctoproject.org/wiki/WW33_-_2018-08-16-_Full_Test_Cycle_-_2.5.1_rc1 === Summary All planned tests were executed except the SDK automated tests were skipped in qemumips (testrun#9868-9869), syslog automated

[yocto] [meta-selinux][PATCH] mcstrans: define SBINDIR to ${D}/${base_sbindir}

From: Mingli Yu Add SBINDIR=${D}/${base_sbindir} to EXTRA_OEMAKE to fix below error when usrmerge enabled in DISTRO_FEATURES. ERROR: QA Issue: mcstrans-dbg package is not obeying usrmerge distro feature. /sbin should be relocated to /usr. [usrmerge] Signed-off-by: Mingli Yu ---

[yocto] Doubts about image "equalness"

Hi, I'm hoping to get opinions on a doubt regarding a certain yocto related problem. We have a following images in place: * production-image.bb * core features, max security * beta-image.bb * require production-image.bb * added logging, reduced security for dev

[yocto] [meta-selinux][PATCH 2/2] policycoreutils: add PACKAGECONFIG for libpam, audit

From: Wenzong Fan * make pam and audit support configurable; * remove INITDIR from EXTRA_OEMAKE, the variable is not supported now. Signed-off-by: Wenzong Fan Signed-off-by: Yi Zhao --- recipes-security/selinux/policycoreutils.inc | 21 ++--- 1 file changed, 14 insertions(+),

[yocto] [meta-selinux][PATCH 1/2] selinux-python: fix installed-vs-shipped QA errors

From: Wenzong Fan Fix the QA errors when enable multilib: ERROR: selinux-python-2.7-r0 do_package: QA Issue: selinux-python: Files/directories were installed but not shipped in any package: /usr/lib /usr/lib/python2.7 /usr/lib/python2.7/site-packages

[yocto] [meta-selinux][resend][PATCH 0/2] meta-selinux fixes

Rebase and resend Wenzong's meta-selinux patches Wenzong Fan (2): selinux-python: fix installed-vs-shipped QA errors policycoreutils: add PACKAGECONFIG for libpam, audit recipes-security/selinux/policycoreutils.inc | 21 ++--- recipes-security/selinux/selinux-python.inc |