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

2019-08-13 Thread 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...@windriver.com wrote:

From: Changqing Li 

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

Signed-off-by: Changqing Li 
---
  .../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)

--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread akuster808 


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 
>> ---
>>  .../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
>>
>>

-- 
___
yocto mailing

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

2019-08-13 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread Armin Kuster 
remove kernel fragments now that they are in the
kernel-cache for 4.19

update bbappend accordingly.

Signed-off-by: Armin Kuster 
---
 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..000
--- 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..000
--- 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..000
--- 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..000
--- 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..000
--- 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 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 000..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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 .../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..000
--- 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..000
--- 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..000
--- 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..000
--- 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

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread Armin Kuster 
Signed-off-by: Armin Kuster 
---
 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..000
--- 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..000
--- 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..000
--- 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..000
--- 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..000
--- 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 mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread Tummalapalli, 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.tummalapa...@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-173.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

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

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190820T08
DTEND;TZID=America/Los_Angeles:20190903T09
RRULE:FREQ=WEEKLY;UNTIL=20190827T065959Z;BYDAY=TU
DTSTAMP:20190813T203759Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@i
 ntel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sjolley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.c
 om
X-MICROSOFT-CDO-OWNERAPPTID:1923148408
CREATED:20180524T181406Z
DESCRIPTION:The Yocto Project hosts a technical call. All community mem
 bers are invited to join on both the call and in the IRC channel\, which ar
 e used simultaneously.We encourage people attending the meeting to logo
 n and announce themselves on the Yocto Project IRC chancel during the meeti
 ng (optional):Yocto IRC: http://webchat.freenode.net/?chan
 nels=#yocto">http://webchat.freenode.net/?channels=#yoctoWiki: 
 https://www.yoctoproject.org/public-virtual-meetings/;>https://www
 .yoctoproject.org/public-virtual-meetings/Bridge is with Zoom a
 t: https://zoom.us/j/990892712; id="ow634" __is_owner="true">https
 ://zoom.us/j/990892712Tuesdays when we aren’t having the Monthl
 y Technical Call The Yocto Project hosts a engineering sync by which the te
 chnical team discusses the current status of engineering topics\, including
  the autobuilder\, documentation\, builds\, and releases.\n\n-::~:~::~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\n
 Please do not edit this section of the description.\n\nView your event at h
 ttps://www.google.com/calendar/event?action=VIEW=NzRwajhkMWg2b3A2MmI5aj
 c0b21jYjlrY3BnamdiOW9jbGhqMGI5amNvczNpbzloNjFpamdkMW5jNCB5b2N0b0B5b2N0b3Byb
 2plY3Qub3Jn=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvbWQyNzYzNDVkN2JiZmVmZTl
 kYWM1MDk3NGEwZmU2ZmYyZmEyZDZlNGE=America%2FLos_Angeles=en=0.\n-::
 ~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~::~:~::-
LAST-MODIFIED:20190813T203755Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting / Engineering Sync
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190827T08
DTEND;TZID=America/Los_Angeles:20190827T09
RRULE:FREQ=WEEKLY;BYDAY=TU
DTSTAMP:20190813T203759Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1nc4_R20190827T15
 0...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@i
 ntel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sjolley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.c
 om
X-MICROSOFT-CDO-OWNERAPPTID:963975502
CREATED:20180524T181406Z
DESCRIPTION:The Yocto Project hosts a technical call. All community mem
 bers are invited to join on both the call and in the IRC channel\, which ar
 e used simultaneously.We encourage people attending the meeting to logo
 n and announce themselves on the Yocto Project IRC chancel during the meeti
 ng (optional):Yocto IRC: http://webchat.freenode.net/?chan
 nels=#yocto">http://webchat.freenode.net/?channels=#yoctoWiki: 
 https://www.yoctoproject.org/public-virtual-meetings/;>https://www
 .yoctoproject.org/public-virtual-meetings/Bridge is with Zoom a
 t: https://zoom.us/j/990892712; id="ow634" __is_owner="true">https
 ://zoom.us/j/990892712Tuesdays when we aren’t having the Monthl
 y Technical Call The Yocto Project hosts a engineering sync by which the te
 chnical team discusses the current status of engineering topics\, including
  the autobuilder\, documentation\, builds\, and releases.\n\n-::~:~::~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\n
 Please do not edit this section of the description.\n\nView your event at h
 ttps://www.google.com/calendar/event?action=VIEW=NzRwajhkMWg2b3A2MmI5aj
 c0b21jYjlrY3BnamdiOW9jbGhqMGI5amNvczNpbzloNjFpamdkMW5jNF9SMjAxOTA4MjdUMTUwM
 DAwIHlvY3RvQHlvY3RvcHJvamVjdC5vcmc=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNv
 bWI0OTI1MmE1ODA1NzNkOTdiOTNmZThiZDc0NWY0YTJhMzBjODdlZTk=America%2FLos_A
 ngeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20190813T203755Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting / Engineering Sync
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Updated invitation: Yocto Project Technical Team Meeting / Engineering Sync @ Tue Aug 20, 2019 8am - 9am (PDT) (yocto@yoctoproject.org)

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190820T08
DTEND;TZID=America/Los_Angeles:20190820T09
DTSTAMP:20190813T203714Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sjolley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@i
 ntel.com
X-MICROSOFT-CDO-OWNERAPPTID:-1512728414
RECURRENCE-ID;TZID=America/Los_Angeles:20190820T08
CREATED:20180524T181406Z
DESCRIPTION:The Yocto Project hosts a technical call. All community mem
 bers are invited to join on both the call and in the IRC channel\, which ar
 e used simultaneously.We encourage people attending the meeting to logo
 n and announce themselves on the Yocto Project IRC chancel during the meeti
 ng (optional):Yocto IRC: http://webchat.freenode.net/?chan
 nels=#yocto">http://webchat.freenode.net/?channels=#yoctoWiki: 
 https://www.yoctoproject.org/public-virtual-meetings/;>https://www
 .yoctoproject.org/public-virtual-meetings/Bridge is with Zoom a
 t: https://zoom.us/j/990892712; id="ow634" __is_owner="true">https
 ://zoom.us/j/990892712Tuesdays when we aren’t having the Monthl
 y Technical Call The Yocto Project hosts a engineering sync by which the te
 chnical team discusses the current status of engineering topics\, including
  the autobuilder\, documentation\, builds\, and releases.\n\n-::~:~::~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\n
 Please do not edit this section of the description.\n\nView your event at h
 ttps://www.google.com/calendar/event?action=VIEW=NzRwajhkMWg2b3A2MmI5aj
 c0b21jYjlrY3BnamdiOW9jbGhqMGI5amNvczNpbzloNjFpamdkMW5jNF8yMDE5MDgyMFQxNTAwM
 DBaIHlvY3RvQHlvY3RvcHJvamVjdC5vcmc=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNv
 bWZhM2NlYTNkNDQyOWJjNWJkNzBhZGI3ODY1YjBjMmZmMDczN2M5ZDg=America%2FLos_A
 ngeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20190813T203711Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting / Engineering Sync
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Updated invitation: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday from Tue Feb 5 to Mon Aug 5 (PST) (yocto@yoctoproject.org)

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190205T08
DTEND;TZID=America/Los_Angeles:20190205T083000
RRULE:FREQ=MONTHLY;UNTIL=20190806T065959Z;BYDAY=1TU
DTSTAMP:20190813T203629Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:62kon3jnin570da8ggvcvs9u9c_r20190205t160...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@intel
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sjolley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.c
 om
X-MICROSOFT-CDO-OWNERAPPTID:-1544847343
CREATED:20180524T181406Z
DESCRIPTION:We encourage people attending the meeting to logon and announce
  themselves on the Yocto Project IRC chancel during the meeting (optional):
 Yocto IRC: https://www.google.com/url?q=http%3A%2F%2Fwebch
 at.freenode.net%2F%3Fchannels%3D%23yocto\;sa=D\;usd=2\;usg=AFQj
 CNEvOHVIkxKIrfXWfUxCcVS5_8kh5w" target="_blank">http://webchat.freenode.net
 /?channels=#yoctoWiki: https://www.yoctoproject.org/pu
 blic-virtual-meetings/">https://www.yoctoproject.org/public-virtual-meeting
 s/Bridge is with Zoom at: https://www.google.com/url?q
 =https%3A%2F%2Fzoom.us%2Fj%2F990892712\;sa=D\;usd=2\;usg=AFQjCN
 G2F5sUpm-S-RhkqNhXVBd3m1_3LA" target="_blank">https://zoom.us/j/990892712\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n\n
 View your event at https://www.google.com/calendar/event?action=VIEW=Nj
 Jrb24zam5pbjU3MGRhOGdndmN2czl1OWNfUjIwMTkwMjA1VDE2MDAwMCB5b2N0b0B5b2N0b3Byb
 2plY3Qub3Jn=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvbTQ1MTk4OGNiMmYwYTExZjI
 1YTNkNDc0NWQwNjY5YzliZDQ1YTBkY2Q=America%2FLos_Angeles=en=0.\n-::
 ~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~::~:~::-
LAST-MODIFIED:20190813T203624Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

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

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20190820T08
DTEND;TZID=America/Los_Angeles:20190903T09
RRULE:FREQ=WEEKLY;BYDAY=TU
DTSTAMP:20190813T203629Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:74pj8d1h6op62b9j74omcb9kcpgjgb9oclhj0b9jcos3io9h61ijgd1...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@i
 ntel.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=
 TRUE;CN=sjolley.yp...@gmail.com;X-NUM-GUESTS=0:mailto:sjolley.yp.pm@gmail.c
 om
X-MICROSOFT-CDO-OWNERAPPTID:1923148408
CREATED:20180524T181406Z
DESCRIPTION:The Yocto Project hosts a technical call. All community mem
 bers are invited to join on both the call and in the IRC channel\, which ar
 e used simultaneously.We encourage people attending the meeting to logo
 n and announce themselves on the Yocto Project IRC chancel during the meeti
 ng (optional):Yocto IRC: http://webchat.freenode.net/?chan
 nels=#yocto">http://webchat.freenode.net/?channels=#yoctoWiki: 
 https://www.yoctoproject.org/public-virtual-meetings/;>https://www
 .yoctoproject.org/public-virtual-meetings/Bridge is with Zoom a
 t: https://zoom.us/j/990892712; id="ow634" __is_owner="true">https
 ://zoom.us/j/990892712Tuesdays when we aren’t having the Monthl
 y Technical Call The Yocto Project hosts a engineering sync by which the te
 chnical team discusses the current status of engineering topics\, including
  the autobuilder\, documentation\, builds\, and releases.\n\n-::~:~::~:~:~:
 ~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-\n
 Please do not edit this section of the description.\n\nView your event at h
 ttps://www.google.com/calendar/event?action=VIEW=NzRwajhkMWg2b3A2MmI5aj
 c0b21jYjlrY3BnamdiOW9jbGhqMGI5amNvczNpbzloNjFpamdkMW5jNCB5b2N0b0B5b2N0b3Byb
 2plY3Qub3Jn=MjUjdGhleW9jdG9wcm9qZWN0QGdtYWlsLmNvbWQyNzYzNDVkN2JiZmVmZTl
 kYWM1MDk3NGEwZmU2ZmYyZmEyZDZlNGE=America%2FLos_Angeles=en=0.\n-::
 ~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
 ~::~:~::-
LAST-MODIFIED:20190813T203624Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:2
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting / Engineering Sync
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Updated invitation: Yocto Project Technical Team Meeting @ Monthly from 8am to 8:30am on the first Tuesday from Tue Jun 5, 2018 to Mon Aug 5 (PDT) (yocto@yoctoproject.org)

2019-08-13 Thread theyoctoproject 
BEGIN:VCALENDAR
PRODID:-//Google Inc//Google Calendar 70.9054//EN
VERSION:2.0
CALSCALE:GREGORIAN
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
X-LIC-LOCATION:America/Los_Angeles
BEGIN:DAYLIGHT
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
TZNAME:PDT
DTSTART:19700308T02
RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
TZNAME:PST
DTSTART:19701101T02
RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Los_Angeles:20180605T08
DTEND;TZID=America/Los_Angeles:20180605T083000
RRULE:FREQ=MONTHLY;UNTIL=20190205T075959Z;BYDAY=1TU
DTSTAMP:20190813T203629Z
ORGANIZER;CN=theyoctoproj...@gmail.com:mailto:theyoctoproj...@gmail.com
UID:62kon3jnin570da8ggvcvs9...@google.com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=theyoctoproj...@gmail.com;X-NUM-GUESTS=0:mailto:theyoctoproject@gmail.c
 om
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=stephen.k.jol...@intel.com;X-NUM-GUESTS=0:mailto:stephen.k.jolley@intel
 .com
ATTENDEE;CUTYPE=INDIVIDUAL;ROLE=REQ-PARTICIPANT;PARTSTAT=ACCEPTED;RSVP=TRUE
 ;CN=yocto@yoctoproject.org;X-NUM-GUESTS=0:mailto:yocto@yoctoproject.org
X-MICROSOFT-CDO-OWNERAPPTID:-636228788
CREATED:20180524T181406Z
DESCRIPTION:We encourage people attending the meeting to logon and announce
  themselves on the Yocto Project IRC chancel during the meeting (optional):
 Yocto IRC: https://www.google.com/url?q=http%3A%2F%2Fwebch
 at.freenode.net%2F%3Fchannels%3D%23yocto\;sa=D\;usd=2\;usg=AFQj
 CNEvOHVIkxKIrfXWfUxCcVS5_8kh5w" target="_blank">http://webchat.freenode.net
 /?channels=#yoctoWiki: https://www.yoctoproject.org/pu
 blic-virtual-meetings/">https://www.yoctoproject.org/public-virtual-meeting
 s/Bridge is with Zoom at: https://www.google.com/url?q
 =https%3A%2F%2Fzoom.us%2Fj%2F990892712\;sa=D\;usd=2\;usg=AFQjCN
 G2F5sUpm-S-RhkqNhXVBd3m1_3LA" target="_blank">https://zoom.us/j/990892712\n\n-::~:~::~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~
 :~:~:~:~:~::~:~::-\nPlease do not edit this section of the description.\n\n
 View your event at https://www.google.com/calendar/event?action=VIEW=Nj
 Jrb24zam5pbjU3MGRhOGdndmN2czl1OWMgeW9jdG9AeW9jdG9wcm9qZWN0Lm9yZw=MjUjdG
 hleW9jdG9wcm9qZWN0QGdtYWlsLmNvbTcwZTEzYmNmOTE2M2Q0ZWI4YWI5ODA2NGZkYjg3ZmQ3Y
 WZhYThkZDQ=America%2FLos_Angeles=en=0.\n-::~:~::~:~:~:~:~:~:~:~:~
 :~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~::~:~::-
LAST-MODIFIED:20190813T203624Z
LOCATION:Zoom Meeting: https://zoom.us/j/990892712
SEQUENCE:1
STATUS:CONFIRMED
SUMMARY:Yocto Project Technical Team Meeting
TRANSP:OPAQUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:This is an event reminder
TRIGGER:-P0DT0H15M0S
END:VALARM
END:VEVENT
END:VCALENDAR


invite.ics
Description: application/ics
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto dev day ELCE 2019 Lyon ?

2019-08-13 Thread Volosincu, Andreea S 
Peter, thank you, that is a good point. I will  check with the instructors if 
there are no issues with changing it to the first day.

Thanks,
Andreea

-Original Message-
From: Peter Kjellerstedt [mailto:peter.kjellerst...@axis.com] 
Sent: Tuesday, August 13, 2019 5:01 AM
To: Philip Balister ; Nicolas Dechesne 
; Volosincu, Andreea S 

Cc: Yocto list discussion 
Subject: RE: [yocto] yocto dev day ELCE 2019 Lyon ?

> -Original Message-
> From: Philip Balister 
> Sent: den 5 juli 2019 23:42
> To: Peter Kjellerstedt ; Nicolas Dechesne 
> ; Thomas Roos 
> ; Volosincu, Andreea S 
> 
> Cc: Yocto list discussion 
> Subject: Re: [yocto] yocto dev day ELCE 2019 Lyon ?
> 
> In 07/04/2019 06:38 AM, Peter Kjellerstedt wrote:
> >> -Original Message-
> >> From: yocto-boun...@yoctoproject.org  boun...@yoctoproject.org>
> >> On Behalf Of Nicolas Dechesne
> >> Sent: den 4 juli 2019 08:45
> >> To: Thomas Roos ; Volosincu, Andreea S 
> >> 
> >> Cc: Yocto list discussion 
> >> Subject: Re: [yocto] yocto dev day ELCE 2019 Lyon ?
> >>
> >> Hi Thomas,
> >>
> >> On Thu, Jul 4, 2019 at 8:18 AM Thomas Roos
> 
> >> wrote:
> >>>
> >>> Hi,
> >>> are there any plans to organize a yocto dev day in October 2019, 
> >>> Lyon. Embedded Linux Conference Europe?
> >>> cheers, Thomas
> >>
> >> Yes, in fact we are trying something new for the first time at 
> >> ELC-E this year, see:
> >> https://lists.yoctoproject.org/pipermail/yocto/2019-May/045088.html
> >>
> >> There will be a 2-day "Yocto Project Summit" with a mix of 
> >> presentations/talks, training classes and developers meetings, 
> >> including a social event in the evening.
> >>
> >> cc'ing Andreea if there are more questions.
> >
> > Will this replace OEDEM too?
> 
> Yes. 5 days of conference sessions meetings is enough for anyone :)
> 
> Philip
> 
> > //Peter

Looking at the information on the Linux Foundation page about OSS/ELCE 
(https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/),
is it correct that the social event for the Yocto Project Summit will be on 
"Day 2", i.e., Friday? I had expected it to be on Thursday as I assume people 
want to go home on Friday evening...

//Peter

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Yocto Project Status WW33'19

2019-08-13 Thread sjolley.yp.pm 
Current Dev Position: YP 2.8 M3

Next Deadline: YP 2.8 Milestone M3 Cutoff (Feature Freeze) Aug 25, 2019

 

SWAT Team Rotation:

*   SWAT lead is currently: Amanda
*   SWAT team rotation: Amanda -> Chen on Aug. 16, 2019
*   SWAT team rotation: Chen -> Armin on Aug. 23, 2019
*
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team

 

Next Team Meetings:

*   Bug Triage meeting Thursday August 15th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Sept. 3rd at 8am PDT (
 https://zoom.us/j/990892712) 
*   Twitch - Next event is Tuesday Sept. 3rd at 8am PDT (
 https://www.twitch.tv/yocto_project)

 

Key Status/Updates:

*   YP 2.6.3 is out of QA and being readied for release.
*   This release which was 2.8 will now become 3.0.
*   The sstate has equivalency work has run into some challenges:

*   performance of the hash server is not able to scale to the
autibuilder's load
*   performance of runqueue has regressed even when not using the hash
equivalency code
*   bugfixes in master-next regress performance even further
*   there are bugs being triggered by the has equivalency code that need
investigation and resolution (along with test cases creating).

These issues are being worked on but we need to ensure correctness of the
new code first before the performance can be fixed

*   There were updates so some key components for bug fixes this week,
in particular pseudo.
*   General patch merging is happening and the queue is mostly clear and
flowing but it isn't happening as frequently as usual due to the hash
equivalency work.

 

Planned Releases for YP 3.0 {2.8}:

*   M2 is released.
*   M3 Cutoff (Feature Freeze) 25th Aug
*   M3 Release 6th Sept
*   M4 Cutoff 30th Sept - this will be YP 3.0.
*   YP 3.0 {2.8 (M4)} Final Release 25th Oct

 

Planned upcoming dot releases:

*   YP 2.7.2 (Warrior) is planned for after YP 3.0 release.
*   YP 2.6.3 (Thud) is out of QA and being readied for release.
*   YP 2.6.4 (Thud) is planned for after YP 2.7.2  release.

 

Tracking Metrics:

*   WDD 2482 (last week 2481) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1489 (last week 1496)
*   Patches in the Pending State: 617 (41%) [last week 615 (41%)]

 

Key Status Links for YP:

 
https://wiki.yoctoproject.org/wiki/Yocto_Project_v2.8_Status

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Schedule

 
https://wiki.yoctoproject.org/wiki/Yocto_2.8_Features

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Project Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] yocto dev day ELCE 2019 Lyon ?

2019-08-13 Thread Peter Kjellerstedt 
> -Original Message-
> From: Philip Balister 
> Sent: den 5 juli 2019 23:42
> To: Peter Kjellerstedt ; Nicolas Dechesne
> ; Thomas Roos
> ; Volosincu, Andreea S
> 
> Cc: Yocto list discussion 
> Subject: Re: [yocto] yocto dev day ELCE 2019 Lyon ?
> 
> In 07/04/2019 06:38 AM, Peter Kjellerstedt wrote:
> >> -Original Message-
> >> From: yocto-boun...@yoctoproject.org  boun...@yoctoproject.org>
> >> On Behalf Of Nicolas Dechesne
> >> Sent: den 4 juli 2019 08:45
> >> To: Thomas Roos ; Volosincu, Andreea S
> >> 
> >> Cc: Yocto list discussion 
> >> Subject: Re: [yocto] yocto dev day ELCE 2019 Lyon ?
> >>
> >> Hi Thomas,
> >>
> >> On Thu, Jul 4, 2019 at 8:18 AM Thomas Roos
> 
> >> wrote:
> >>>
> >>> Hi,
> >>> are there any plans to organize a yocto dev day in October 2019,
> >>> Lyon. Embedded Linux Conference Europe?
> >>> cheers, Thomas
> >>
> >> Yes, in fact we are trying something new for the first time at ELC-E
> >> this year, see:
> >> https://lists.yoctoproject.org/pipermail/yocto/2019-May/045088.html
> >>
> >> There will be a 2-day "Yocto Project Summit" with a mix of
> >> presentations/talks, training classes and developers meetings,
> >> including a social event in the evening.
> >>
> >> cc'ing Andreea if there are more questions.
> >
> > Will this replace OEDEM too?
> 
> Yes. 5 days of conference sessions meetings is enough for anyone :)
> 
> Philip
> 
> > //Peter

Looking at the information on the Linux Foundation page about OSS/ELCE 
(https://events.linuxfoundation.org/events/embedded-linux-conference-europe-2019/program/co-located-events/),
 
is it correct that the social event for the Yocto Project Summit will 
be on "Day 2", i.e., Friday? I had expected it to be on Thursday as I 
assume people want to go home on Friday evening...

//Peter

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] State of Meson build system through eSDK

2019-08-13 Thread Martin Siegumfeldt 
On 8/13/19 12:59 PM, Alexander Kanavin wrote:
On Tue, 13 Aug 2019 at 12:41, Martin Siegumfeldt 
mailto:m...@gomspace.com>> wrote:
The link above is not about eSDK, it's about devtool which works perfectly fine 
in a non-SDK environment (e.g. plain yocto).

Hmm, since it is a subsection beneath 'Using the Extensible SDK' I was 
expecting the list to describe supported build systems related to devtool in 
context of the eSDK?

This is maybe not communicated well, but devtool works the same in and out of 
SDK environment. You can check what build systems it supports here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/recipetool/create_buildsys.py#n874

It probably wouldn't be too much effort to add a meson handler there. In any 
case, 'devtool add' is just a starting point, and does not promise to produce a 
fully working recipe.

Alex

Ok, so it does appear to be "close" but yet unknown territory. If I manage to 
find time for experiments, I'll get back with the results.

Thanks again :)
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] State of Meson build system through eSDK

2019-08-13 Thread Alexander Kanavin 
On Tue, 13 Aug 2019 at 12:41, Martin Siegumfeldt  wrote:

> The link above is not about eSDK, it's about devtool which works perfectly
> fine in a non-SDK environment (e.g. plain yocto).
>
> Hmm, since it is a subsection beneath 'Using the Extensible SDK' I was
> expecting the list to describe supported build systems related to devtool
> in context of the eSDK?
>

This is maybe not communicated well, but devtool works the same in and out
of SDK environment. You can check what build systems it supports here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/scripts/lib/recipetool/create_buildsys.py#n874

It probably wouldn't be too much effort to add a meson handler there. In
any case, 'devtool add' is just a starting point, and does not promise to
produce a fully working recipe.

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] State of Meson build system through eSDK

2019-08-13 Thread Martin Siegumfeldt 
On 8/13/19 11:57 AM, Alexander Kanavin wrote:
On Tue, 13 Aug 2019 at 10:40, Martin Siegumfeldt 
mailto:m...@gomspace.com>> wrote:
I am wondering if/when Meson is expected supported through the eSDK - I
don't see it from the list:
https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-a-closer-look-at-devtool-add
?

The link above is not about eSDK, it's about devtool which works perfectly fine 
in a non-SDK environment (e.g. plain yocto).

Hmm, since it is a subsection beneath 'Using the Extensible SDK' I was 
expecting the list to describe supported build systems related to devtool in 
context of the eSDK?

I think meson in SDKs actually is supported, as there is a nativesdk- version 
of the meson recipe. Do you want to try and report?

Sorry I don't have any particular SW at hand - I was more thinking long term 
build system strategy, and everyone seems to be chasing Meson these days.
Alex

Thanks,

Martin
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] Init stops working on second boot cycle

2019-08-13 Thread Andy Pont 
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 
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?

-Andy.



-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] please help on compiling my kernel

2019-08-13 Thread Tg, Harish 
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.

Regards,
Harish.
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Re: [yocto] State of Meson build system through eSDK

2019-08-13 Thread Alexander Kanavin 
On Tue, 13 Aug 2019 at 10:40, Martin Siegumfeldt  wrote:

> I am wondering if/when Meson is expected supported through the eSDK - I
> don't see it from the list:
>
> https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-a-closer-look-at-devtool-add
> ?
>

The link above is not about eSDK, it's about devtool which works perfectly
fine in a non-SDK environment (e.g. plain yocto).

I think meson in SDKs actually is supported, as there is a nativesdk-
version of the meson recipe. Do you want to try and report?

Alex
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

[yocto] State of Meson build system through eSDK

2019-08-13 Thread Martin Siegumfeldt 
Hi,


I am wondering if/when Meson is expected supported through the eSDK - I
don't see it from the list:
https://www.yoctoproject.org/docs/current/sdk-manual/sdk-manual.html#sdk-a-closer-look-at-devtool-add
?


Thanks,

Martin

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto