Date   

Re: Trouble using initramfs

Anuj Mittal
 

On Thu, 2019-08-15 at 19:12 -0300, Antonio Teixeira wrote:
Hello.

I've been having trouble with loading initramfs on boot when the
initramfs is bundled with the kernel image.
I've been using the following options in local.conf:
INITRAMFS_IMAGE = "core-image-minimal-initramfs"
INITRAMFS_IMAGE_BUNDLE = "1"

I'm using the linux-intel kernel from the meta-intel layer, however,
when booting, the kernel simply doesn't load the initramfs.

If I set INITRAMFS_IMAGE_BUNDLE to "0", copy the generated initramfs
image to the boot partition, and then point grub to the external
initramfs.cpio.gz image using the initrd option in the boot entry
config, the kernel loads it fine and everything works.
Which branch are you using? Can you try the latest master with wic?
There was a fix to wic to allow copying the kernel image with bundled
initramfs to boot partition instead of the one without when
INITRAMFS_IMAGE_BUNDLE is 1.

Thanks,

Anuj


Trouble using initramfs

Antonio Teixeira
 

Hello.

I've been having trouble with loading initramfs on boot when the initramfs is bundled with the kernel image.
I've been using the following options in local.conf:
INITRAMFS_IMAGE = "core-image-minimal-initramfs"
INITRAMFS_IMAGE_BUNDLE = "1"

I'm using the linux-intel kernel from the meta-intel layer, however, when booting, the kernel simply doesn't load the initramfs.

If I set INITRAMFS_IMAGE_BUNDLE to "0", copy the generated initramfs image to the boot partition, and then point grub to the external initramfs.cpio.gz image using the initrd option in the boot entry config, the kernel loads it fine and everything works.

I'm booting in a x86_64 computer (not an embedded device) using these instructions:

https://wiki.yoctoproject.org/wiki/How_do_I#Q:_How_do_I_put_Yocto_on_a_hard_drive.3F

Am I missing something? Do I need to set some other kernel parameters? Is there any way I can check if the resulting kernel image indeed has an initramfs bundled with it?


Re: please help on compiling my kernel

Randy MacLeod
 

On 8/13/19 5:59 AM, Tg, Harish wrote:
Hi Guys,
                 I am facing a strange issue which was working/compiling earlier. I did a clean and retried. Now I am getting this error with the command “bitbake -c compile -f linux-ti-staging”:
WARNING: linux-ti-staging-4.4.45+gitAUTOINC+89944627d5-r1a.arago5 do_fetch: Failed to fetch URL git://git.omapzoom.org/kernel/omap;protocol=git;branch=p-ti-lsk-linux-4.4.y-next, attempting MIRRORS if available
ERROR: linux-ti-staging-4.4.45+gitAUTOINC+89944627d5-r1a.arago5 do_fetch: Fetcher failure: Fetch command failed with exit code 128, output:
fatal: Not a git repository (or any parent up to mount point /mnt/yocto)
Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).
ERROR: linux-ti-staging-4.4.45+gitAUTOINC+89944627d5-r1a.arago5 do_fetch: Function failed: Fetcher failure for URL: 'git://git.omapzoom.org/kernel/omap;protocol=git;branch=p-ti-lsk-linux-4.4.y-next'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /mnt/yocto/yocto_repo/build/arago-tmp-external-linaro-toolchain/work/delphi_jlr_isp_proto-linux-gnueabi/linux-ti-staging/4.4.45+gitAUTOINC+89944627d5-r1a.arago5/temp/log.do_fetch.102021
ERROR: Task 2 (/mnt/yocto/yocto_repo/sources/meta-ti/recipes-kernel/linux/linux-ti-staging_4.4.bb, do_fetch) failed with exit code '1'
Kindly help with this. Thanks.

Likely the server was just down for a while.

Both the web site:
http://git.omapzoom.org/?p=kernel/omap.git;a=summary
and:
$ git clone -b p-ti-lsk-linux-4.4.y-next git://git.omapzoom.org/kernel/omap.git omap.git
Cloning into 'omap.git'...
remote: Counting objects: 6410683, done.
remote: Compressing objects: 100% (1028266/1028266), done.
Receiving objects: 100% (6410683/6410683), 1.54 GiB | 2.62 MiB/s, done.
remote: Total 6410683 (delta 5337468), reused 6409647 (delta 5336439)
Resolving deltas: 100% (5337468/5337468), done.
Checking out files: 100% (52679/52679), done.
rmacleod@ala-lpggp2$echo $?
0

work for me now.

Do you have a firewall blocking your internet access?
I don't have this problems thankfully but if you do, it looks
like there are some good recommendations here:

https://stackoverflow.com/questions/4891527/git-protocol-blocked-by-company-how-can-i-get-around-that

Of course you should abide by your corporate download policies.
Oh and some vendors provide full copies of all source when you install
their Yocto-based products.

../Randy

Regards,
Harish.

--
# Randy MacLeod
# Wind River Linux


Re: wic create - bad ownership of directories inside image

Randy MacLeod
 

On 8/12/19 5:11 AM, Behnke, Jochen wrote:
Hello,
I am using poky 2.6.1 (thud) and create images using the wic utility.
Recently I noticed that all directories contained in the created image are owned by UID 1000 and not by root. The files inside the image however are owned by root.
The UID 1000 refers to my unprivileged user on the host system.
Here is the command I use to create the image
“wic create mkefidisk –e core-image-minimal”
The images created by bitbake directly (.tar.bz2, .hddimg) are correct so this seems to be a wic related problem.
Does anybody have a solution for this?
Hi Jochen,

No and I've never seen this particular extreme symptom.

There is a known, generally rare bug:
Bug 12434 - pseudo: Incorrect UID/GID in packaged files
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12434
but that usually shows up when building.

You could check you build logs for the generic stings from:

glibc-locale-2.26: glibc-locale:
/glibc-binary-localedata-en-gb/usr/lib/locale/en_GB/LC_MEASUREMENT
is owned by uid 3004, which is the same as the user running bitbake.
This may be due to host contamination [host-user-contaminated]


Is your issue 100% reproducible?

../Randy


Many thanks in advance, any hint is appreciated.
Regards
Jochen
<gfidisc.SID=010500000000000515000000993c4a7a4675257c8b2de024250d0000>
__________________________________
*SCHMIDT Technology GmbH*
Feldbergstrasse 1
78112 St. Georgen/Germany
Telefon +49 (0) 77 24 / 89 90
Fax +49 (0) 77 24 / 89 91 01
info@schmidttechnology.de <mailto:info@schmidttechnology.de>
http://www.schmidttechnology.de
USt-Id Nr. DE 811725105 · Registergericht Freiburg HRB 600 755
Geschaeftsfuehrung: Oliver Schmidt, Stephan Schmidt
<gfidisc.SID=010500000000000515000000993c4a7a4675257c8b2de024250d0000>

--
# Randy MacLeod
# Wind River Linux


Re: Segmentation fault | bitbake machine-image.bb | core dumped

Randy MacLeod
 

On 8/12/19 10:42 AM, jaymin.dabhi@vivaldi.net wrote:
Hello All,
Facing segmentation fault (core dumped) while doing bitbake.
I am using Yocto Jethro branch.
Jethro isn't officially supported by the Yocto Project.
The support cycle is ~ 1 year.

https://wiki.yoctoproject.org/wiki/Releases

Can you reproduce the issue on master or a newer supported branch?
If so you could file a bug in:
https://wiki.yoctoproject.org/wiki/Releases

Also, see below for some tips.

When I added python3-pip recipe (in local.conf) and started building image, segmentation fault occurred.
Although, I am able to bitbake python3-pip individually (i.e. bitbake python3-pip).
As per log my assumption is, core dumped is occurring at make_ext4fs execution.
Following are the error logs:
ERROR: Function failed: do_makesystem (log file is located at poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059) ERROR: Logfile of failure stored in: poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059 Log data follows:
| DEBUG: Executing shell function do_makesystem
| poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/run.do_makesystem.15059: line 105: 15073 Segmentation fault      (core dumped) make_ext4fs -J -b 1024 -s -a / -S
Odd, I've never see that happen before.
Is it reproducible?

Can you adjust the core file limits using 'ulimit',
generate a core file and get a backtrace?

poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs/etc/selinux/mls/contexts/files/file_contexts -l 768000000 poky/build/tmp-glibc/deploy/images/apq8053-perf/apq8053-sysfs.ext4 poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs
| WARNING: poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/run.do_makesystem.15059:1 exit 139 from
|   make_ext4fs -J -b 1024 -s -a / -S poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs/etc/selinux/mls/contexts/files/file_contexts -l 768000000 poky/build/tmp-glibc/deploy/images/apq8053-perf/apq8053-sysfs.ext4 poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/rootfs
| ERROR: Function failed: do_makesystem (log file is located at poky/build/tmp-glibc/work/apq8053-oe-linux/machine-image/1.0-r0/temp/log.do_makesystem.15059) ERROR: Task 11 ( poky/meta-qti-bsp/recipes-products/images/machine-image.bb, do_makesystem) failed with exit code '1'
Whether python3-pip recipe is creating an issue or something else? (attached the python3-pip recipe file)
What did you change in your conf/local.conf file?
If you revert that change, then you are able to generate the image
again?

../Randy

Please let me know.
Any suggestions are welcome.
Regards,
Jaymin

--
# Randy MacLeod
# Wind River Linux


Re: Init stops working on second boot cycle

Randy MacLeod
 

On 8/13/19 6:21 AM, Andy Pont wrote:
I’ve got a strange issue and I don’t know whether it is a Yocto related issue, a kernel issue or something else completely…
I have an image that is built with thud (2.6.2) using meta-atmel for the SAMA5D2-Xplained reference board.  I deploy the resulting .wic file to an SD card and boot the reference board and all is OK.  I can log into the terminal, upload files, etc. and again all seems to be well.
If I press the reset button on the hardware platform, on the next boot cycle it always stops with the following being last messages being displayed:
Freeing unused kernel memory: 1024K
Run /sbin/init as init process
INIT: version 2.88 booting
The system hasn’t completely hung as the occasional kernel message appears but the user space init process (sysvinit) doesn’t seem to be
What sort of occasional kernel message and do they eventually stop?

working at all.  If I put the SD card into a Linux desktop machine the file system on it is still valid and the changes that I have made are still present.
Anyone got any ideas as to what is screwing it up?
No but here are some generic debugging tips.
In no particular order, have you tried:

1) setting kernel boot options such as:
init=/bin/bash

Does that reboot consistently when you press reset?

2) getting sysvinit to start an emergency shell?
https://manpages.debian.org/testing/sysvinit-core/init.8.en.html
I don't know how you'd do that for your board but is
should be possible.

3) single user mode:
https://wiki.gentoo.org/wiki/Sysvinit#Single_user_mode

4) Does the problem happen if you run 'shutdown -r now'
rather than pressing the reset button?

Good luck,

--
# Randy MacLeod
# Wind River Linux


Re: Bitbake local.conf variable been override by weak assignment

Rick Liu
 

oops~
After I purged build/tmp and build/cache,
it just works,
so it's probably just cache issue.

# $BRCM_NXT-RELEASE-216_BRANCH [2 operations]
# set /home/rl891036/scrach/DHELPDESK-3176/poky/build/conf/local.conf:60
# "SIT_int_nxt_v216.1.15.0"
# set? /home/rl891036/scrach/DHELPDESK-3176/poky/build/../meta-brcm/meta-datacenter/recipes-kernel/nxt-l2-drv/brcm-nxt-l2-drv_nxtrelease.bb:10
# "RICK"
# pre-expansion value:
# "SIT_int_nxt_v216.1.15.0"
BRCM_NXT-RELEASE-216_BRANCH="SIT_int_nxt_v216.1.15.0"

On Wed, Aug 14, 2019 at 1:18 PM Rick Liu <rick.liu@broadcom.com> wrote:

I have defined a global default value BRCM_NXT-RELEASE-216_BRANCH in local.conf,
and setup a weak assignment (?=) in my recipe,
but somehow the weak assignment override the local.conf global default value.
Does anyone have any idea?

build/conf/local.conf:
BRCM_NXT-RELEASE-216_BRANCH = "SIT_int_nxt_v216.1.15.0"
PREFERRED_VERSION_brcm-nxt-l2-drv = "nxtrelease%"

meta-brcm/meta-datacenter/recipes-kernel/nxt-l2-drv/brcm-nxt-l2drv_nxtrelese.bb:
BRCM_NXT-RELEASE-216_BRANCH ?= "RICK"

$ bitbake -e brcm-nxt-l2-drv
# $BRCM_NXT-RELEASE-216_BRANCH [2 operations]
# set /home/rl891036/scrach/DHELPDESK-3176/poky/build/conf/local.conf:60
# [_defaultval] "SIT_int_nxt_v216.1.15.0"
# set? /home/rl891036/scrach/DHELPDESK-3176/poky/build/../meta-brcm/meta-datacenter/recipes-kernel/nxt-l2-drv/brcm-nxt-l2-drv_nxtrelease.bb:10
# "RICK"
# pre-expansion value:
# "RICK"
BRCM_NXT-RELEASE-216_BRANCH="RICK"


Bitbake local.conf variable been override by weak assignment

Rick Liu
 

I have defined a global default value BRCM_NXT-RELEASE-216_BRANCH in local.conf,
and setup a weak assignment (?=) in my recipe,
but somehow the weak assignment override the local.conf global default value.
Does anyone have any idea?

build/conf/local.conf:
BRCM_NXT-RELEASE-216_BRANCH = "SIT_int_nxt_v216.1.15.0"
PREFERRED_VERSION_brcm-nxt-l2-drv = "nxtrelease%"

meta-brcm/meta-datacenter/recipes-kernel/nxt-l2-drv/brcm-nxt-l2drv_nxtrelese.bb:
BRCM_NXT-RELEASE-216_BRANCH ?= "RICK"

$ bitbake -e brcm-nxt-l2-drv
# $BRCM_NXT-RELEASE-216_BRANCH [2 operations]
# set /home/rl891036/scrach/DHELPDESK-3176/poky/build/conf/local.conf:60
# [_defaultval] "SIT_int_nxt_v216.1.15.0"
# set? /home/rl891036/scrach/DHELPDESK-3176/poky/build/../meta-brcm/meta-datacenter/recipes-kernel/nxt-l2-drv/brcm-nxt-l2-drv_nxtrelease.bb:10
# "RICK"
# pre-expansion value:
# "RICK"
BRCM_NXT-RELEASE-216_BRANCH="RICK"


Unable to build Yocto meta-freescale layer for NXP

Sayan Sinha <sayan.sinha@...>
 

Hello everyone,

  I was trying to build Yocto for my NXP. I tried building the Meta Freescale layer (meta-freescale - Layer containing NXP hardware support metadata). As mentioned in the Yocto Project Quick Build page, I added the Meta Freescale layer to bitbake using `bitbake-layers add-layer ../meta-freescale-2.2`. Unfortunately, when I run `bitbake meta-freescale-2.2`, I get an error message

```
ERROR: ParseError at ~/poky/meta/classes/image.bbclass:18: Could not inherit file classes/image_types_uboot.bbclass | ETA: 0:00:06

Summary: There were 3 WARNING messages shown.
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
```
Any insights on this would be constructive. I would also like to mention that my final aim is to build Yocto (with RTOS support, preferably using Litmus RT) for NXP SBC-S32V234.

Thanks a lot in advance!


[meta-raspberrypi] Issues building bcm2835_bootfiles in Thud

Phillip Marks <pmarks@...>
 

We are building Thud for a raspberry-pi0+wifi and we've noticed that the recipe bcm2835_bootfiles under meta-raspberrypi/recipes-bsp/bootfiles is not pulling in the proprietary *.dtb modules from the firmware repository. This is causing linux-raspberrypi to fail as it tries to build those modules and fails on "no target found for bcm2708-rpi-0-w.dtb". How does bcm2835_bootfiles pull in the Broadcom firmware modules and where in build does it store them? We don't see them in tmp/work. 

- Phillip Marks


Re: [patchtest][PATCH V2] patchtest: fix linux-yocto version

Changqing Li
 

Hi, Richard

This patchset need to be merged.

patchtest: fix linux-yocto version

and patchtest: fix virtio-9p-pci is not a valid device


Thanks

On 6/13/19 5:16 PM, changqing.li@windriver.com wrote:
From: Changqing Li <changqing.li@windriver.com>

4.9 is not avaiable currently, so remove version from bbappend
and remove PREFERRED_VERSION.

Signed-off-by: Changqing Li <changqing.li@windriver.com>
---
.../linux/{linux-yocto_4.%.bbappend => linux-yocto_%.bbappend} | 0
scripts/create-guest-machine | 5 -----
2 files changed, 5 deletions(-)
rename meta-patchtest/recipes-kernel/linux/{linux-yocto_4.%.bbappend => linux-yocto_%.bbappend} (100%)

diff --git a/meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend b/meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
similarity index 100%
rename from meta-patchtest/recipes-kernel/linux/linux-yocto_4.%.bbappend
rename to meta-patchtest/recipes-kernel/linux/linux-yocto_%.bbappend
diff --git a/scripts/create-guest-machine b/scripts/create-guest-machine
index 8dd6a2e..8381ef8 100755
--- a/scripts/create-guest-machine
+++ b/scripts/create-guest-machine
@@ -145,11 +145,6 @@ cat >> $POKY/build/conf/auto.conf << EOF
$PTSMARK
MACHINE = "$MACHINE"
-# The preferred kernel version in poky (4.10%, master) returns an error whilst
-# executing patchtest on guest. Changing the preferred version to 4.9% as it
-# is more suitable and does not present any errors.
-PREFERRED_VERSION_linux-yocto_qemux86-64 = "4.9%"
-
PACKAGE_CLASSES = "package_ipk"
IMAGE_FSTYPES = "ext4"
SSTATE_MIRRORS ?= "file://.* http://sstate.yoctoproject.org/dev/PATH"
--
BRs

Sandy(Li Changqing)


Re: [PATCH][thud] meta-yocto-bsp: Bump to the latest stable kernel for the BSPs

Armin Kuster
 



On 8/12/19 8:48 PM, Kevin Hao wrote:
On Fri, Apr 19, 2019 at 01:23:35PM +0800, Kevin Hao wrote:
In order to fix a systemtap bug [1] on arm board, we backport a kernel
patch from v5.0 kernel to v4.14 & v4.18 kernel, then need to bump the
kernel version to include this patch. Even this is only an arm specific
bug, we would like to bump the kernel version for the BSPs at the same
time. Boot test for all the boards.

[1] https://bugzilla.yoctoproject.org/show_bug.cgi?id=13273
Hi Armin,

Could you help merge this patch to thud branch?
yes. It is now on my list.

Thanks,
Armin

Thanks,
Kevin

Signed-off-by: Kevin Hao <kexin.hao@...>
---
 .../recipes-kernel/linux/linux-yocto_4.14.bbappend   | 20 ++++++++++----------
 .../recipes-kernel/linux/linux-yocto_4.18.bbappend   | 20 ++++++++++----------
 2 files changed, 20 insertions(+), 20 deletions(-)

diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
index 502485a94b15..426757e48c9e 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.14.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86    ?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
-SRCREV_machine_genericx86-64 ?= "2c5caa7e84311f2a0097974a697ac1f59030530e"
-SRCREV_machine_edgerouter ?= "e06bfa18c727bd0e6e10cf26d9f161e4c791f52b"
-SRCREV_machine_beaglebone-yocto ?= "b8805de77dcf8f59d8368fee4921c146c1300a6a"
-SRCREV_machine_mpc8315e-rdb ?= "f88e87360b10f8fbd853a7d412982e6620f3f96d"
+SRCREV_machine_genericx86    ?= "5252513a39b4b3773debab1f77071d7c430ecb10"
+SRCREV_machine_genericx86-64 ?= "5252513a39b4b3773debab1f77071d7c430ecb10"
+SRCREV_machine_edgerouter ?= "d8fb40cd0e99325715c70aed6f361a8318097829"
+SRCREV_machine_beaglebone-yocto ?= "c67809688bd22cb4cb909bcf1a1045e6337c3229"
+SRCREV_machine_mpc8315e-rdb ?= "258ee8228e0a512c6dbe2a0dadcd9f030ba45964"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.14.76"
-LINUX_VERSION_genericx86-64 = "4.14.76"
-LINUX_VERSION_edgerouter = "4.14.71"
-LINUX_VERSION_beaglebone-yocto = "4.14.71"
-LINUX_VERSION_mpc8315e-rdb = "4.14.71"
+LINUX_VERSION_genericx86 = "4.14.98"
+LINUX_VERSION_genericx86-64 = "4.14.98"
+LINUX_VERSION_edgerouter = "4.14.98"
+LINUX_VERSION_beaglebone-yocto = "4.14.98"
+LINUX_VERSION_mpc8315e-rdb = "4.14.98"
diff --git a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
index 7f15843f3a90..11b35cc1c2f8 100644
--- a/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
+++ b/meta-yocto-bsp/recipes-kernel/linux/linux-yocto_4.18.bbappend
@@ -8,11 +8,11 @@ KMACHINE_genericx86 ?= "common-pc"
 KMACHINE_genericx86-64 ?= "common-pc-64"
 KMACHINE_beaglebone-yocto ?= "beaglebone"
 
-SRCREV_machine_genericx86    ?= "db2d813869a0501782469ecdb17e277a501c9f57"
-SRCREV_machine_genericx86-64 ?= "db2d813869a0501782469ecdb17e277a501c9f57"
-SRCREV_machine_edgerouter ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
-SRCREV_machine_beaglebone-yocto ?= "28e7781d57a59227bf1c08c7f3dbdfee16aa0dc2"
-SRCREV_machine_mpc8315e-rdb ?= "99071a599d8650b069fb8135866fca203f375350"
+SRCREV_machine_genericx86    ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_genericx86-64 ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_edgerouter ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_beaglebone-yocto ?= "b24d9d2146d4ce4ef3ad7251b936f35c69dcf0c4"
+SRCREV_machine_mpc8315e-rdb ?= "0802dc980cbc8bdb156d6fe305e7b88e6b602634"
 
 COMPATIBLE_MACHINE_genericx86 = "genericx86"
 COMPATIBLE_MACHINE_genericx86-64 = "genericx86-64"
@@ -20,8 +20,8 @@ COMPATIBLE_MACHINE_edgerouter = "edgerouter"
 COMPATIBLE_MACHINE_beaglebone-yocto = "beaglebone-yocto"
 COMPATIBLE_MACHINE_mpc8315e-rdb = "mpc8315e-rdb"
 
-LINUX_VERSION_genericx86 = "4.18.22"
-LINUX_VERSION_genericx86-64 = "4.18.22"
-LINUX_VERSION_edgerouter = "4.18.25"
-LINUX_VERSION_beaglebone-yocto = "4.18.25"
-LINUX_VERSION_mpc8315e-rdb = "4.18.25"
+LINUX_VERSION_genericx86 = "4.18.35"
+LINUX_VERSION_genericx86-64 = "4.18.35"
+LINUX_VERSION_edgerouter = "4.18.35"
+LINUX_VERSION_beaglebone-yocto = "4.18.35"
+LINUX_VERSION_mpc8315e-rdb = "4.18.35"
-- 
2.14.4




[meta-security][PATCH 2/2] linux-yocto-dev: update to use kernel cache

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-kernel/linux/linux-yocto-dev.bbappend | 13 ++-----------
1 file changed, 2 insertions(+), 11 deletions(-)

diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend b/recipes-kernel/linux/linux-yocto-dev.bbappend
index 68b2b8b..239e30e 100644
--- a/recipes-kernel/linux/linux-yocto-dev.bbappend
+++ b/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -1,11 +1,2 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/linux-yocto-5.0:"
-
-SRC_URI += "\
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor_on_boot.cfg', '', d)} \
-"
-
-SRC_URI += "\
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack-default-lsm.cfg', '', d)} \
-"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "apparmor", " features/apparmor/apparmor.scc", "" ,d)}"
++KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "smack", " features/smack/smack.scc", "" ,d)}"
--
2.17.1


[meta-security][PATCH 1/2] linux-yocto: use 4.19 kernel cache now

Armin Kuster
 

remove kernel fragments now that they are in the
kernel-cache for 4.19

update bbappend accordingly.

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-kernel/linux/linux-yocto/apparmor.cfg | 15 ---------------
.../linux/linux-yocto/apparmor_on_boot.cfg | 1 -
.../linux/linux-yocto/smack-default-lsm.cfg | 2 --
recipes-kernel/linux/linux-yocto/smack.cfg | 8 --------
recipes-kernel/linux/linux-yocto/yama.cfg | 1 -
recipes-kernel/linux/linux-yocto_4.%.bbappend | 13 ++-----------
6 files changed, 2 insertions(+), 38 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-yocto/apparmor.cfg
delete mode 100644 recipes-kernel/linux/linux-yocto/apparmor_on_boot.cfg
delete mode 100644 recipes-kernel/linux/linux-yocto/smack-default-lsm.cfg
delete mode 100644 recipes-kernel/linux/linux-yocto/smack.cfg
delete mode 100644 recipes-kernel/linux/linux-yocto/yama.cfg

diff --git a/recipes-kernel/linux/linux-yocto/apparmor.cfg b/recipes-kernel/linux/linux-yocto/apparmor.cfg
deleted file mode 100644
index b5f9bb2..0000000
--- a/recipes-kernel/linux/linux-yocto/apparmor.cfg
+++ /dev/null
@@ -1,15 +0,0 @@
-CONFIG_AUDIT=y
-# CONFIG_NETFILTER_XT_TARGET_AUDIT is not set
-CONFIG_SECURITY_NETWORK=y
-# CONFIG_SECURITY_NETWORK_XFRM is not set
-CONFIG_SECURITY_PATH=y
-# CONFIG_SECURITY_SELINUX is not set
-CONFIG_SECURITY_APPARMOR=y
-CONFIG_SECURITY_APPARMOR_HASH=y
-CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
-# CONFIG_SECURITY_APPARMOR_DEBUG is not set
-CONFIG_INTEGRITY_AUDIT=y
-CONFIG_DEFAULT_SECURITY_APPARMOR=y
-# CONFIG_DEFAULT_SECURITY_DAC is not set
-CONFIG_DEFAULT_SECURITY="apparmor"
-CONFIG_AUDIT_GENERIC=y
diff --git a/recipes-kernel/linux/linux-yocto/apparmor_on_boot.cfg b/recipes-kernel/linux/linux-yocto/apparmor_on_boot.cfg
deleted file mode 100644
index fc35740..0000000
--- a/recipes-kernel/linux/linux-yocto/apparmor_on_boot.cfg
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
diff --git a/recipes-kernel/linux/linux-yocto/smack-default-lsm.cfg b/recipes-kernel/linux/linux-yocto/smack-default-lsm.cfg
deleted file mode 100644
index b5c4845..0000000
--- a/recipes-kernel/linux/linux-yocto/smack-default-lsm.cfg
+++ /dev/null
@@ -1,2 +0,0 @@
-CONFIG_DEFAULT_SECURITY="smack"
-CONFIG_DEFAULT_SECURITY_SMACK=y
diff --git a/recipes-kernel/linux/linux-yocto/smack.cfg b/recipes-kernel/linux/linux-yocto/smack.cfg
deleted file mode 100644
index 62f465a..0000000
--- a/recipes-kernel/linux/linux-yocto/smack.cfg
+++ /dev/null
@@ -1,8 +0,0 @@
-CONFIG_IP_NF_SECURITY=m
-CONFIG_IP6_NF_SECURITY=m
-CONFIG_EXT2_FS_SECURITY=y
-CONFIG_EXT3_FS_SECURITY=y
-CONFIG_EXT4_FS_SECURITY=y
-CONFIG_SECURITY=y
-CONFIG_SECURITY_SMACK=y
-CONFIG_TMPFS_XATTR=y
diff --git a/recipes-kernel/linux/linux-yocto/yama.cfg b/recipes-kernel/linux/linux-yocto/yama.cfg
deleted file mode 100644
index 3b55731..0000000
--- a/recipes-kernel/linux/linux-yocto/yama.cfg
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SECURITY_YAMA=y
diff --git a/recipes-kernel/linux/linux-yocto_4.%.bbappend b/recipes-kernel/linux/linux-yocto_4.%.bbappend
index 321392c..39d4e6f 100644
--- a/recipes-kernel/linux/linux-yocto_4.%.bbappend
+++ b/recipes-kernel/linux/linux-yocto_4.%.bbappend
@@ -1,11 +1,2 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}:"
-
-SRC_URI += "\
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor_on_boot.cfg', '', d)} \
-"
-
-SRC_URI += "\
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack-default-lsm.cfg', '', d)} \
-"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "apparmor", " features/apparmor/apparmor.scc", "" ,d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "smack", " features/smack/smack.scc", "" ,d)}"
--
2.17.1


[meta-security][PATCH 3/3] linux-stable/5.2: add stable bbappend

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-kernel/linux/linux-stable_5.2.bbappend | 4 ++++
1 file changed, 4 insertions(+)
create mode 100644 recipes-kernel/linux/linux-stable_5.2.bbappend

diff --git a/recipes-kernel/linux/linux-stable_5.2.bbappend b/recipes-kernel/linux/linux-stable_5.2.bbappend
new file mode 100644
index 0000000..76b5df5
--- /dev/null
+++ b/recipes-kernel/linux/linux-stable_5.2.bbappend
@@ -0,0 +1,4 @@
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "apparmor", " features/apparmor/apparmor.scc", "" ,d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "smack", " features/smack/smack.scc", "" ,d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "yama", " features/yama/yama.scc", "" ,d)}"
+
--
2.17.1


[meta-security][PATCH 2/3] meta-integrity: remove kernel fragments now in cache

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
.../recipes-kernel/linux/linux-%.bbappend | 5 ++---
.../recipes-kernel/linux/linux/ima.cfg | 18 ------------------
.../linux/linux/ima_evm_root_ca.cfg | 3 ---
.../recipes-kernel/linux/linux/modsign.cfg | 5 -----
.../recipes-kernel/linux/linux/modsign.scc | 4 ----
5 files changed, 2 insertions(+), 33 deletions(-)
delete mode 100644 meta-integrity/recipes-kernel/linux/linux/ima.cfg
delete mode 100644 meta-integrity/recipes-kernel/linux/linux/ima_evm_root_ca.cfg
delete mode 100644 meta-integrity/recipes-kernel/linux/linux/modsign.cfg
delete mode 100644 meta-integrity/recipes-kernel/linux/linux/modsign.scc

diff --git a/meta-integrity/recipes-kernel/linux/linux-%.bbappend b/meta-integrity/recipes-kernel/linux/linux-%.bbappend
index ca96c8d..f9a48cd 100644
--- a/meta-integrity/recipes-kernel/linux/linux-%.bbappend
+++ b/meta-integrity/recipes-kernel/linux/linux-%.bbappend
@@ -1,6 +1,5 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/linux:"
+KERNEL_FEATURES_append = " ${@bb.utils.contains("DISTRO_FEATURES", "ima", " features/ima/ima.scc", "" ,d)}"

-SRC_URI += "${@bb.utils.contains('DISTRO_FEATURES', 'ima', ' file://ima.cfg', '', d)}"
-SRC_URI += "${@bb.utils.contains('DISTRO_FEATURES', 'modsign', ' file://modsign.scc file://modsign.cfg', '', d)}"
+KERNEL_FEATURES_append = " ${@bb.utils.contains('DISTRO_FEATURES', 'modsign', ' features/ima/modsign.scc', '', d)}"

inherit ${@bb.utils.contains('DISTRO_FEATURES', 'modsign', 'kernel-modsign', '', d)}
diff --git a/meta-integrity/recipes-kernel/linux/linux/ima.cfg b/meta-integrity/recipes-kernel/linux/linux/ima.cfg
deleted file mode 100644
index b3e47ba..0000000
--- a/meta-integrity/recipes-kernel/linux/linux/ima.cfg
+++ /dev/null
@@ -1,18 +0,0 @@
-CONFIG_IMA=y
-CONFIG_IMA_MEASURE_PCR_IDX=10
-CONFIG_IMA_NG_TEMPLATE=y
-CONFIG_IMA_DEFAULT_TEMPLATE="ima-ng"
-CONFIG_IMA_DEFAULT_HASH_SHA1=y
-CONFIG_IMA_DEFAULT_HASH="sha1"
-CONFIG_IMA_APPRAISE=y
-CONFIG_IMA_APPRAISE_BOOTPARAM=y
-CONFIG_IMA_TRUSTED_KEYRING=y
-CONFIG_SIGNATURE=y
-CONFIG_IMA_WRITE_POLICY=y
-CONFIG_IMA_READ_POLICY=y
-CONFIG_IMA_LOAD_X509=y
-CONFIG_IMA_X509_PATH="/etc/keys/x509_ima.der"
-
-#CONFIG_INTEGRITY_SIGNATURE=y
-#CONFIG_INTEGRITY_ASYMMETRIC_KEYS=y
-#CONFIG_INTEGRITY_TRUSTED_KEYRING=y
diff --git a/meta-integrity/recipes-kernel/linux/linux/ima_evm_root_ca.cfg b/meta-integrity/recipes-kernel/linux/linux/ima_evm_root_ca.cfg
deleted file mode 100644
index 9a45425..0000000
--- a/meta-integrity/recipes-kernel/linux/linux/ima_evm_root_ca.cfg
+++ /dev/null
@@ -1,3 +0,0 @@
-# CONFIG_IMA_APPRAISE_SIGNED_INIT is not set
-CONFIG_EVM_LOAD_X509=y
-CONFIG_EVM_X509_PATH="/etc/keys/x509_evm.der"
diff --git a/meta-integrity/recipes-kernel/linux/linux/modsign.cfg b/meta-integrity/recipes-kernel/linux/linux/modsign.cfg
deleted file mode 100644
index c0c4ebc..0000000
--- a/meta-integrity/recipes-kernel/linux/linux/modsign.cfg
+++ /dev/null
@@ -1,5 +0,0 @@
-CONFIG_MODULE_SIG=y
-CONFIG_MODULE_SIG_FORCE=y
-CONFIG_MODULE_SIG_SHA256=y
-CONFIG_MODULE_SIG_HASH="sha256"
-CONFIG_MODULE_SIG_KEY="modsign_key.pem"
diff --git a/meta-integrity/recipes-kernel/linux/linux/modsign.scc b/meta-integrity/recipes-kernel/linux/linux/modsign.scc
deleted file mode 100644
index bce78ae..0000000
--- a/meta-integrity/recipes-kernel/linux/linux/modsign.scc
+++ /dev/null
@@ -1,4 +0,0 @@
-define KFEATURE_DESCRIPTION "Kernel Module Signing (modsign) enablement"
-define KFEATURE_COMPATIBILITY all
-
-kconf non-hardware modsign.cfg
--
2.17.1


[meta-security][PATCH 1/3] linux-%: remove kernel fragments now in cache

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-kernel/linux/linux-%.bbapend | 9 ---------
recipes-kernel/linux/linux/apparmor.cfg | 9 ---------
recipes-kernel/linux/linux/apparmor_on_boot.cfg | 1 -
recipes-kernel/linux/linux/smack-default-lsm.cfg | 2 --
recipes-kernel/linux/linux/smack.cfg | 7 -------
5 files changed, 28 deletions(-)
delete mode 100644 recipes-kernel/linux/linux-%.bbapend
delete mode 100644 recipes-kernel/linux/linux/apparmor.cfg
delete mode 100644 recipes-kernel/linux/linux/apparmor_on_boot.cfg
delete mode 100644 recipes-kernel/linux/linux/smack-default-lsm.cfg
delete mode 100644 recipes-kernel/linux/linux/smack.cfg

diff --git a/recipes-kernel/linux/linux-%.bbapend b/recipes-kernel/linux/linux-%.bbapend
deleted file mode 100644
index ec7adeb..0000000
--- a/recipes-kernel/linux/linux-%.bbapend
+++ /dev/null
@@ -1,9 +0,0 @@
-FILESEXTRAPATHS_prepend := "${THISDIR}/linux:"
-
-SRC_URI += "\
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' file://apparmor_on_boot.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack-default-lsm.cfg', '', d)} \
- ${@bb.utils.contains('DISTRO_FEATURES', 'yama', ' file://yama.cfg', '', d)} \
-"
diff --git a/recipes-kernel/linux/linux/apparmor.cfg b/recipes-kernel/linux/linux/apparmor.cfg
deleted file mode 100644
index ae6cdcd..0000000
--- a/recipes-kernel/linux/linux/apparmor.cfg
+++ /dev/null
@@ -1,9 +0,0 @@
-CONFIG_AUDIT=y
-CONFIG_SECURITY_PATH=y
-CONFIG_SECURITY_APPARMOR=y
-CONFIG_SECURITY_APPARMOR_HASH=y
-CONFIG_SECURITY_APPARMOR_HASH_DEFAULT=y
-CONFIG_INTEGRITY_AUDIT=y
-CONFIG_DEFAULT_SECURITY_APPARMOR=y
-CONFIG_DEFAULT_SECURITY="apparmor"
-CONFIG_AUDIT_GENERIC=y
diff --git a/recipes-kernel/linux/linux/apparmor_on_boot.cfg b/recipes-kernel/linux/linux/apparmor_on_boot.cfg
deleted file mode 100644
index fc35740..0000000
--- a/recipes-kernel/linux/linux/apparmor_on_boot.cfg
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SECURITY_APPARMOR_BOOTPARAM_VALUE=1
diff --git a/recipes-kernel/linux/linux/smack-default-lsm.cfg b/recipes-kernel/linux/linux/smack-default-lsm.cfg
deleted file mode 100644
index b5c4845..0000000
--- a/recipes-kernel/linux/linux/smack-default-lsm.cfg
+++ /dev/null
@@ -1,2 +0,0 @@
-CONFIG_DEFAULT_SECURITY="smack"
-CONFIG_DEFAULT_SECURITY_SMACK=y
diff --git a/recipes-kernel/linux/linux/smack.cfg b/recipes-kernel/linux/linux/smack.cfg
deleted file mode 100644
index 0d5fc64..0000000
--- a/recipes-kernel/linux/linux/smack.cfg
+++ /dev/null
@@ -1,7 +0,0 @@
-CONFIG_NETLABEL=y
-CONFIG_SECURITY_NETWORK=y
-# CONFIG_SECURITY_NETWORK_XFRM is not set
-CONFIG_SECURITY_SMACK=y
-CONFIG_SECURITY_SMACK_BRINGUP=y
-CONFIG_SECURITY_SMACK_APPEND_SIGNALS=y
-CONFIG_TMPFS_XATTR=y
--
2.17.1


[yocto-announce] [ANNOUNCEMENT] Yocto Project 2.6.3 (thud 20.0.3) Released

Vineela
 

Hello All,

We are pleased to announce the Yocto Project 2.6.3 (thud-20.0.3) Release is now available for download.

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/poky-thud-20.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.3/poky-thud-20.0.3.tar.bz2

A gpg signed version of these release notes is available at:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/RELEASENOTES

Full Test Report:

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/testreport.txt

Thank you for everyone's contributions to this release.

Sincerely,

Vineela Tummalapalli
Yocto Project Build and Release
vineela.tummalapalli@intel.com

------------------
yocto-2.6.3 Errata
--------------------

Release Name: poky-thud-20.0.3
Branch: thud
Tag: thud-20.0.3
Hash: cb26830f765f03309c0663352cc5849491271be8
md5: 1489c2ea6743790147f88037f70e483a
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/poky-thud-20.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.3/poky-thud-20.0.3.tar.bz2

Release Name: meta-mingw-thud-20.0.3
Branch: thud
Tag: thud-20.0.3
Hash: 6556cde16fbdf42c7edae89bb186e5ae4982eff5
md5: 5d646b155cba75c4dd3d7cb4d165bd03
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/meta-mingw-thud-20.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.3/meta-mingw-thud-20.0.3.tar.bz2

Release Name: meta-intel-thud-20.0.3
Branch: thud
Tag: thud-20.0.3
Hash: 278f0b5fa2f1836635178bdc770e035d77ae03c7
md5: 08be18666a3e960c261de8b5fe443ca4
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/meta-intel-thud-20.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.3/meta-intel-thud-20.0.3.tar.bz2

Release Name: meta-gplv2-thud-20.0.3
Branch: thud
Tag: thud-20.0.3
Hash: aabc30f3bd03f97326fb8596910b94639fea7575
md5: 363b9acecc2ee20714eab435a343250b
Download Locations:
http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.3/meta-gplv2-thud-20.0.3.tar.bz2
http://mirrors.kernel.org/yocto/yocto/yocto-2.6.3/meta-gplv2-thud-20.0.3.tar.bz2


---------------
Known Issues
---------------
Core-image-sato-sdk image installed on NUC7 internal harddisk leads to hang at the Yocto splash screen during bootup.
To exit the splash screen hang state and continue to boot to sato UI, manually press the enter key multiple times.


---------------
Security Fixes
---------------
expat: fix CVE-2018-20843
libcroco: fix CVE-2017-7961
ghostscript: Fix 3 CVEs
bzip2: fix CVE-2019-12900
gstreamer1.0-plugins-base: fix CVE-2019-9928
libsdl: CVE fixes
glib: Security fix for CVE-2019-9633
qemu: Security fixes CVE-2018-20815 CVE-2019-9824
glibc: backport CVE fixes
lighttpd: fix CVE-2019-11072
qemu: Security fix for CVE-2019-12155
Curl: Securiyt fix CVE-2019-5435 CVE-2019-5436
wget: Security fix for CVE-2019-5953
glib-2.0: Security fix for CVE-2019-12450
Tar: Security fix CVE-2019-0023
qemu: Security fix for CVE-2018-19489
cairo: fix CVE-2018-19876 CVE-2019-6461 CVE-2019-6462
sqlite3: Security fixes for CVE-2018-20505 & 20506
busybox: Security fixes for CVE-2018-20679 CVE-2019-5747
python: add a fix for CVE-2019-9948 and CVE-2019-9636
qemu: Several CVE fixes
elfutils: Security fixes CVE-2019-7146,7149,7150
glibc: Security fix CVE-2019-9169
ruby: remove CVE-2018-1000073.patch as already fixed
avahi: fix CVE-2017-6519
libexif: fix CVE-2016-6328 and CVE-2018-20030
libsndfile1: fix CVE-2019-3832
bluez5: fix CVE-2018-10910
python: fix CVE-2018-14647 in python-native too
openssl: follow OE's rule for specifying CVE ID
openssl: fix CVE-2019-1543


---------------
Fixes
---------------
build-appliance-image: Update to thud head revision
poky.conf: Bump version for 2.6.3 thud release
libarchive: integrate security fixes
OpkgPM: use --add-ignore-recommends to process BAD_RECOMMENDATIONS
opkg: add --ignore-recommends flag
scripts: Remove deprecated imp module usage
uboot-sign.bbclass: Remove tab indentations in python code
uninative: Update to 2.6 release
uninative: Switch from bz2 to xz
yocto-uninative: Update to 2.5 release
wpa_supplicant: Changed systemd template units
go: update to minor update 1.11.10
go: Upgrade 1.11.1 -> 1.11.4 minor release
go-crosssdk: PN should use SDK_SYS, not TARGET_ARCH
go-target.inc: fix go not found while multilib enabled
cups: upgrade to 2.2.10
cups: upgrade to 2.2.9
file: Multiple Secruity fixes
python: Update to 2.7.16
ref-manual: Fixed typo for BBMULTICONFIG variable.
bsp-guide: Fixed build error.
bsp-guide: Minor edits to Configuring Kernel section.
bsp.xml: Updated some output examples and the BSP structure
brief-yoctoprojectqs: Updated examples.
Documentation: Prepare for 2.6.3 release.
bitbake: gitsm: Add need_update method to determine when we are going to a new SRCREV
bitbake: gitsm: Fix a bug where the wrong path was used for the submodule init
bitbake: bitbake: fix version comparison when one of the versions ends in .
bitbake: bitbake: cooker: Rename __depends in all multiconfigs
bitbake: toaster: Fix Thud Bitbake release metadata
core-image-sato-sdk-ptest: Tweak size to stay within 4GB limit
core-image-sato-sdk-ptest: Try and keep image below 4GB limit
wic/bootimg-efi: replace hardcoded volume name with label
resulttool: Add option to dump all ptest logs
wic: change expand behaviour to match docs
recipetool: fix unbound variable when fixed SRCREV can't be found
resulttool/manualexecution: Enable test case configuration option
resultool/resultutils: Fix module import error
resulttool: Add log subcommand
resulttool: Load results from URL
resulttool/manualexecution: Refactor and remove duplicate code
resulttool/manualexecution: Enable creation of configuration option file
oeqa/targetcontrol.py: fix qemuparams not work in runqemu with launch_cmd
oeqa/target/ssh: Replace suggogatepass with ignoring errors
oeqa/sdk: use bash to execute SDK test commands
oeqa/concurrenttest: Patch subunit module to handle classSetup failures
oeqa/runner: Fix subunit setupClass/setupModule failure handling
oeqa/core/runner: Handle unexpectedSucesses
oeqa/ssh: Avoid unicode decode exceptions
oeqa/core/runner: dump stdout and stderr of each test case
oeqa/utils/qemurunner: Fix typo in previous commit
oeqa/qemurunner: Dont mix binary and non-binary strings
opkg-utils: backport a patch to fix a sstate timestamp issue
adwaita-icon-theme: do not delete symbolic svg but pack them in ${PN}-symbolic
runqemu: do not check return code of tput
image_types.bbclass: fix a race between the ubi and ubifs FSTYPES
e2fsprogs: Skip slow ptest tests
ruby: add ptest
ruby: make ext module fiddle can compile success
ruby.inc: Add dependency on readline-native
recipetool: add missed module
pseudo: Update to gain key bugfixes
resulttool/manualexecution: Enable configuration options selection
linux-yocto/4.18: update to v4.18.33
linux-yocto-tiny/4.18: point KBRANCH to 4.18
core-image-sato-sdk-ptest: Fix free space issues causing test failures
core-image-sato-sdk-ptest: Increase qemu memory to 1GB
resulttool: Enable report for single result file
libsndfile1: update security patches
bluez5: Fix status subcommand of init script
bluez5: add mesh dependency on ell
devtool: prevent starting git gc in background
python-native: fix one do_populate_sysroot warning
run-ptest: use error handling for useradd and userdel
zlib: clean up ptest
zlib: cleanup
correct do_patch for kernel bbappend in sdk
oe-init-build-env: Error out when failed to locate cwd
python: time.tzset missing
timezone: update to 2019a
timezone: refactor to simplify maint
openssl10: Upgrade 1.0.2q -> 1.0.2r
openssl: Upgrade 1.1.1a -> 1.1.1b
openssl: don't disable the AFALG engine based on host kernel
openssl: Add cryptodev-linux PACKAGECONFIG
openssl: drop Python 2.x dependency in -ptest
openssl: Fix ptest test output translation
glibc: Drop upstream rejected patches
overview-manual: Fixed broken link to pseudo.
Documentation: Prepare for 2.6.2 release.
pkgdata.py: avoid target-sdk-dummy-provides to mess things up
resulttool/manualexecution: Refactor and simplify codebase
resulttool/manualexecution: Fixed step sorted by integer
resulttool/manualexecution: Enable display full steps without press enter
resulttool/manualexecution: Standardize input check
resulttool: Allow extraction of ptest data
resulttool: Allow store to work on single files
oeqa/manual/toaster: updated test id naming
oeqa/manual/toaster: transfer manual toaster test cases to oeqa
oeqa/manual/kernel-dev.json: test id updated
oeqa/manual/compliance-test.json: test id updated and missing test cases added
oeqa/manual/bsp-hw.json: test id updated and obsolete test cases removed
oeqa/manual/bsp-hw.json: add non-IA tests
oeqa/manual/sdk.json: Updated toolchain tarball to core-image-sato
oeqa/manual: Add manual runtime 'compliance' testcases to json


Updated invitation: Yocto Project Technical Team Meeting / Engineering Sync @ Weekly from 8am to 9am on Tuesday (PDT) (yocto@yoctoproject.org)

theyoctoproject@...
 

This event has been changed.

Yocto Project Technical Team Meeting / Engineering Sync

When
Changed: Weekly from 8am to 9am on Tuesday Pacific Time - Los Angeles
Where
Zoom Meeting: https://zoom.us/j/990892712 (map)
Calendar
yocto@...
Who
theyoctoproject@... - organizer
yocto@...
stephen.k.jolley@...
sjolley.yp.pm@...

The Yocto Project hosts a technical call. All community members are invited to join on both the call and in the IRC channel, which are used simultaneously.
We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

Bridge is with Zoom at: https://zoom.us/j/990892712

Tuesdays when we aren’t having the Monthly Technical Call The Yocto Project hosts a engineering sync by which the technical team discusses the current status of engineering topics, including the autobuilder, documentation, builds, and releases.

Going (yocto@...)?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account yocto@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.


Updated invitation: Yocto Project Technical Team Meeting / Engineering Sync @ Weekly at 8am on Tuesday (PDT) (yocto@yoctoproject.org)

theyoctoproject@...
 

This event has been changed.

Yocto Project Technical Team Meeting / Engineering Sync

When
Weekly at 8am on Tuesday Pacific Time - Los Angeles
Where
Zoom Meeting: https://zoom.us/j/990892712 (map)
Calendar
yocto@...
Who
theyoctoproject@... - organizer
yocto@...
stephen.k.jolley@...
sjolley.yp.pm@...

The Yocto Project hosts a technical call. All community members are invited to join on both the call and in the IRC channel, which are used simultaneously.
We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

Bridge is with Zoom at: https://zoom.us/j/990892712

Tuesdays when we aren’t having the Monthly Technical Call The Yocto Project hosts a engineering sync by which the technical team discusses the current status of engineering topics, including the autobuilder, documentation, builds, and releases.

Going (yocto@...)?   All events in this series:   Yes - Maybe - No    more options »

Invitation from Google Calendar

You are receiving this courtesy email at the account yocto@... because you are an attendee of this event.

To stop receiving future updates for this event, decline this event. Alternatively you can sign up for a Google account at https://www.google.com/calendar/ and control your notification settings for your entire calendar.

Forwarding this invitation could allow any recipient to send a response to the organizer and be added to the guest list, or invite others regardless of their own invitation status, or to modify your RSVP. Learn More.

7521 - 7540 of 53826