[yocto] Reminder: Yocto Project Technical Team Meeting - Tuesday, Mar. 8, 2016 8:00 AM US Pacific Time

Tuesday, Mar. 8, 2016 8:00 AM US Pacific Time Agenda: * Opens collection - 5 min (Stephen) * Yocto Project status - 5 min (Stephen/team) https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.1_Status https://wiki.yoctoproject.org/wiki/Yocto_2.1_Schedule

Re: [linux-yocto] [PATCH 0/1] Fix ftrace missing in -standard BSPs

On 2016-03-07 6:53 PM, California Sullivan wrote: Targetted for 4.4 and master. California Sullivan (1): features/ftrace: set CONFIG_FTRACE=y Looks good to me .. the reliance on implicit selections is something that we've been trying to squash over the years, and this is exactly why! I've

Re: [yocto] [PATCH 01/13] Add include file for the 20160223 SELinux userspace release.

On Tue, Mar 8, 2016 at 3:52 AM, Stephen Smalley wrote: > Signed-off-by: Stephen Smalley > --- > recipes-security/selinux/selinux_20160223.inc | 5 + > 1 file changed, 5 insertions(+) > create mode 100644 recipes-security/selinux/selinux_20160223.inc

[linux-yocto] [PATCH 0/1] Fix ftrace missing in -standard BSPs

Targetted for 4.4 and master. California Sullivan (1): features/ftrace: set CONFIG_FTRACE=y features/ftrace/ftrace.cfg | 1 + 1 file changed, 1 insertion(+) -- 2.5.0 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org

[linux-yocto] [PATCH 1/1] features/ftrace: set CONFIG_FTRACE=y

With EXPERT, EMBEDDED and DEBUG_KERNEL removed from the base, this is no longer being selected by default in in standard BSPs, causing breakage in things that relied on it. Signed-off-by: California Sullivan --- features/ftrace/ftrace.cfg | 1 + 1 file changed,

Re: [yocto] [meta-security][PATCH] samhain-client: Erorr Fix

merged. thanks -armin On 03/06/2016 07:49 PM, Li Xin wrote: > The Error is as following: > # /usr/sbin/samhain -t init -p info > .. > Segmentation fault > # echo $? > 139 > > Signed-off-by: Li Xin > --- > recipes-security/samhain/samhain.inc | 7 ++- >

[yocto] [meta-security][PATCH] libsecomp: update to 2.3.0

Signed-off-by: Armin Kuster --- recipes-security/libseccomp/libseccomp.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/recipes-security/libseccomp/libseccomp.bb b/recipes-security/libseccomp/libseccomp.bb index b197fca..20dfc79 100644 ---

[yocto] [meta-selinux][PATCH 1/1] refpolicy_git: change SRCREV names

When we define several SRCREV_x variables, it is not safe to make any name a subset of another one because SRCREV_FORMAT may be expanded improperly. This occurs only rarely, but it does happen. Signed-off-by: Joe Slater --- recipes-security/refpolicy/refpolicy_git.inc |

Re: [yocto] packages with PKGSIZE 0

I see! This is good information, Ross. Truly appreciate the insight. Thanks ~Sagar From: Burton, Ross [mailto:ross.bur...@intel.com] Sent: Monday, March 7, 2016 1:51 PM To: Bhanagay, Sagar Cc: yocto@yoctoproject.org Subject: Re: [yocto] packages with PKGSIZE 0 On 7 March 2016 at 21:46,

Re: [yocto] packages with PKGSIZE 0

On 7 March 2016 at 21:46, Bhanagay, Sagar wrote: > I was going through the list of packages installed in the image (as per > the manifest file). > > I noticed that metadata information for these packages is present at - > > */build/tmp/sysroots/NAME/pkgdata/runtime/* > >

[yocto] packages with PKGSIZE 0

Hello, I was going through the list of packages installed in the image (as per the manifest file). I noticed that metadata information for these packages is present at - /build/tmp/sysroots/NAME/pkgdata/runtime/ Now I do notice that rarely for a few packages mentioned in the manifest list, the

Re: [yocto] Raspberry Pi 2 BSP build problem

On Mon, Mar 7, 2016 at 9:10 PM, Alan Hughes wrote: > I've been trying to build a BSP using Yocto 2.0 (Jethro) targetting a > Raspberry Pi 2. Everything goes OK until we reach the point of building the > "u-boot-rpi" package, at which point it blows up saying that it

Re: [yocto] Raspberry Pi 2 BSP build problem

This looks like the problem we were experiencing a while back when we were switching from gcc-4x to gcc-5x. If I remember correctly, a certain range of slightly older kernel/u-boot could not be compiled by gcc-5x toolchains without a patch. You could look around for that patch. Or you could

[yocto] [PATCH 11/13] refpolicy: Add support for the SYSTEMD build.conf option.

refpolicy has introduced a new build.conf option, SYSTEMD=y, to enable rules specific to using systemd as the init system. In particular, without setting this option, rules for direct domain transitions from init_t to daemon domains are not included in the policy. Define a POLICY_SYSTEMD variable

[yocto] [PATCH 13/13] libselinux: procattr fixes

selinux upstream commits c7cf5d8aa061b9616bf9d5e91139ce4fb40f532c and f77021d720f12767576c25d751c75cacd7478614 Signed-off-by: Stephen Smalley --- ...bselinux-procattr-return-einval-for-0-pid.patch | 47 ++

[yocto] [PATCH 06/13] policycoreutils: uprev to 2.5 (20160223)

Signed-off-by: Stephen Smalley --- ...cycoreutils-fix-TypeError-for-seobject.py.patch | 27 - .../policycoreutils-pp-builtin-roles.patch | 70 -- ...-process-ValueError-for-sepolicy-seobject.patch | 23 ---

[yocto] [PATCH 05/13] checkpolicy: uprev to 2.5 (20160223)

Signed-off-by: Stephen Smalley --- recipes-security/selinux/checkpolicy.inc| 2 +- recipes-security/selinux/checkpolicy_2.4.bb | 7 --- recipes-security/selinux/checkpolicy_2.5.bb | 7 +++ 3 files changed, 8 insertions(+), 8 deletions(-) delete mode 100644

[yocto] [PATCH 08/13] secilc: Add recipe

SELinux Common Intermediate Language (CIL) policy compiler Signed-off-by: Stephen Smalley --- recipes-security/selinux/secilc.inc| 11 +++ recipes-security/selinux/secilc_2.5.bb | 7 +++ 2 files changed, 18 insertions(+) create mode 100644

[yocto] [PATCH 07/13] sepolgen: uprev to 1.2.3 (20160223)

Signed-off-by: Stephen Smalley --- recipes-security/selinux/sepolgen_1.2.1.bb | 7 --- recipes-security/selinux/sepolgen_1.2.3.bb | 7 +++ 2 files changed, 7 insertions(+), 7 deletions(-) delete mode 100644 recipes-security/selinux/sepolgen_1.2.1.bb create mode

[yocto] [PATCH 04/13] libsemanage: uprev to 2.5 (20160223)

Signed-off-by: Stephen Smalley --- recipes-security/selinux/libsemanage.inc | 3 ++ ...ibsemanage-allow-to-disable-audit-support.patch | 49 ++ recipes-security/selinux/libsemanage_2.4.bb| 19 -

[yocto] [PATCH 03/13] libselinux: uprev to 2.5 (20160223)

Signed-off-by: Stephen Smalley --- ...bselinux-get-pywrap-depends-on-selinux.py.patch | 31 - .../libselinux-make-O_CLOEXEC-optional.patch | 67 ++-- .../libselinux-mount-procfs-before-check.patch | 74 --

[yocto] [PATCH 02/13] libsepol: uprev to 2.5 (release 20160223)

Signed-off-by: Stephen Smalley --- recipes-security/selinux/libsepol_2.4.bb | 9 - recipes-security/selinux/libsepol_2.5.bb | 9 + 2 files changed, 9 insertions(+), 9 deletions(-) delete mode 100644 recipes-security/selinux/libsepol_2.4.bb create mode 100644

[yocto] [PATCH 01/13] Add include file for the 20160223 SELinux userspace release.

Signed-off-by: Stephen Smalley --- recipes-security/selinux/selinux_20160223.inc | 5 + 1 file changed, 5 insertions(+) create mode 100644 recipes-security/selinux/selinux_20160223.inc diff --git a/recipes-security/selinux/selinux_20160223.inc

[yocto] Raspberry Pi 2 BSP build problem

I've been trying to build a BSP using Yocto 2.0 (Jethro) targetting a Raspberry Pi 2. Everything goes OK until we reach the point of building the "u-boot-rpi" package, at which point it blows up saying that it cannot find the file "linux/compiler-gcc5.h". I've looked on the web for any clues,

Re: [yocto] [PATCH] udev: Rename udev bbappend to eudev.

Can someone please let me know what the reasoning behind the switch to eudev? Sincerely, Frederick From: yocto-boun...@yoctoproject.org on behalf of Philip Tricca Sent: Sunday, March 6, 2016 12:08 PM To:

Re: [linux-yocto] FW: [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

On 2016-03-07 2:05 AM, Zheng, Wu wrote: Hi Bruce Ashfield, Our system platform will use linux-yocto-4.4. Therefore, Sending the patch again, It is for linux-yocto-4.4. Thanks. I've merged the change to the 4.4 tree. SRCREV updates will follow in a few days, but if you adjust SRCREVs

Re: [yocto] [meta-selinux][PATCH] busybox: explicitly set temporary shell scripts to be executable

On 03/01/2016 11:43 PM, Philip Tricca wrote: > On 03/01/2016 02:58 PM, Alejandro del Castillo wrote: >> I first started looking at busybox postinst (modified on meta-selinux) since >> I >> am getting errors during "opkg upgrade buysbox". The errors that I am getting >> are of the form: >> >>

Re: [yocto] [meta-selinux][PATCH] audit: upgrade 2.4.4 -> 2.5

On 3/6/16 5:38 PM, Philip Tricca wrote: > Tested this today and it works as expected: thanks! > > This leaves the same PR value as the previous version. The OE style > guide thinks PR should be removed when PV changes. Since we're going > from 2.4.4 -> 2.5 this makes me think that since PV

Re: [yocto] [meta-selinux][PATCH] audit: upgrade 2.4.4 -> 2.5

> From: Philip Tricca [fl...@twobit.us] > Sent: Sunday, March 06, 2016 3:38 PM > To: Radzykewycz, T (Radzy); joe_macdon...@mentor.com; Hatle, Mark > Cc: yocto@yoctoproject.org; Li, Rongqing; Fan, Wenzong > Subject: Re: [meta-selinux][PATCH] audit: upgrade

Re: [yocto] Adding lxc support to image

On 7 March 2016 at 13:52, Biyani Arun (CM/ESC-NA) wrote: > I would like to include lxc style container support in poky image. I added > “meta-virtualization” to my > bblayers.conf. I now get errors when running “bitbake-layers show-recipes”. > > Parsing recipes..ERROR:

[yocto] Adding lxc support to image

I would like to include lxc style container support in poky image. I added "meta-virtualization" to my bblayers.conf. I now get errors when running "bitbake-layers show-recipes". Parsing recipes..ERROR: No recipes available for:

[yocto] [meta-qt3][PATCH] classes: add qmake_base.bbclass

The class was removed from oe classes, but some recipes like qt-x11-free still inherit it. Keep the class within the layer to acommmodate them. Signed-off-by: Adrian Dudau --- classes/qmake_base.bbclass | 119 + 1 file changed,

Re: [yocto] Howto change the default shell in yocto?

On 05/03/16, Burton, Ross wrote: > On 5 March 2016 at 11:48, Oliver Graute wrote: > > > first the default *system* shell (/bin/sh) is this possible? or does this > > affect > > to much of the yoco system itself, if I change /bin/sh to /bin/dash? > > > > bash is only the

Re: [yocto] How to add some additional enviroment variables to /etc/profile file while building IMAGE

On 7 March 2016 at 10:20, Vivek Per wrote: > i want to add some additional enviroment variables in /etc/profile > file. How can i add these while building, so that it reflect in my target > image. > base-files is the recipe that ships /etc/profile, so you can use a

[yocto] How to add some additional enviroment variables to /etc/profile file while building IMAGE

Hi, i want to add some additional enviroment variables in /etc/profile file. How can i add these while building, so that it reflect in my target image. Thanks and regards vivek -- ___ yocto mailing list yocto@yoctoproject.org