[OE-core][PATCH] yocto-uninative: Update to 4.4 for glibc 2.39

[Michael Halstead]

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index eaa3e9b31c..4ac66fd506 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.38"
-UNINATIVE_VERSION = "4.3"
+UNINATIVE_MAXGLIBCVERSION = "2.39"
+UNINATIVE_VERSION = "4.4"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"8df05f4a41455018b4303b2e0ea4eac5c960b5a13713f6dbb33dfdb3e32753ec"
-UNINATIVE_CHECKSUM[i686] ?= 
"bea76b4a97c9ba0077c0dd1295f519cd599dbf71f0ca1c964471c4cdb043addd"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"b61876130f494f75092f21086b4a64ea5fb064045769bf1d32e9cb6af17ea8ec"
+UNINATIVE_CHECKSUM[i686] ?= 
"9f28627828f0082cc0344eede4d9a861a9a064bfa8f36e072e46212f0fe45fcc"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"d81c54284be2bb886931fc87281d58177a2cd381cf99d1981f8923039a72a302"
-- 
2.43.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#196239): 
https://lists.openembedded.org/g/openembedded-core/message/196239
Mute This Topic: https://lists.openembedded.org/mt/104596276/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] yocto-uninative: Update to 4.3

[Michael Halstead]

Add in stable updates to glibc 2.38 to fix malloc bugs

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 6596c0f4a2..eaa3e9b31c 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -7,9 +7,9 @@
 #
 
 UNINATIVE_MAXGLIBCVERSION = "2.38"
-UNINATIVE_VERSION = "4.2"
+UNINATIVE_VERSION = "4.3"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"cff40e7bdde50aeda06707af8c001796a71b4cf33c5ae1616e5c47943ff6b94e"
-UNINATIVE_CHECKSUM[i686] ?= 
"a70516447e9a9f1465ffaf1c7f89e79d1692d2356d86fd2a5a63acd908db1ff2"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"6a86d71eeafba4fefec600c9bf8cf4a01324d1eb52788b6e398d3f23c10d19fb"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"8df05f4a41455018b4303b2e0ea4eac5c960b5a13713f6dbb33dfdb3e32753ec"
+UNINATIVE_CHECKSUM[i686] ?= 
"bea76b4a97c9ba0077c0dd1295f519cd599dbf71f0ca1c964471c4cdb043addd"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"1c35f09a75c4096749bbe1e009df4e3968cde151424062cf4aa3ed89db22b030"
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#187015): 
https://lists.openembedded.org/g/openembedded-core/message/187015
Mute This Topic: https://lists.openembedded.org/mt/101101203/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: 
https://lists.openembedded.org/g/openembedded-core/leave/8023207/21656/1426099254/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] yocto-uninative: Update to 4.2 for glibc 2.38

[Michael Halstead]

Uninative 4.2 adds glibc 2.38.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index b3bd7794fb..6596c0f4a2 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.37"
-UNINATIVE_VERSION = "4.1"
+UNINATIVE_MAXGLIBCVERSION = "2.38"
+UNINATIVE_VERSION = "4.2"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"b6ff9171aa7d3828bc81197822e804725908856bbd488bf412121cc0deddcb60"
-UNINATIVE_CHECKSUM[i686] ?= 
"6354fd2e09af1f111bad5e34ce7af4f9ad7cd266188af7eeceaeb982afd5354b"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"f83eca543170adfd2432b135ca655922a4303622d73cc4b13e92b973cdf49e3a"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"cff40e7bdde50aeda06707af8c001796a71b4cf33c5ae1616e5c47943ff6b94e"
+UNINATIVE_CHECKSUM[i686] ?= 
"a70516447e9a9f1465ffaf1c7f89e79d1692d2356d86fd2a5a63acd908db1ff2"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"6a86d71eeafba4fefec600c9bf8cf4a01324d1eb52788b6e398d3f23c10d19fb"
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#186119): 
https://lists.openembedded.org/g/openembedded-core/message/186119
Mute This Topic: https://lists.openembedded.org/mt/100775874/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: 
https://lists.openembedded.org/g/openembedded-core/leave/8023207/21656/1426099254/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] resulttool/resultutils: allow index generaiton despite corrupt json

[Michael Halstead]

non-release indexes will continue to generate when test output is
corrupted.

Signed-off-by: Michael Halstead 
---
 scripts/lib/resulttool/resultutils.py | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/scripts/lib/resulttool/resultutils.py 
b/scripts/lib/resulttool/resultutils.py
index 7666331ba2..c5521d81bd 100644
--- a/scripts/lib/resulttool/resultutils.py
+++ b/scripts/lib/resulttool/resultutils.py
@@ -58,7 +58,11 @@ def append_resultsdata(results, f, configmap=store_map, 
configvars=extra_configv
 testseries = posixpath.basename(posixpath.dirname(url.path))
 else:
 with open(f, "r") as filedata:
-data = json.load(filedata)
+try:
+data = json.load(filedata)
+except json.decoder.JSONDecodeError:
+print("Cannot decode {}. Possible corruption. 
Skipping.".format(f))
+data = ""
 testseries = os.path.basename(os.path.dirname(f))
 else:
 data = f
-- 
2.41.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#184278): 
https://lists.openembedded.org/g/openembedded-core/message/184278
Mute This Topic: https://lists.openembedded.org/mt/100146210/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: 
https://lists.openembedded.org/g/openembedded-core/leave/8023207/21656/1426099254/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] uninative: Upgrade to 4.0 to include latest gcc 13.1.1

[Michael Halstead]

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index f3c05b7e20..ad4816a1f3 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -7,9 +7,9 @@
 #
 
 UNINATIVE_MAXGLIBCVERSION = "2.37"
-UNINATIVE_VERSION = "3.10"
+UNINATIVE_VERSION = "4.0"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"b11f7dff0ff5e3c971f22e89a105efb0f8d2006fd71d1ea3e5da771e416b0e01"
-UNINATIVE_CHECKSUM[i686] ?= 
"ad7daa7fca7693ca07eea5279f830333530171d357759b380954a25254edd8dd"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"ce8ff7e3247da312fbf84008f415bc1b4d113ac9fe4ec91581e4a20cd8b475d3"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"7baa8418a302df52e00916193b0a04f318356d9d2670c9a2bce3e966efefd738"
+UNINATIVE_CHECKSUM[i686] ?= 
"83114d36883d43a521e280742b9849bf85d039b2f83d8e21d480659babe75ee8"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"fd75b2a1a67a10f6b7d65afb7d0f3e71a63b0038e428f34dfe420bb37716558a"
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#181850): 
https://lists.openembedded.org/g/openembedded-core/message/181850
Mute This Topic: https://lists.openembedded.org/mt/99190723/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: 
https://lists.openembedded.org/g/openembedded-core/leave/8023207/21656/1426099254/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] selftest/runtime_test/virgl: Disable for all Rocky Linux

[Michael Halstead]

RHEL compatible kernels do not support vgem so we disable virgl headless
testing.

Signed-off-by: Michael Halstead 
---
 meta/lib/oeqa/selftest/cases/runtime_test.py | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/meta/lib/oeqa/selftest/cases/runtime_test.py 
b/meta/lib/oeqa/selftest/cases/runtime_test.py
index e32c4aff85..81b8d056cc 100644
--- a/meta/lib/oeqa/selftest/cases/runtime_test.py
+++ b/meta/lib/oeqa/selftest/cases/runtime_test.py
@@ -257,7 +257,8 @@ class TestImage(OESelftestTestCase):
 import subprocess, os
 
 distro = oe.lsb.distro_identifier()
-if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 
'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or distro.startswith('almalinux')):
+if distro and (distro in ['debian-9', 'debian-10', 'centos-7', 
'centos-8', 'ubuntu-16.04', 'ubuntu-18.04'] or
+distro.startswith('almalinux') or distro.startswith('rocky')):
 self.skipTest('virgl headless cannot be tested with %s' %(distro))
 
 qemu_distrofeatures = get_bb_var('DISTRO_FEATURES', 
'qemu-system-native')
-- 
2.39.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#178205): 
https://lists.openembedded.org/g/openembedded-core/message/178205
Mute This Topic: https://lists.openembedded.org/mt/97486168/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: 
https://lists.openembedded.org/g/openembedded-core/leave/8023207/21656/1426099254/xyzzy
 [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] uninative: Upgrade to 3.8 to include libgcc

[Michael Halstead]

Including libgcc solves issues with libpthread.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 7012db441b..eaed6f81f8 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -7,9 +7,9 @@
 #
 
 UNINATIVE_MAXGLIBCVERSION = "2.36"
-UNINATIVE_VERSION = "3.7"
+UNINATIVE_VERSION = "3.8"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"6a29bcae4b5b716d2d520e18800b33943b65f8a835eac1ff8793fc5ee65b4be6"
-UNINATIVE_CHECKSUM[i686] ?= 
"3f6d52e64996570c716108d49f8108baccf499a283bbefae438c7266b7a93305"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"b110bf2e10fe420f5ca2f3ec55f048ee5f0a54c7e34856a3594e51eb2aea0570"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"6b81da51cc0113056564dd87079f860214d1149ce28ce4d1a6f070c64296e298"
+UNINATIVE_CHECKSUM[i686] ?= 
"62260d4e923a27f19a5abe24076e97331145e3736e15e090569232b72a36642d"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"e71e745a3f402a57318af3708c986d81741940b6b949ba7d4ddca835d4fd9cbf"
-- 
2.39.0


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#175695): 
https://lists.openembedded.org/g/openembedded-core/message/175695
Mute This Topic: https://lists.openembedded.org/mt/96159230/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] uninative: Upgrade to 3.7 with glibc 2.36

[Michael Halstead]

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 411fe45a24..7012db441b 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,10 +6,10 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.35"
-UNINATIVE_VERSION = "3.6"
+UNINATIVE_MAXGLIBCVERSION = "2.36"
+UNINATIVE_VERSION = "3.7"
 
 UNINATIVE_URL ?= 
"http://downloads.yoctoproject.org/releases/uninative/${UNINATIVE_VERSION}/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"d64831cf2792c8e470c2e42230660e1a8e5de56a579cdd59978791f663c2f3ed"
-UNINATIVE_CHECKSUM[i686] ?= 
"2f0ee9b66b1bb2c85e2b592fb3c9c7f5d77399fa638d74961330cdb8de34ca3b"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"9bfc4c970495b3716b2f9e52c4df9f968c02463a9a95000f6657fbc3fde1f098"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"6a29bcae4b5b716d2d520e18800b33943b65f8a835eac1ff8793fc5ee65b4be6"
+UNINATIVE_CHECKSUM[i686] ?= 
"3f6d52e64996570c716108d49f8108baccf499a283bbefae438c7266b7a93305"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"b110bf2e10fe420f5ca2f3ec55f048ee5f0a54c7e34856a3594e51eb2aea0570"
-- 
2.37.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#169294): 
https://lists.openembedded.org/g/openembedded-core/message/169294
Mute This Topic: https://lists.openembedded.org/mt/92989931/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Hash Equivalence Server Domain Change

[Michael Halstead]

We are moving the hash equivalence server to dedicated servers. As part of
the change we need to change the domain.

Please update any BB_HASHSERVE_UPSTREAM
<https://docs.yoctoproject.org/bitbake/dev/bitbake-user-manual/bitbake-user-manual-ref-variables.html#term-BB_HASHSERVE_UPSTREAM>
variables
from "typhoon.yocto.io:8687" to "hashserv.yocto.io:8687" at your
earliest convenience.

We plan to make the switch during the next maintenance window on Friday
July 22nd. The previous server will quickly fall out of date and be taken
offline next week.

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#168287): 
https://lists.openembedded.org/g/openembedded-core/message/168287
Mute This Topic: https://lists.openembedded.org/mt/92489530/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH 2/2] scripts/autobuilder-worker-prereq-tests: add additional limit testing

[Michael Halstead]

Check that open file and user process limits are greater than or equal to what
the autobuilder uses.

Signed-off-by: Michael Halstead 
---
 scripts/autobuilder-worker-prereq-tests | 15 +++
 1 file changed, 15 insertions(+)

diff --git a/scripts/autobuilder-worker-prereq-tests 
b/scripts/autobuilder-worker-prereq-tests
index 3956349b30..572227dccd 100755
--- a/scripts/autobuilder-worker-prereq-tests
+++ b/scripts/autobuilder-worker-prereq-tests
@@ -51,6 +51,21 @@ if (( $WATCHES < 65000 )); then
 echo 'Need to increase watches (echo fs.inotify.max_user_watches=65536 | 
sudo tee -a /etc/sysctl.conf'
 exit 1
 fi
+OPEN_FILES=$(ulimit -n)
+if (( $OPEN_FILES < 65535 )); then
+echo 'Increase maximum open files in /etc/security/limits.conf'
+echo '*softnofile   131072'
+echo '*hardnofile   131072'
+exit 1
+fi
+MAX_PROCESSES=$(ulimit -u)
+if (( $MAX_PROCESSES < 514542 )); then
+echo 'Increase maximum user processes in /etc/security/limits.conf'
+echo '*hardnproc   515294'
+echo '*softnproc   514543'
+exit 1
+fi
+
 mkdir -p tmp/deploy/images/qemux86-64
 pushd tmp/deploy/images/qemux86-64
 if [ ! -e core-image-minimal-qemux86-64.ext4 ]; then
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#165522): 
https://lists.openembedded.org/g/openembedded-core/message/165522
Mute This Topic: https://lists.openembedded.org/mt/91042761/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH 1/2] scripts/autobuilder-worker-prereq-tests: update to use yocto 4.0

[Michael Halstead]

Use files from the current release to avoid the depreciated -show-cursor
option.

Signed-off-by: Michael Halstead 
---
 scripts/autobuilder-worker-prereq-tests | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/scripts/autobuilder-worker-prereq-tests 
b/scripts/autobuilder-worker-prereq-tests
index 82e9a77bd5..3956349b30 100755
--- a/scripts/autobuilder-worker-prereq-tests
+++ b/scripts/autobuilder-worker-prereq-tests
@@ -54,13 +54,13 @@ fi
 mkdir -p tmp/deploy/images/qemux86-64
 pushd tmp/deploy/images/qemux86-64
 if [ ! -e core-image-minimal-qemux86-64.ext4 ]; then
-wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-2.5.1/machines/qemu/qemux86-64/core-image-minimal-qemux86-64.ext4
+wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0/machines/qemu/qemux86-64/core-image-minimal-qemux86-64.ext4
 fi
 if [ ! -e core-image-minimal-qemux86-64.qemuboot.conf ]; then
-wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-2.5.1/machines/qemu/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf
+wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0/machines/qemu/qemux86-64/core-image-minimal-qemux86-64.qemuboot.conf
 fi
 if [ ! -e bzImage-qemux86-64.bin ]; then
-wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-2.5.1/machines/qemu/qemux86-64/bzImage-qemux86-64.bin
+wget 
http://downloads.yoctoproject.org/releases/yocto/yocto-4.0/machines/qemu/qemux86-64/bzImage-qemux86-64.bin
 fi
 popd
 bitbake qemu-helper-native
-- 
2.36.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#165521): 
https://lists.openembedded.org/g/openembedded-core/message/165521
Mute This Topic: https://lists.openembedded.org/mt/91042760/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][PATCH] scripts/autobuilder-worker-prereq-tests: jinja2 check

[Michael Halstead]

Ensure the jinja2 module is available during bringup.

Signed-off-by: Michael Halstead 
---
 scripts/autobuilder-worker-prereq-tests | 5 +
 1 file changed, 5 insertions(+)

diff --git a/scripts/autobuilder-worker-prereq-tests 
b/scripts/autobuilder-worker-prereq-tests
index 5d7e6e2601..82e9a77bd5 100755
--- a/scripts/autobuilder-worker-prereq-tests
+++ b/scripts/autobuilder-worker-prereq-tests
@@ -35,6 +35,11 @@ if [ "$?" != "0" ]; then
 echo "Please set git config --global user.email"
 exit 1
 fi
+python3 -c "import jinja2"
+if [ "$?" != "0" ]; then
+echo "Please ensure jinja2 is available"
+exit 1
+fi
 bitbake -p
 if [ "$?" != "0" ]; then
 echo "Bitbake parsing failed"
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156970): 
https://lists.openembedded.org/g/openembedded-core/message/156970
Mute This Topic: https://lists.openembedded.org/mt/86320755/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

I'll go ahead and switch to CentOS8-Stream once the current a-full is
complete. If there is a need to follow RHEL8 exactly we can add a Rocky
Linux worker in the future.


On Mon, Oct 4, 2021 at 11:28 AM Alexander Kanavin 
wrote:

> Since the original centos 8 is going away (support-wise) in less than 3
> months, should we just convert all workers to stream and move on?
>
> Alex
>
> On Mon, 4 Oct 2021 at 18:27, Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> This error was fixed upstream
>> https://bugzilla.redhat.com/show_bug.cgi?id=1975562 kernel 4.18.0-325.x
>> which has landed in CentOS8 Stream on centos8-ty-2 but not plain CentOS8
>> where the newest kernel is still at 4.18.0-305.x.
>>
>> I'll reboot into the older 4.18.0-240.15 kernel again on centos8-ty-1 as
>> a fix for now.
>>
>> On Tue, Sep 28, 2021 at 6:12 PM Anuj Mittal 
>> wrote:
>>
>>> Did we find out the reason why this was happening? I have started
>>> getting this error on Centos-8 while building hardknott.
>>>
>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4045
>>>
>>> Thanks,
>>>
>>> Anuj
>>>
>>> On Wed, 2021-06-16 at 23:45 +0100, Richard Purdie wrote:
>>> > On Sun, 2021-06-06 at 21:51 +0200, Alexander Kanavin wrote:
>>> > > On Sun, 6 Jun 2021 at 01:10, Richard Purdie
>>> > >  wrote:
>>> > > > I tried again with the autobuilder, still fails:
>>> > > >
>>> > > >
>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3516
>>> > > >
>>> > > > so whatever it is, it is still "live".
>>> > > >
>>> > >
>>> > >
>>> > > I did some digging. The issue happens when:
>>> > > - host is centos8
>>> > > - SDKMACHINE is i686 (e.g. cmake is 32 bit)
>>> > >
>>> > > Then there's a failing syscall attempting to set file times:
>>> > > utimensat_time64(AT_FDCWD, "../install/usr/local/lib/cmake/assimp-
>>> > > 4.1/assimp-config.cmake",
>>> > > [{tv_sec=1622966723, tv_nsec=6319439026193432576},
>>> > > {tv_sec=1622966579, tv_nsec=17840053692309438464}], 0) = -1
>>> > > EINVAL (Invalid argument)
>>> > >
>>> > > On latest Fedora, there's no issue:
>>> > > utimensat_time64(AT_FDCWD, "../install2/usr/local/lib/cmake/assimp-
>>> > > 4.1/assimp-config.cmake",
>>> > > [{tv_sec=1623002886, tv_nsec=6369724778172907520},
>>> > > {tv_sec=1623002886, tv_nsec=17839174083007217664}], 0) = 0
>>> > >
>>> > > utimensat_time64 only appeared with 5.1 kernels, however, 4.18 should
>>> > > be returning ENOSYS in that case
>>> > > probably?
>>> >
>>> > I hacked up a quick test bit of code (which makes assumptions
>>> > about 32 bit):
>>> >
>>> > #include 
>>> > #include 
>>> > #include 
>>> > #include 
>>> > #include 
>>> > #include 
>>> >
>>> > struct timespec64 {
>>> > long long   tv_sec; /* seconds */
>>> > long long   tv_nsec;/* nanoseconds */
>>> > };
>>> >
>>> > int main() {
>>> >   int fd = open("foo", O_RDWR | O_CREAT, 0644);
>>> >   write(fd, "foo", 3);
>>> >   struct timespec64 times[2] = {};
>>> >   times[0].tv_sec = 1622966723;
>>> >   times[0].tv_nsec = 631943;
>>> >   times[1].tv_sec = 1622966579;
>>> >   times[1].tv_nsec = 178400;
>>> >   int rc = syscall(SYS_utimensat_time64, fd, NULL, [0], 0);
>>> >   printf("rc=%d\n", rc);
>>> >   close(fd);
>>> >   return rc;
>>> > }
>>> >
>>> > built with "gcc -m32 test-syscall.c -o test" and run with "strace
>>> > ./test".
>>> > This works on all the systems I tried it in. As does:
>>> >
>>> >
>>> >   times[0].tv_sec = 1;
>>> >   times[0].tv_nsec = 2;
>>> >   times[1].tv_sec = 3;
>>> >   times[1].tv_nsec = 4;
>>> >
>>> > however if you set (and ignore the compiler warning):
>>> >
>>> >   times[0].tv_sec = 1622966723;
>>> >   times[0].tv_nsec = 6319439026193432576;
>>> >   times[1].tv_sec = 1622966579;
>>> >   times[1].tv_nsec = 17840053692309438464;
>>> >
>>> > then you see EINVAL on the centos system but not on my ubuntu one. It
>>> > will
>>> > do that until you reduce the values of tv_nsec right now. So it seems
>>> > most
>>> > systems accept large tv_nsec values but the Centos one does not.
>>> >
>>> > I think tv_nsec may be being clamped to LONG_MAX of 4 bytes but should
>>> > be
>>> > a LONG_LONG_MAX of 8 bytes on a 32 bit since the field is a 64 bit
>>> > long.
>>> >
>>> > Michael: Hopefully that gives you something to raise with them?
>>> >
>>> > Cheers,
>>> >
>>> > Richard
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>> 
>>>
>>>
>>
>> --
>> Michael Halstead
>> Linux Foundation / Yocto Project
>> Systems Operations Engineer
>>
>

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156633): 
https://lists.openembedded.org/g/openembedded-core/message/156633
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

This error was fixed upstream
https://bugzilla.redhat.com/show_bug.cgi?id=1975562 kernel 4.18.0-325.x
which has landed in CentOS8 Stream on centos8-ty-2 but not plain CentOS8
where the newest kernel is still at 4.18.0-305.x.

I'll reboot into the older 4.18.0-240.15 kernel again on centos8-ty-1 as a
fix for now.

On Tue, Sep 28, 2021 at 6:12 PM Anuj Mittal  wrote:

> Did we find out the reason why this was happening? I have started
> getting this error on Centos-8 while building hardknott.
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/63/builds/4045
>
> Thanks,
>
> Anuj
>
> On Wed, 2021-06-16 at 23:45 +0100, Richard Purdie wrote:
> > On Sun, 2021-06-06 at 21:51 +0200, Alexander Kanavin wrote:
> > > On Sun, 6 Jun 2021 at 01:10, Richard Purdie
> > >  wrote:
> > > > I tried again with the autobuilder, still fails:
> > > >
> > > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3516
> > > >
> > > > so whatever it is, it is still "live".
> > > >
> > >
> > >
> > > I did some digging. The issue happens when:
> > > - host is centos8
> > > - SDKMACHINE is i686 (e.g. cmake is 32 bit)
> > >
> > > Then there's a failing syscall attempting to set file times:
> > > utimensat_time64(AT_FDCWD, "../install/usr/local/lib/cmake/assimp-
> > > 4.1/assimp-config.cmake",
> > > [{tv_sec=1622966723, tv_nsec=6319439026193432576},
> > > {tv_sec=1622966579, tv_nsec=17840053692309438464}], 0) = -1
> > > EINVAL (Invalid argument)
> > >
> > > On latest Fedora, there's no issue:
> > > utimensat_time64(AT_FDCWD, "../install2/usr/local/lib/cmake/assimp-
> > > 4.1/assimp-config.cmake",
> > > [{tv_sec=1623002886, tv_nsec=6369724778172907520},
> > > {tv_sec=1623002886, tv_nsec=17839174083007217664}], 0) = 0
> > >
> > > utimensat_time64 only appeared with 5.1 kernels, however, 4.18 should
> > > be returning ENOSYS in that case
> > > probably?
> >
> > I hacked up a quick test bit of code (which makes assumptions
> > about 32 bit):
> >
> > #include 
> > #include 
> > #include 
> > #include 
> > #include 
> > #include 
> >
> > struct timespec64 {
> > long long   tv_sec; /* seconds */
> > long long   tv_nsec;/* nanoseconds */
> > };
> >
> > int main() {
> >   int fd = open("foo", O_RDWR | O_CREAT, 0644);
> >   write(fd, "foo", 3);
> >   struct timespec64 times[2] = {};
> >   times[0].tv_sec = 1622966723;
> >   times[0].tv_nsec = 631943;
> >   times[1].tv_sec = 1622966579;
> >   times[1].tv_nsec = 178400;
> >   int rc = syscall(SYS_utimensat_time64, fd, NULL, [0], 0);
> >   printf("rc=%d\n", rc);
> >   close(fd);
> >   return rc;
> > }
> >
> > built with "gcc -m32 test-syscall.c -o test" and run with "strace
> > ./test".
> > This works on all the systems I tried it in. As does:
> >
> >
> >   times[0].tv_sec = 1;
> >   times[0].tv_nsec = 2;
> >   times[1].tv_sec = 3;
> >   times[1].tv_nsec = 4;
> >
> > however if you set (and ignore the compiler warning):
> >
> >   times[0].tv_sec = 1622966723;
> >   times[0].tv_nsec = 6319439026193432576;
> >   times[1].tv_sec = 1622966579;
> >   times[1].tv_nsec = 17840053692309438464;
> >
> > then you see EINVAL on the centos system but not on my ubuntu one. It
> > will
> > do that until you reduce the values of tv_nsec right now. So it seems
> > most
> > systems accept large tv_nsec values but the Centos one does not.
> >
> > I think tv_nsec may be being clamped to LONG_MAX of 4 bytes but should
> > be
> > a LONG_LONG_MAX of 8 bytes on a 32 bit since the field is a 64 bit
> > long.
> >
> > Michael: Hopefully that gives you something to raise with them?
> >
> > Cheers,
> >
> > Richard
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> 
>
>

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156614): 
https://lists.openembedded.org/g/openembedded-core/message/156614
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

Thanks Alex,
The issue persists with the newest CentOS8 Stream kernel. Time to file a
bug with RedHat I suppose.

https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3535/steps/12/logs/stdio

On Fri, Jun 11, 2021 at 3:18 PM Alexander Kanavin 
wrote:

> I think the easiest is to run the genericx86 job on the worker. If the
> problem exists, you'll see a failure like this one:
>
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/48/builds/3523/steps/12/logs/stdio
>
> Alex
>
> On Fri, 11 Jun 2021 at 23:56, Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> I've switched centos8-ty-2.yocto.io over to Stream and it's now running
>> kernel 4.18.0-310.el8.x86_64. I'm not sure how to test if the problem
>> still exists but I don't see a related entry in the changelog so I expect
>> it does.
>>
>> Alex, can you check or send me a bit more info about how to check myself?
>>
>> On Wed, Jun 9, 2021 at 7:07 AM Alexander Kanavin 
>> wrote:
>>
>>> On Wed, 9 Jun 2021 at 13:37, Richard Purdie <
>>> richard.pur...@linuxfoundation.org> wrote:
>>>
>>>> Thanks Michael and Alex. We can therefore pretty safely say that
>>>> something was
>>>> broken between the 240 and 305 of the centos8 kernel for the 32 bit
>>>> syscall
>>>> utimensat syscalls.
>>>>
>>>> I did poke around https://github.com/kernelim/linux/tree/centos8 which
>>>> does
>>>> have a kernel diff but it is huge and you have to clone the repo to get
>>>> it.
>>>>
>>>> git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat
>>>> -C 40
>>>>
>>>> shows they did add the syscalls in that kernel.
>>>>
>>>> So this does look to be a RedHat issue. Not sure if we want to report it
>>>> to them? Can we run the autobuilders on the older kernel for now until
>>>> they hopefully fix it?
>>>>
>>>
>>> Centos 8 will be discontinued in just over 6 months  (
>>> https://www.centos.org/centos-linux/)
>>> so I think at least one of the centos 8 workers should be updated to
>>> centos stream 8
>>> (https://www.centos.org/centos-stream/ - includes instructions) and
>>> take it from there.
>>>
>>> Alex
>>>
>>
>>
>> --
>> Michael Halstead
>> Linux Foundation / Yocto Project
>> Systems Operations Engineer
>>
>

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152875): 
https://lists.openembedded.org/g/openembedded-core/message/152875
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

I've switched centos8-ty-2.yocto.io over to Stream and it's now running
kernel 4.18.0-310.el8.x86_64. I'm not sure how to test if the problem
still exists but I don't see a related entry in the changelog so I expect
it does.

Alex, can you check or send me a bit more info about how to check myself?

On Wed, Jun 9, 2021 at 7:07 AM Alexander Kanavin 
wrote:

> On Wed, 9 Jun 2021 at 13:37, Richard Purdie <
> richard.pur...@linuxfoundation.org> wrote:
>
>> Thanks Michael and Alex. We can therefore pretty safely say that
>> something was
>> broken between the 240 and 305 of the centos8 kernel for the 32 bit
>> syscall
>> utimensat syscalls.
>>
>> I did poke around https://github.com/kernelim/linux/tree/centos8 which
>> does
>> have a kernel diff but it is huge and you have to clone the repo to get
>> it.
>>
>> git show a3342908613ba72a84f652ca7a56c3e2113bda12 | grep sys_utimensat -C
>> 40
>>
>> shows they did add the syscalls in that kernel.
>>
>> So this does look to be a RedHat issue. Not sure if we want to report it
>> to them? Can we run the autobuilders on the older kernel for now until
>> they hopefully fix it?
>>
>
> Centos 8 will be discontinued in just over 6 months  (
> https://www.centos.org/centos-linux/)
> so I think at least one of the centos 8 workers should be updated to
> centos stream 8
> (https://www.centos.org/centos-stream/ - includes instructions) and take
> it from there.
>
> Alex
>


-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152872): 
https://lists.openembedded.org/g/openembedded-core/message/152872
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

I've rebooted centos8-ty-1 using the previous 4.18.0-240.15.1.el8_3.x86_64
kernel and kept it in the pool. I've paused centos8-ty-2 so it won't
interfere with builds and left it at the current 4.18.0-305.3.1.el8.x86_64
kernel for testing.

On Mon, Jun 7, 2021 at 11:04 AM Alexander Kanavin 
wrote:

> On Mon, 7 Jun 2021 at 19:18, Khem Raj  wrote:
>
>> > I added the needed packages to the CentOS workers. The compiled binary
>> prints "rc=0" on the three CentOS workers.
>>
>> can we now try linking and running it against SDK built nativesdk-glibc ?
>>
>
> Using the host libc won't show the issue, as it is old (2.28), isn't using
> utimensat_time64 and goes straight to utimensat.
>
> With nativesdk-glibc, it still succeeds:
> utimensat_time64(3, NULL, [{tv_sec=1, tv_nsec=2} /*
> 1970-01-01T00:00:01.2+ */, {tv_sec=3, tv_nsec=4} /*
> 1970-01-01T00:00:03.4+ */], 0) = 0
>
> So we'd need to look into why the kernel accepts this, but rejects the
> call from cmake. Any easy way to trace this? Just to repeat the failing one:
>
> utimensat_time64(AT_FDCWD,
> "../install/usr/local/lib/cmake/assimp-4.1/assimp-config.cmake",
> [{tv_sec=1622966723, tv_nsec=6319439026193432576}, {tv_sec=1622966579,
> tv_nsec=17840053692309438464}], 0) = -1 EINVAL (Invalid argument)
>
> Alex
>


-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152787): 
https://lists.openembedded.org/g/openembedded-core/message/152787
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 04/10] cmake: update 3.20.2 -> 3.20.3

[Michael Halstead]

On Mon, Jun 7, 2021 at 8:10 AM Khem Raj  wrote:

>
>
> On Mon, Jun 7, 2021 at 3:20 AM Alexander Kanavin 
> wrote:
>
>> On Mon, 7 Jun 2021 at 00:19, Khem Raj  wrote:
>>
>>> here is a small testcase to excercise utimensat_time64
>>>
>>> https://raw.githubusercontent.com/xantares/test-seccomp-time64/master/test-time64.c
>>>
>>> gcc -m32 test-time64.c
>>>
>>> it will be good to check how the resulting binary behaves with centos
>>> provided libc and sdk provided one.
>>>
>>
>> Yes, testing the issue without involving the sdk would be good, but I
>> can't build it in the host environment, and don't have rights to install
>> missing 32 bit support packages (not sure what that would be):
>>
>> /usr/include/gnu/stubs.h:7:11: fatal error: gnu/stubs-32.h: No such file
>> or directory
>>  # include 
>>
>
> Yeah it needs 32bit development libc and compiler installed
>


I added the needed packages to the CentOS workers. The compiled binary
prints "rc=0" on the three CentOS workers.

Is reverting to an older kernel in order yet?


>
>
>>^~~~
>>
>> Alex
>>
>

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152761): 
https://lists.openembedded.org/g/openembedded-core/message/152761
Mute This Topic: https://lists.openembedded.org/mt/83304703/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Error tagging: 2020-04.8-dunfell, 2020-04.8, and yocto-3.1.8 recreated

[Michael Halstead]

During today's release three tags (2020-04.8-dunfell, 2020-04.8, and 
yocto-3.1.8) were made against the HEAD of the master branch instead of the 
correct commit on the dunfell branch. The incorrect tags have been deleted and 
replaced with the correct tags. A git force pull may be required to bring 
repositories back into line. Please update your local repositories and ensure 
any automated systems using the openembedded-core repo are functioning as 
expected.

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#152550): 
https://lists.openembedded.org/g/openembedded-core/message/152550
Mute This Topic: https://lists.openembedded.org/mt/83270120/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] go: Use dl.google.com for SRC_URI

[Michael Halstead]

I've removed the following:
go1.16.3.src.tar.gz ( 0 bytes)
go1.16.3.src.tar.gz_bad-checksum_b298d29de9236ca47a023e382313bcc2d2eed31dfa706b60a04103ce83a71a25
( 20912861 bytes)

I can add a job to check for 0 byte tarballs. Do you think that would be
helpful?


On Thu, Apr 29, 2021 at 4:26 PM Khem Raj  wrote:

> you also want to get rid of *.lock files as well.
>
> On Thu, Apr 29, 2021 at 4:24 PM Khem Raj  wrote:
> >
> > Adding Miachel as well.
> >
> > this seems to be running
> > buildoptions.SourceMirroring.test_yocto_source_mirror selftest, which
> > AFAICT should force downloads from yp mirror only
> > when I check the YP mirror then this tarball exists there
> >
> > http://downloads.yoctoproject.org/mirror/sources/go1.16.3.src.tar.gz
> >
> > but problem is that its 0 sized.
> >
> > Secondly I also see a bad checksum file there
> >
> >
> http://downloads.yoctoproject.org/mirror/sources/go1.16.3.src.tar.gz_bad-checksum_b298d29de9236ca47a023e382313bcc2d2eed31dfa706b60a04103ce83a71a25
> >
> > I am seeing that there are lot of *_bad-checksum_* files in YP src
> > mirror http://downloads.yoctoproject.org/mirror/sources/
> >
> > Michael,
> >
> > Can we delete these *_bad-checksum_* files as well as zero-sized
> > tarballs please?
> >
> > On Thu, Apr 29, 2021 at 3:57 PM Alexandre Belloni
> >  wrote:
> > >
> > > Hello,
> > >
> > > On 20/04/2021 11:28:38-0700, Khem Raj wrote:
> > > > golang.org/dl is resolving to this anyway
> > > >
> > >
> > > Unfortunately, this is still an issue on the autobuilders:
> > >
> > > ERROR: go-cross-core2-32-1.16.3-r0 do_fetch: The URL: '
> https://dl.google.com/go/go1.16.3.src.tar.gz;name=main' is not trusted
> and cannot be used
> > > ERROR: go-cross-core2-32-1.16.3-r0 do_fetch: Fetcher failure for URL: '
> https://dl.google.com/go/go1.16.3.src.tar.gz;name=main'. Unable to fetch
> URL from any source.
> > > ERROR: Logfile of failure stored in:
> /home/pokybuild/yocto-worker/a-quick/build/build-st/tmp/work/x86_64-linux/go-cross-core2-32/1.16.3-r0/temp/log.do_fetch.525
> > > ERROR: go-runtime-1.16.3-r0 do_fetch: The URL: '
> https://dl.google.com/go/go1.16.3.src.tar.gz;name=main' is not trusted
> and cannot be used
> > > ERROR: go-runtime-1.16.3-r0 do_fetch: Fetcher failure for URL: '
> https://dl.google.com/go/go1.16.3.src.tar.gz;name=main'. Unable to fetch
> URL from any source.
> > > ERROR: Logfile of failure stored in:
> /home/pokybuild/yocto-worker/a-quick/build/build-st/tmp/work/core2-32-poky-linux/go-runtime/1.16.3-r0/temp/log.do_fetch.544
> > >
> > > This is fairly reproducible:
> > >
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/1404/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/1403/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/1402/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/1401/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2076/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2074/steps/23/logs/stdio
> > >
> https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/2070/steps/23/logs/stdio
> > >
> > >
> > > > Signed-off-by: Khem Raj 
> > > > ---
> > > >  meta/recipes-devtools/go/go-common.inc | 2 +-
> > > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > >
> > > > diff --git a/meta/recipes-devtools/go/go-common.inc
> b/meta/recipes-devtools/go/go-common.inc
> > > > index 39a681a712..c368b95b69 100644
> > > > --- a/meta/recipes-devtools/go/go-common.inc
> > > > +++ b/meta/recipes-devtools/go/go-common.inc
> > > > @@ -14,7 +14,7 @@ LICENSE = "BSD-3-Clause"
> > > >
> > > >  inherit goarch
> > > >
> > > > -SRC_URI = "https://golang.org/dl/go${PV}.src.tar.gz;name=main;
> > > > +SRC_URI = "https://dl.google.com/go/go${PV}.src.tar.gz;name=main;
> > > >  S = "${WORKDIR}/go"
> > > >  B = "${S}"
> > > >  UPSTREAM_CHECK_REGEX = "(?P\d+(\.\d+)+)\.src\.tar"
> > > > --
> > > > 2.31.1
> > > >
> > >
> > > >
> > > > 
> > > >
> > >
> > >
> > > --
> > > Alexandre Belloni, co-owner and COO, Bootlin
> > > Embedded Linux and Kernel engineering
> > > https://bootlin.com
>


-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#151151): 
https://lists.openembedded.org/g/openembedded-core/message/151151
Mute This Topic: https://lists.openembedded.org/mt/82241899/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] yocto-uninative.inc: version 3.0 incorporate seccomp filter workaround

[Michael Halstead]

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index bc47083978..a2a2dd18ec 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -8,7 +8,7 @@
 
 UNINATIVE_MAXGLIBCVERSION = "2.33"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.11/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"fa703e25c26eaebb1afd895337b92a24cc5077818e093af74912e53846a117fe"
-UNINATIVE_CHECKSUM[i686] ?= 
"638901c990ffbe716a34400134a2ad49a1c3104e3b48cdafd6fcd28e9b133294"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"047ddd78d6b5cabd2a102120e27755a9eaa1d5724c6a8f4007daa3f10ecb6871"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/3.0/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"1c668909098c5b56132067adc69a249cb771f4560428e5822de903a12d97bf33"
+UNINATIVE_CHECKSUM[i686] ?= 
"e6cc2fc056234cffa6a2ff084cce27d544ea3f487a62b5e253351cefd4421900"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"5ec5a9276046e7eceeac749a18b175667384e1f445cd4526300a41404d985a5b"
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#148000): 
https://lists.openembedded.org/g/openembedded-core/message/148000
Mute This Topic: https://lists.openembedded.org/mt/80603930/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] yocto-uninative.inc: version 2.11 updates glibc to 2.33

[Michael Halstead]

Support glibc 2.33.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 69b6edee5f..bc47083978 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,9 +6,9 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.32"
+UNINATIVE_MAXGLIBCVERSION = "2.33"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.9/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"9f25a667aee225b1dd65c4aea73e01983e825b1cb9b56937932a1ee328b45f81"
-UNINATIVE_CHECKSUM[i686] ?= 
"cae5d73245d95b07cf133b780ba3f6c8d0adca3ffc4e7e7fab61d5e24d36"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.11/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"fa703e25c26eaebb1afd895337b92a24cc5077818e093af74912e53846a117fe"
+UNINATIVE_CHECKSUM[i686] ?= 
"638901c990ffbe716a34400134a2ad49a1c3104e3b48cdafd6fcd28e9b133294"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"047ddd78d6b5cabd2a102120e27755a9eaa1d5724c6a8f4007daa3f10ecb6871"
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#147715): 
https://lists.openembedded.org/g/openembedded-core/message/147715
Mute This Topic: https://lists.openembedded.org/mt/80423308/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] uninative: Upgrade to 2.10

[Michael Halstead]

Final glibc 2.32 based uninative.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index 69b6edee5f..85336014b1 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -8,7 +8,7 @@
 
 UNINATIVE_MAXGLIBCVERSION = "2.32"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.9/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"9f25a667aee225b1dd65c4aea73e01983e825b1cb9b56937932a1ee328b45f81"
-UNINATIVE_CHECKSUM[i686] ?= 
"cae5d73245d95b07cf133b780ba3f6c8d0adca3ffc4e7e7fab61d5e24d36"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"d07916b95c419c81541a19c8ef0ed8cbd78ae18437ff28a4c8a60ef40518e423"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.10/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"645e5c50b2b48aabb8b10f783a9f94b4b7c5ddc7cfceb5386d43b86d30253202"
+UNINATIVE_CHECKSUM[i686] ?= 
"233e09b5ff30e15341232a0c16fa8448ff31dccb8f3f3e2ad3948cdac8c4a598"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"04333677f81990ce2cf55c3bc256cd84a66085d18fc95ccddfab8581e4aec014"
-- 
2.29.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#147714): 
https://lists.openembedded.org/g/openembedded-core/message/147714
Mute This Topic: https://lists.openembedded.org/mt/80423223/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Brief git.openembedded.org Downtime

[Michael Halstead]

This work is complete and all services are available. As a bonus the new
hardware is faster.

Service restored at 2020-04-25 20:14 PDT.

On Sat, Apr 25, 2020 at 5:52 PM Michael Halstead via lists.openembedded.org
 wrote:

> There is a potential issue with the physical machine hosting
> git.openembedded.org. I'm going to take the VM offline to move it to new
> hardware. The process should take less than 30 minutes.  Full backups have
> been taken in case of unexpected failures.
>
> The downtime will begin in about 2 hours starting at 2020-04-25 20:00 PDT.
> I will e-mail when the process is complete.
>
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>
>
> 
>


-- 

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#137495): 
https://lists.openembedded.org/g/openembedded-core/message/137495
Mute This Topic: https://lists.openembedded.org/mt/73274306/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Brief git.openembedded.org Downtime

[Michael Halstead]

There is a potential issue with the physical machine hosting
git.openembedded.org. I'm going to take the VM offline to move it to new
hardware. The process should take less than 30 minutes.  Full backups have
been taken in case of unexpected failures.

The downtime will begin in about 2 hours starting at 2020-04-25 20:00 PDT.
I will e-mail when the process is complete.

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#137493): 
https://lists.openembedded.org/g/openembedded-core/message/137493
Mute This Topic: https://lists.openembedded.org/mt/73274306/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [bitbake-devel] Mailing list platform change March 20th

[Michael Halstead]

The migration to Groups.io is nearly complete. All functionality is ready
to use and you can send e-mail now. Archives are in place except for the
most recent from the Openembedded-commits list. Those are continuing to
import.

There is no need to update your address book as the list addresses have not
changed.

If you encounter any issues please visit
https://www.openembedded.org/wiki/GroupsMigration for the latest
information. If your concern isn't addressed e-mail me directly.

Thank you,
--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer


On Fri, Mar 20, 2020 at 1:56 PM akuster808  wrote:

> Micheal,
>
> Thanks for doing this.
>
> So just for my clarification, there is no needed to update any README to
> use a different e-mail to like we did for the Yocto transitions since oe is
> already using "lists.openembedded.org"
>
> - armin
>
>
> On 3/20/20 11:59 AM, Michael Halstead wrote:
>
> The migration will begin shortly. List mail will be delayed until the
> process is complete. E-mail sent during downtime should eventually be
> delivered. However waiting to send until after the switch is recommended.
>
> Thank you,
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>
> On Thu, Mar 19, 2020 at 9:44 AM Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> Everything is proceeding smoothly and this work will continue as planned.
>> The migration starts at noon PDT tomorrow.
>>
>> List owners please take care of all outstanding moderation in the next 24
>> hours to ensure a smooth transition.
>>
>> Thank you,
>> --
>> Michael Halstead
>> Linux Foundation / Yocto Project
>> Systems Operations Engineer
>>
>> On Fri, Mar 13, 2020 at 4:58 PM Michael Halstead <
>> mhalst...@linuxfoundation.org> wrote:
>>
>>> We are moving our lists from Mailman to Groups.io. E-mail to lists will
>>> be delayed during the move window. We are aiming to complete the migration
>>> during business hours in the Pacific time zone.
>>>
>>> A new account will be created for you on the Groups.io platform if you
>>> don't already have one.
>>>
>>> You can read more about the change on the wiki:
>>> https://www.openembedded.org/wiki/GroupsMigration
>>>
>>> If there are serious issues we will rollback the changes. We will e-mail
>>> all lists when work is complete.
>>>
>>> --
>>> Michael Halstead
>>> Linux Foundation / Yocto Project
>>> Systems Operations Engineer
>>>
>>>
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#136569): 
https://lists.openembedded.org/g/Openembedded-core/message/136569
Mute This Topic: https://lists.openembedded.org/mt/72436512/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/Openembedded-core/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Mailing list platform change March 20th

[Michael Halstead]

The migration will begin shortly. List mail will be delayed until the
process is complete. E-mail sent during downtime should eventually be
delivered. However waiting to send until after the switch is recommended.

Thank you,
--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

On Thu, Mar 19, 2020 at 9:44 AM Michael Halstead <
mhalst...@linuxfoundation.org> wrote:

> Everything is proceeding smoothly and this work will continue as planned.
> The migration starts at noon PDT tomorrow.
>
> List owners please take care of all outstanding moderation in the next 24
> hours to ensure a smooth transition.
>
> Thank you,
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>
> On Fri, Mar 13, 2020 at 4:58 PM Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> We are moving our lists from Mailman to Groups.io. E-mail to lists will
>> be delayed during the move window. We are aiming to complete the migration
>> during business hours in the Pacific time zone.
>>
>> A new account will be created for you on the Groups.io platform if you
>> don't already have one.
>>
>> You can read more about the change on the wiki:
>> https://www.openembedded.org/wiki/GroupsMigration
>>
>> If there are serious issues we will rollback the changes. We will e-mail
>> all lists when work is complete.
>>
>> --
>> Michael Halstead
>> Linux Foundation / Yocto Project
>> Systems Operations Engineer
>>
>>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Mailing list platform change March 20th

[Michael Halstead]

Everything is proceeding smoothly and this work will continue as planned.
The migration starts at noon PDT tomorrow.

List owners please take care of all outstanding moderation in the next 24
hours to ensure a smooth transition.

Thank you,
--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

On Fri, Mar 13, 2020 at 4:58 PM Michael Halstead <
mhalst...@linuxfoundation.org> wrote:

> We are moving our lists from Mailman to Groups.io. E-mail to lists will
> be delayed during the move window. We are aiming to complete the migration
> during business hours in the Pacific time zone.
>
> A new account will be created for you on the Groups.io platform if you
> don't already have one.
>
> You can read more about the change on the wiki:
> https://www.openembedded.org/wiki/GroupsMigration
>
> If there are serious issues we will rollback the changes. We will e-mail
> all lists when work is complete.
>
> --
> Michael Halstead
> Linux Foundation / Yocto Project
> Systems Operations Engineer
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Mailing list platform change March 20th

[Michael Halstead]

We are moving our lists from Mailman to Groups.io. E-mail to lists will be
delayed during the move window. We are aiming to complete the migration
during business hours in the Pacific time zone.

A new account will be created for you on the Groups.io platform if you
don't already have one.

You can read more about the change on the wiki:
https://www.openembedded.org/wiki/GroupsMigration

If there are serious issues we will rollback the changes. We will e-mail
all lists when work is complete.

--
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] yocto-uninative.inc: version 2.8 updates glibc to 2.31

[Michael Halstead]

Allow sstate use in Tumbleweed and other distros as they update glibc.
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index ad75d3e2a3..889695eae3 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,9 +6,9 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.30"
+UNINATIVE_MAXGLIBCVERSION = "2.31"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.7/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"e76a45886ee8a0b3904b761c17ac8ff91edf9811ee455f1832d10763ba794dfc"
-UNINATIVE_CHECKSUM[i686] ?= 
"810d027dfb1c7675226afbcec07808770516c969ee7378f6d8240281083f8924"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"9498d8bba04749a7310ac2576d0796461184965351a56f6d32c888a1f216"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.8/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"989187344bf9539b464fb7ed9c223e51f4bdb4c7a677d2c314e6fed393176efe"
+UNINATIVE_CHECKSUM[i686] ?= 
"cc3e45bc8594488b407363e3fa9af5a099279dab2703c64342098719bd674990"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"a09922172c3a439105e0ae6b943daad2d83505b17da0aba97961ff433b8c21ab"
-- 
2.24.1

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] New Dedicated Licensing and Documentation Mailing Lists

[Michael Halstead]

We are adding new lists for topics concerning subcommunities that
will benefit from focused list traffic.


The licensing list will separate licensing and legal discussion from
general development to aid participation of specialists in this area.

Please join at https://lists.yoctoproject.org/g/licensing/join.


Join the docs list to discuss all things documentation and to
collaborate on the patches to the docs.

Please join at https://lists.yoctoproject.org/g/docs/join.

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] New Dedicated Licensing and Documentation Mailing Lists

[Michael Halstead]

We are adding new lists for topics concerning subcommunities that
will benefit from focused list traffic.


The licensing list will separate licensing and legal discussion from
general development to aid participation of specialists in this area.

Please join at https://lists.yoctoproject.org/g/licensing/join.


Join the docs list to discuss all things documentation and to
collaborate on the patches to the docs.

Please join at https://lists.yoctoproject.org/g/docs/join.

-- 
Michael Halstead
Linux Foundation / Yocto Project
Systems Operations Engineer
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/6] oe-selftest: extend virgl gtk test to also check the SDL option

[Michael Halstead]

On Fri, Nov 8, 2019 at 9:56 AM Alexander Kanavin 
wrote:

> On Fri, 8 Nov 2019 at 18:20, Michael Halstead <
> mhalst...@linuxfoundation.org> wrote:
>
>> > If you replace that with tigervnc (a modern, supported fork of
>> tightvnc), then the tests pass fine.
>> > https://tigervnc.org/
>> >
>>
>> TigerVNC is now installed from the standard repos where available.
>>
>> >
>> > As Fedora has already obsoleted tightvnc in favor of tigervnc, I think
>> we should do the same on all debian machines (debian provides both tightvnc
>> and tigervnc, but treats them as equal).
>> > https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package
>> > I also checked that tightvnc is not available for opensuse either.
>>
>>
>> Server components of TigerVNC are in xorg-x11-Xvnc package which is
>> installed on all the openSUSE workers so I expect the VNC server there to
>> work. Please let me know if they do not.
>>
>>
>> On Ubuntu 16.04 and Debian 8 workers I've installed from
>> https://bintray.com/tigervnc/stable/tigervnc/1.9.0. This should allow
>> tests to complete. Installing packages outside of the distribution's
>> package manager might invalidate these as sanity tested distros. I'd
>> appreciate feedback about this.
>>
>
> Thanks a lot! There are two things to check:
> 1. Old instances of vnc may still be running and should be shut down (via
> 'vncserver -kill :1')
> 2. vncserver executable should point to tigervnc (if both tigervnc and
> tightvnc are installed - I don't know if you removed the tightvnc packages).
>

I removed tightvnc and all workers have been rebooted so we are good to go.

Any comment on using packages from outside of the distro's official
packaging?


>
> Otherwise everything should be ready for re-testing the patches. I can
> resend them if needed.
>
> Alex
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 3/6] oe-selftest: extend virgl gtk test to also check the SDL option

[Michael Halstead]

On Mon, Nov 4, 2019 at 1:11 PM Alexander Kanavin 
wrote:
>
> On Sat, 2 Nov 2019 at 23:29, Alexander Kanavin 
wrote:
>>
>> Same failures on the Debian 10 worker:
>>>>
>>>>
>>>> https://autobuilder.yoctoproject.org/typhoon/#/builders/56/builds/778
>>>
>>>
>>> runqemu - ERROR - Failed to run qemu: Xlib:  extension "RANDR" missing
on display ":1".
>>> qemu-system-x86_64: ../libepoxy-1.5.3/src/dispatch_common.c:863:
epoxy_get_proc_address: Assertion `0 && "Couldn't find current GLX or EGL
context.\n"' failed.
>>>
>>> Thanks - the Gtk part is passing fine, so it's something SDL does that
upsets the X/GL stack on the Debian 10 host.
>>> I am reluctant to disable the SDL part of the virgl tests on Debian 10,
as it is a new distro (unlike centos 7).
>>>
>>> I'll try to see if I can run Debian 10 in a VM here and try to
reproduce. Or is it possible to debug directly on a Debian 10 worker?
>>
>>
>> So I actually went ahead, and installed Debian 10 into a qemu image,
then transferred a pre-populated build directory into it, and ran runqemu
there against tigervnc (hurray for the nested kvm feature!).
>>
>> Both 'runqemu kvm sdl gl' and 'runqemu kvm gtk gl' work fine, including
running kmscube!
>>
>> So I'd like to see what packages are installed on the Debian 10 worker
vs. my Debian 10 installation.
>>
>> Can you issue 'dpkg -l' on the worker, and send me the output, please?
Maybe something is missing?
>
>
> After additional digging I reproduced this. The culprit is the outdated
VNC server implementation that runs on the Debian 10 autobuilder (and maybe
others as well).
>
> Specifically, it's tightvncserver, where all Linux development has ceased
10 years ago (!).
> https://www.tightvnc.com/
>
> If you replace that with tigervnc (a modern, supported fork of tightvnc),
then the tests pass fine.
> https://tigervnc.org/
>

TigerVNC is now installed from the standard repos where available.

>
> As Fedora has already obsoleted tightvnc in favor of tigervnc, I think we
should do the same on all debian machines (debian provides both tightvnc
and tigervnc, but treats them as equal).
> https://src.fedoraproject.org/rpms/tightvnc/blob/master/f/dead.package
> I also checked that tightvnc is not available for opensuse either.


Server components of TigerVNC are in xorg-x11-Xvnc package which is
installed on all the openSUSE workers so I expect the VNC server there to
work. Please let me know if they do not.


On Ubuntu 16.04 and Debian 8 workers I've installed from
https://bintray.com/tigervnc/stable/tigervnc/1.9.0. This should allow tests
to complete. Installing packages outside of the distribution's package
manager might invalidate these as sanity tested distros. I'd appreciate
feedback about this.

--
Michael Halstead
Yocto Project / SysAdmin


>
> Alex
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH v2] uninative: Update to 2.7 release

[Michael Halstead]

The 2.7 release updates glibc to version 2.30. Recently added to openSUSE
Tumbleweed and needed for Fedora Core 31.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 10 +-
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index df24346855..ad75d3e2a3 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -6,9 +6,9 @@
 # to the distro running on the build machine.
 #
 
-UNINATIVE_MAXGLIBCVERSION = "2.29"
+UNINATIVE_MAXGLIBCVERSION = "2.30"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.6/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"a37118fc8b423f48146120707b81dd15017512c3e8ef9e6ca2cb3a033f4f4046"
-UNINATIVE_CHECKSUM[i686] ?= 
"3234fc3ded810225071f23a0e9a99f4f8c2480059945a848eff076ce78122ade"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"133387753a9acf3e1b788103c59fac91e968e2ee331d7a4b9498e926ada7be57"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.7/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"e76a45886ee8a0b3904b761c17ac8ff91edf9811ee455f1832d10763ba794dfc"
+UNINATIVE_CHECKSUM[i686] ?= 
"810d027dfb1c7675226afbcec07808770516c969ee7378f6d8240281083f8924"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"9498d8bba04749a7310ac2576d0796461184965351a56f6d32c888a1f216"
-- 
2.21.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] uninative: Update to 2.7 release

[Michael Halstead]

The 2.7 release updates glibc to version 2.30. Recently added to openSUSE
Tumbleweed and needed for Fedora Core 31.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 8 
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index df24346855..42fed6f2ba 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -8,7 +8,7 @@
 
 UNINATIVE_MAXGLIBCVERSION = "2.29"
 
-UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.6/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"a37118fc8b423f48146120707b81dd15017512c3e8ef9e6ca2cb3a033f4f4046"
-UNINATIVE_CHECKSUM[i686] ?= 
"3234fc3ded810225071f23a0e9a99f4f8c2480059945a848eff076ce78122ade"
-UNINATIVE_CHECKSUM[x86_64] ?= 
"133387753a9acf3e1b788103c59fac91e968e2ee331d7a4b9498e926ada7be57"
+UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.7/;
+UNINATIVE_CHECKSUM[aarch64] ?= 
"e76a45886ee8a0b3904b761c17ac8ff91edf9811ee455f1832d10763ba794dfc"
+UNINATIVE_CHECKSUM[i686] ?= 
"810d027dfb1c7675226afbcec07808770516c969ee7378f6d8240281083f8924"
+UNINATIVE_CHECKSUM[x86_64] ?= 
"9498d8bba04749a7310ac2576d0796461184965351a56f6d32c888a1f216"
-- 
2.21.0

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH][V2] sdkext: use simpler kernel module for devtool test

[Michael Halstead]

On 9/5/19 2:27 PM, richard.pur...@linuxfoundation.org wrote:
> On Thu, 2019-09-05 at 13:54 -0400, Mark Asselstine wrote:
>> On Thursday, August 22, 2019 11:56:16 A.M. EDT Mark Asselstine wrote:
>>> The current devtool test for the building of an out-of-tree kernel
>>> module uses something which requires several "high order" kconfigs
>>> to
>>> be set. This results in the test failing, not for expected reasons,
>>> but rather because it depends on specific kernel configuration.
>>>
>>> You will get error messages such as
>>>
>>>   ERROR: "video_ioctl2"
>>>  
>>> [.../1.0-r5/testsdkext/workspace/sources/v4l2loopback-
>>> driver/v4l2loopback.k
>>> o] undefined!
>>>   ERROR: "video_unregister_device"
>>>  
>>> [.../1.0-r5/testsdkext/workspace/sources/v4l2loopback-
>>> driver/v4l2loopback.k
>>> o] undefined!
>>>
>>> Using a simpler hello-world kernel module example will only require
>>> that CONFIG_MODULE is enabled, thus avoiding a false positive.
>>>
>>> Signed-off-by: Mark Asselstine 
>>> ---
>>>
>>> **V2**
>>>  - also updated the CROPS manual test json file
>>>(I have no idea how to run this so untested but this is a
>>> straight
>>> substition)
>>>  - continue to use github until we can move the sample to somewhere
>>>like git.yoctoproject.org
>> Richard, are you thinking we need to figure out the
>> git.yoctoproject.org repo 
>> before we can move ahead with merging this?
> I would like to fix that, yes. I could ask Michael for help but I do
> have access to sort it myself too.
>
> I'm also trying to sort out a few other issues before -next can merge.
>
> Since I'm failing to get to it,
>
> Michael,
>
> Could you clone:
>
> https://github.com/masselstine/kernel-module-hello-world.git 
>
> onto git.yp.org as a new repo and give write access to it for Mark,
> myself, Bruce and Ross please?

This repo is ready at
g...@push.yoctoproject.org:kernel-module-hello-world for the four of you.

It is available read-only for anyone at,

git://git.yoctoproject.org/kernel-module-hello-world

and

https://git.yoctoproject.org/git/pokykernel-module-hello-world

>
> Cheers,
>
> Richard
>
>
>
-- 
Michael Halstead
Linux Foundation / SysAdmin

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 2/4] python3-numpy: update to 1.17.0

[Michael Halstead]

On 8/13/19 2:54 AM, Alexander Kanavin wrote:
> On Tue, 13 Aug 2019 at 10:34, Richard Purdie
>  <mailto:richard.pur...@linuxfoundation.org>> wrote:
>
>
> This doesn't build on opensuse 42.3:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/52/builds/907
>
> Its numpy-native and looks like it might be the old compiler :(
>
>
> That version of opensuse went end-of-life about a month ago. We can
> hold this off until the autobuilder is upgraded.
>
> Alex
I'm ready to drop this worker at any time. opensuse-42.3 is still a
SANITY_TESTED_DISTRO. Is it fine to go ahead and remove this?

-- 
Michael Halstead
Linux Foundation / SysAdmin

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [yocto] patchwork

[Michael Halstead]

On 5/13/19 1:59 AM, Mark Hatle wrote:
> On 5/13/19 10:46 AM, Adrian Bunk wrote:
>> On Mon, May 13, 2019 at 10:32:48AM +0300, Mark Hatle wrote:
>>> On 5/12/19 9:04 PM, akuster808 wrote:
>>>> ok, so no Admins. This is unexceptionable.
>>>>
>>>> OE TSC and Board, I believe its your time to get involved.
>>> I've not used patchwork before, do you know who originally configured it?  
>>> Was
>>> it Paul Eggleton, or Richard, or?  If I have an idea who was originally
>>> responsible, I'm pretty sure we can figure out a handoff plan to someone 
>>> else.
>> http://git.yoctoproject.org/cgit/cgit.cgi/patchwork/
> No I mean who set it up for OE (or the YP) to use.  I don't even know at this
> point whose infrastructure the component runs on.  If I had that I'd know to
> start with either Tom or Michael.
>
> --Mark

I set the OE Patchwork up with Jose Lamego's help and maintain that
server now.


>>> --Mark
>> cu
>> Adrian
>>
-- 
Michael Halstead
Linux Foundation / SysAdmin

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Yocto Project Status WW07'19

[Michael Halstead]

The regular 3 hour update wasn't installed on the new server. I have 
repaired that and added the RRS updates as well..


The update has been run several times in testing and I'm curious if RRS 
has caught up as expected.


On 2/12/19 5:57 PM, Paul Eggleton wrote:

Hi Alex

On Wednesday, 13 February 2019 6:22:23 AM NZDT Alexander Kanavin wrote:

On Tue, 12 Feb 2019 at 17:10,  wrote:

The recipe reporting system integration with the layer index is available
at: https://layers.openembedded.org/rrs/recipes/OE-Core/2.7/M3/ and the
historical data has now been imported.

Sadly the new RRS still seems to be suffering from the 'outdated info'
problem. For example glibc, or python3 recipes have been updated to
latest versions, yet RRS still shows that they haven't been.

We're reliant upon the layer index updating and it appears that's not working
at the moment. I have asked Michael to look into it. Thanks for the report,
I'll reply back here when things are sorted out.

Cheers,
Paul


--
Michael Halstead
Linux Foundation / SysAdmin

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] ✗ patchtest: failure for Shorten file names in sstate-cache

[Michael Halstead]

On 1/11/19 9:16 AM, Paul Barker wrote:

On Fri, 11 Jan 2019, at 17:05, Patchwork wrote:

== Series Details ==

Series: Shorten file names in sstate-cache
Revision: 1
URL   : https://patchwork.openembedded.org/series/15617/
State : failure

That's weird... the patch applies fine onto master here, I've just tested 
applying it to a clean clone of openembedded-core.


The patchtest server was stuck resetting its working repository to a 
local merge. I've repaired the issue on the patchtest server and 
submitted 
https://lists.yoctoproject.org/pipermail/yocto/2019-January/043790.html 
to prevent it from reoccurring.



== Summary ==


Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the proposed
series by patchtest resulting in the following failures:



* Issue Series does not apply on top of target branch
[test_series_merge_on_head]
   Suggested fixRebase your series on top of targeted branch
   Targeted branch  master (currently at 65c419b8c4)

Git can't find a commit hash starting with 65c419b8c4 in poky or oe-core.




If you believe any of these test results are incorrect, please reply to the
mailing list (openembedded-core@lists.openembedded.org) raising your concerns.
Otherwise we would appreciate you correcting the issues and submitting a new
version of the patchset if applicable. Please ensure you add/increment the
version number when sending the new version (i.e. [PATCH] -> [PATCH v2] ->
[PATCH v3] -> ...).

---
Guidelines:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines
Test framework: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest
Test suite: http://git.yoctoproject.org/cgit/cgit.cgi/patchtest-oe




--
Michael Halstead
Linux Foundation / SysAdmin

--
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [OE-Core][PATCH] yocto-uninative: Correct sha256sum for aarch64

[Michael Halstead]

Avoid uninative checksum warnings when building on aarch64 hardware.

Signed-off-by: Michael Halstead 
---
 meta/conf/distro/include/yocto-uninative.inc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/conf/distro/include/yocto-uninative.inc 
b/meta/conf/distro/include/yocto-uninative.inc
index c9d502ba4f..0d484f6c3c 100644
--- a/meta/conf/distro/include/yocto-uninative.inc
+++ b/meta/conf/distro/include/yocto-uninative.inc
@@ -9,7 +9,7 @@
 UNINATIVE_MAXGLIBCVERSION = "2.28"
 
 UNINATIVE_URL ?= "http://downloads.yoctoproject.org/releases/uninative/2.3/;
-UNINATIVE_CHECKSUM[aarch64] ?= 
"b7fbbaad1ec86d76eca84d83098f50525b8a4124cc8685eaed"
+UNINATIVE_CHECKSUM[aarch64] ?= 
"e495046969c796b7fbbaad1ec86d76eca84d83098f50525b8a4124cc8685eaed"
 UNINATIVE_CHECKSUM[i686] ?= 
"44253cddbf629082568cea4fff59419106871a0cf81b4845b5d34e7014887b20"
 UNINATIVE_CHECKSUM[x86_64] ?= 
"c6954563dad3c95608117c6fc328099036c832bbd924ebf5fdccb622fc0a8684"
 
-- 
2.17.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 3/3] scripts/autobuilder-worker-prereq-tests: Shore up qemu testing

[Michael Halstead]

Check that yocto-autobuilder-helper has been cloned to the correct location.
Check that vnc is running using the same script the autobuilder does.
Set the DISPLAY enviroment variable to :1 the same way we do when building
normally.
Make the VM's serial console available so we can log in and power off allowing
the tests to continue.

Signed-off-by: Michael Halstead 
---
 scripts/autobuilder-worker-prereq-tests | 10 --
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/scripts/autobuilder-worker-prereq-tests 
b/scripts/autobuilder-worker-prereq-tests
index bb46c69135..358dd2beee 100755
--- a/scripts/autobuilder-worker-prereq-tests
+++ b/scripts/autobuilder-worker-prereq-tests
@@ -15,6 +15,12 @@
 # test buildistory git repo works?
 #
 
+if [ ! -x $HOME/yocto-autobuilder-helper/scripts/checkvnc ]; then
+echo "$HOME/yocto-autobuilder-helper should be created."
+exit 1
+fi
+$HOME/yocto-autobuilder-helper/scripts/checkvnc
+
 . ./oe-init-build-env > /dev/null
 if [ "$?" != "0" ]; then
 exit 1
@@ -53,12 +59,12 @@ if [ ! -e bzImage-qemux86-64.bin ]; then
 fi
 popd
 bitbake qemu-helper-native
-runqemu qemux86-64
+DISPLAY=:1 runqemu serialstdio qemux86-64
 if [ "$?" != "0" ]; then
 echo "Unable to use runqemu"
 exit 1
 fi
-runqemu qemux86-64 kvm
+DISPLAY=:1 runqemu serialstdio qemux86-64 kvm
 if [ "$?" != "0" ]; then
 echo "Unable to use runqemu with kvm"
 exit 1
-- 
2.17.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 2/3] scripts/runqemu: Replace subprocess.run() for compatibilty

[Michael Halstead]

subprocess.run() was introduced in Python 3.5. We currently support down to
Python 3.4 so I've replaced it with subprocess.check_call() which is available
in that version.

Signed-off-by: Michael Halstead 
---
 scripts/runqemu | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 0c61253d6a..c79be9a846 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -1321,7 +1321,7 @@ def main():
 logger.info("SIGTERM received")
 os.kill(config.qemupid, signal.SIGTERM)
 config.cleanup()
-subprocess.run(["tput", "smam"])
+subprocess.check_call(["tput", "smam"])
 signal.signal(signal.SIGTERM, sigterm_handler)
 
 config.check_args()
@@ -1343,7 +1343,7 @@ def main():
 return 1
 finally:
 config.cleanup()
-subprocess.run(["tput", "smam"])
+subprocess.check_call(["tput", "smam"])
 
 if __name__ == "__main__":
 sys.exit(main())
-- 
2.17.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH 1/3] scripts/runqemu: Add serialstdio mode

[Michael Halstead]

From: Richard Purdie 

Its currently not possible to have a console available whilst using qemu in 
graphics
mode. This is causing some issues for testing autobuilder bringup so all a 
"serialstdio"
mode to runqemu to accomodate this.

The existing serialstdio internal variable is renamed to allow the new user 
visible option.

Signed-off-by: Richard Purdie 
---
 scripts/runqemu | 9 +++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/scripts/runqemu b/scripts/runqemu
index 087220ca0a..0c61253d6a 100755
--- a/scripts/runqemu
+++ b/scripts/runqemu
@@ -75,6 +75,7 @@ of the following environment variables (in any order):
   Simplified QEMU command-line options can be passed with:
 nographic - disable video console
 serial - enable a serial console on /dev/ttyS0
+serialstdio - enable a serial console on the console (regardless of 
graphics mode)
 slirp - enable user networking, no root privileges is required
 kvm - enable KVM when running x86/x86_64 (VT-capable CPU required)
 kvm-vhost - enable KVM with vhost when running x86/x86_64 (VT-capable CPU 
required)
@@ -211,6 +212,7 @@ class BaseConfig(object):
 self.slirp_enabled = False
 self.nfs_instance = 0
 self.nfs_running = False
+self.serialconsole = False
 self.serialstdio = False
 self.cleantap = False
 self.saved_stty = ''
@@ -428,6 +430,9 @@ class BaseConfig(object):
 self.qemu_opt_script += ' -nographic'
 self.kernel_cmdline_script += ' console=ttyS0'
 elif arg == 'serial':
+self.kernel_cmdline_script += ' console=ttyS0'
+self.serialconsole = True
+elif arg == "serialstdio":
 self.kernel_cmdline_script += ' console=ttyS0'
 self.serialstdio = True
 elif arg == 'audio':
@@ -1169,7 +1174,7 @@ class BaseConfig(object):
 if self.snapshot:
 self.qemu_opt += " -snapshot"
 
-if self.serialstdio:
+if self.serialconsole:
 if sys.stdin.isatty():
 subprocess.check_call("stty intr ^]", shell=True)
 logger.info("Interrupt character is '^]'")
@@ -1196,7 +1201,7 @@ class BaseConfig(object):
 # INIT: Id "S1" respawning too fast: disabled for 5 minutes
 serial_num = len(re.findall("-serial", self.qemu_opt))
 if serial_num == 0:
-if re.search("-nographic", self.qemu_opt):
+if re.search("-nographic", self.qemu_opt) or self.serialstdio:
 self.qemu_opt += " -serial mon:stdio -serial null"
 else:
 self.qemu_opt += " -serial mon:vc -serial null"
-- 
2.17.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] [PATCH] scripts/autobuilder-worker-prereq-tests: adjust max_user_watches

[Michael Halstead]

Temporarily modify path to run as non-privileged user on more distros.
Change the recommended value to match what we use on the autobuilder.

Signed-off-by: Michael Halstead 
---
 scripts/autobuilder-worker-prereq-tests | 9 +
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/scripts/autobuilder-worker-prereq-tests 
b/scripts/autobuilder-worker-prereq-tests
index c0148fbce8..bb46c69135 100755
--- a/scripts/autobuilder-worker-prereq-tests
+++ b/scripts/autobuilder-worker-prereq-tests
@@ -34,10 +34,11 @@ if [ "$?" != "0" ]; then
 echo "Bitbake parsing failed"
 exit 1
 fi
-WATCHES=`sysctl fs.inotify.max_user_watches -n`
-if (( $WATCHES < 10 )); then
-echo 'Need to increase watches (echo fs.inotify.max_user_watches=524288 | 
sudo tee -a /etc/sysctl.conf'
-#exit 1
+
+WATCHES=$(PATH="/sbin:/usr/sbin:$PATH" sysctl fs.inotify.max_user_watches -n)
+if (( $WATCHES < 65000 )); then
+echo 'Need to increase watches (echo fs.inotify.max_user_watches=65536 | 
sudo tee -a /etc/sysctl.conf'
+exit 1
 fi
 mkdir -p tmp/deploy/images/qemux86-64
 pushd tmp/deploy/images/qemux86-64
-- 
2.17.2

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH 14/14] babeltrace: switch over to git

[Michael Halstead]

That file is now available from the yoctoproject.org link you provided.
It probably appeared a few days later. Is there any issue now?


On 05/08/2018 02:25 AM, Burton, Ross wrote:
> CCing Halstead who does.  Hopefully the autobuilder.yocto.io
> <http://autobuilder.yocto.io> cache has
> a babeltrace-1.5.5.tar.bz2 tarball we can add to the mirror?
>
> Ross
>
> On 7 May 2018 at 11:17, Alexander Kanavin
> <alexander.kana...@linux.intel.com
> <mailto:alexander.kana...@linux.intel.com>> wrote:
>
> On 05/04/2018 10:51 PM, Martin Jansa wrote:
>
> Can you please upload the tarball (I assume you still have it
> from the time you were testing the upgrade to 1.5.5) to:
> 
> http://downloads.yoctoproject.org/mirror/sources/babeltrace-1.5.5.tar.bz2
> 
> <http://downloads.yoctoproject.org/mirror/sources/babeltrace-1.5.5.tar.bz2>
> or
> http://sources.openembedded.org/babeltrace-1.5.5.tar.bz2
> <http://sources.openembedded.org/babeltrace-1.5.5.tar.bz2>
> so that it's covered with default mirrors.bbclass as well?
>
>
> I don't have upload rights to that.
>
> Alex
>
> -- 
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> <mailto:Openembedded-core@lists.openembedded.org>
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> <http://lists.openembedded.org/mailman/listinfo/openembedded-core>
>
>

-- 
Michael Halstead
Linux Foundation / SysAdmin



signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Fwd: confirm 6bb527bbc2e6d9a2a2165aa081ea1271ece07fe8

[Michael Halstead]

We had several hundred bounces from Gmail today. I've made changes and
Gmail is currently accepting new messages.

I'm running a script to clear users' bounce counts now.

-- 
Michael Halstead
SysAdmin


On Thu, Mar 29, 2018 at 3:11 PM, Andrea Galbusera <giz...@gmail.com> wrote:

> On Thu, Mar 29, 2018 at 11:56 PM, Martin Jansa <martin.ja...@gmail.com>
> wrote:
> > I got the same today.
>
> Me too!
>
> >
> > On Thu, Mar 29, 2018 at 11:51 PM, Trevor Woerner <twoer...@gmail.com>
> wrote:
> >>
> >> uhhh gmail is on the bad list?
> >> anyone else get one of these?
> >>
> >>
> >> -- Forwarded message --
> >> From: <openembedded-core-requ...@lists.openembedded.org>
> >> Date: Thu, Mar 29, 2018 at 8:13 AM
> >> Subject: confirm
> >> To: twoer...@gmail.com
> >>
> >>
> >> Your membership in the mailing list Openembedded-core has been
> >> disabled due to excessive bounces The last bounce received from you
> >> was dated 29-Mar-2018.  You will not get any more messages from this
> >> list until you re-enable your membership.  You will receive 3 more
> >> reminders like this before your membership in the list is deleted.
> >>
> >>
> >> --
> >> ___
> >> Openembedded-core mailing list
> >> Openembedded-core@lists.openembedded.org
> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >>
> >
> >
> > --
> > ___
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
> >
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] errors.yoctoproject.org refusing connections?

[Michael Halstead]

On 08/14/2017 04:12 AM, Martin Jansa wrote:
> Hi,
> recently couple uploads to errors.yoctoproject.org 
> <http://errors.yoctoproject.org> end with "Connection reset by peer":
> NOTE: Uploading the report 
> /home/jenkins/oe/world/shr-core/tmp-glibc/log/error-report/error_report_20170813141910.txt
>  to errors.yoctoproject.org:80 <http://errors.yoctoproject.org:80>
> WARNING: Server connection failed [Errno 104] Connection reset by peer
> NOTE: Build completion summary:
> is there some issue on the server or just regular maintenance/upgrades of the 
> application which I just happen to hit quite often? I wasn't seeing so many 
> errors until recently (last month or so).
> Regards,

The filesystem was near capacity causing some new uploads to fail. I've
made more room right now. I'll plan to move to newer hardware in the
future which should help with other issues.

-- 
Michael Halstead
Linux Foundation / SysAdmin

-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Building logrotate for older releases is broken

[Michael Halstead]

On 04/20/2017 09:12 AM, Burton, Ross wrote:
>
> On 20 April 2017 at 13:51, Peter Kjellerstedt
> <peter.kjellerst...@axis.com <mailto:peter.kjellerst...@axis.com>> wrote:
>
> The integration of this patch into OE-Core has broken building old
> releases that rely on fetching the logrotate-3.9.1.tar.gz tar ball
> with MD5 checksum 4492b145b6d542e4a2f41e77fa199ab0 from the mirror
> at http://downloads.yoctoproject.org/mirror/sources/
> <http://downloads.yoctoproject.org/mirror/sources/>. Can you please
> change the recipe to not call the downloaded tar ball the same name
> as it had in Jethro, Krogoth and Morty (given that the checksums do
> not match), and then restore the original tar ball in the mirror?
>
>
> Eek, of course. :(
>
> Staged a revert locally for pyro/master.
>
> Michael, would it be possible to restore this older logrotate tarball
> to the mirror?  We might need donations of a tarball...
>
I've restored "4492b145b6d542e4a2f41e77fa199ab0  logrotate-3.9.1.tar.gz"
on downloads.yoctoproject.org and set it so it can't be overwritten.

Please let me know if anything else is required.

> Ross

-- 
Michael Halstead
Linux Foundation / SysAdmin



signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2

[Michael Halstead]

On Feb 22, 2017 1:56 PM, "Derek Straka" <de...@asterius.io> wrote:

Martin - No problem.  I'll resend the patches.

Michael - Would it be worth waiting before I resend the change sets?  It
looks like at least a subset of them have made it through.


Please wait while I make sure this problem is correctly resolved before
re-sending. I'll e-mail once we're ready.


Thanks.

-Derek

On Wed, Feb 22, 2017 at 3:55 PM, Michael Halstead <
mhalst...@linuxfoundation.org> wrote:

> I've seen several issues with hooks. I was working on them yesterday and
> will continue today.
>
> These are currently managed by hand but we are moving them into
> configuration management which should help keep them working consistently.
>
> On Feb 22, 2017 12:47 PM, "Martin Jansa" <martin.ja...@gmail.com> wrote:
>
>> On Wed, Feb 22, 2017 at 12:45:36PM -0500, Derek Straka wrote:
>> > Signed-off-by: Derek Straka <de...@asterius.io>
>>
>> It's not your fault Derek, but most of the patches from today and based
>> on the pings from today also some earlier patches didn't make it into
>> patchwork. This one is the only exception.
>>
>> Michael, Jose: are you aware of some issues with patchwork? Could it be
>> caused by the default Reply-to change from yesterday (or day before
>> during OEDAM)?
>>
>> I know only about issues processing merged changes:
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
>> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759
>>
>> And also UI issue in patchwork that paging doesn't work, e.g.:
>> https://patchwork.openembedded.org/bundle/jama/master-next/?
>> submitterboth
>> shows that there are 5 pages of changes (which should be in most cases
>> marked as accepted by the hook above), but clicking on 2nd page produces
>> link which drops the query parameters:
>> https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
>> so it says "No patches to display"
>>
>> Regards,
>>
>> > ---
>> >  .../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb}
>>  | 4 ++--
>> >  1 file changed, 2 insertions(+), 2 deletions(-)
>> >  rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb
>> => python-paho-mqtt_1.2.bb} (68%)
>> >
>> > diff --git a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.b
>> b b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
>> > similarity index 68%
>> > rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb
>> > rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
>> > index b8f5f3f..c8acfc5 100644
>> > --- a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb
>> > +++ b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
>> > @@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\
>> > python-threading \
>> >  "
>> >
>> > -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366"
>> > -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9
>> f2c4529b5689a65fde45e6f1ac36b9a261e"
>> > +SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1"
>> > +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a2
>> 1eb66f436184691d0bf1f2a85a6213c6c1f"
>> > --
>> > 2.7.4
>> >
>> > --
>> > ___
>> > Openembedded-devel mailing list
>> > openembedded-de...@lists.openembedded.org
>> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>>
>> --
>> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>>
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>
>>

> Michael: one syntax error in patchwork code was pulled into production
> yesterday. This is the cause for missing patches. The error is fixed in
> the Yocto repo now, please perform a server code update ASAP.


Leo and I pulled changes and restarted so this should be in place now.
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Patchwork not picking changes from the ML Was: [oe] [meta-python][PATCH] python-paho-mqtt: update to version 1.2

[Michael Halstead]

I've seen several issues with hooks. I was working on them yesterday and
will continue today.

These are currently managed by hand but we are moving them into
configuration management which should help keep them working consistently.

On Feb 22, 2017 12:47 PM, "Martin Jansa"  wrote:

> On Wed, Feb 22, 2017 at 12:45:36PM -0500, Derek Straka wrote:
> > Signed-off-by: Derek Straka 
>
> It's not your fault Derek, but most of the patches from today and based
> on the pings from today also some earlier patches didn't make it into
> patchwork. This one is the only exception.
>
> Michael, Jose: are you aware of some issues with patchwork? Could it be
> caused by the default Reply-to change from yesterday (or day before
> during OEDAM)?
>
> I know only about issues processing merged changes:
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10967
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=10759
>
> And also UI issue in patchwork that paging doesn't work, e.g.:
> https://patchwork.openembedded.org/bundle/jama/
> master-next/?submitterboth
> shows that there are 5 pages of changes (which should be in most cases
> marked as accepted by the hook above), but clicking on 2nd page produces
> link which drops the query parameters:
> https://patchwork.openembedded.org/bundle/jama/master-next/?page=2
> so it says "No patches to display"
>
> Regards,
>
> > ---
> >  .../python/{python-paho-mqtt_1.1.bb => python-paho-mqtt_1.2.bb}
>  | 4 ++--
> >  1 file changed, 2 insertions(+), 2 deletions(-)
> >  rename meta-python/recipes-devtools/python/{python-paho-mqtt_1.1.bb =>
> python-paho-mqtt_1.2.bb} (68%)
> >
> > diff --git a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb
> b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
> > similarity index 68%
> > rename from meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb
> > rename to meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
> > index b8f5f3f..c8acfc5 100644
> > --- a/meta-python/recipes-devtools/python/python-paho-mqtt_1.1.bb
> > +++ b/meta-python/recipes-devtools/python/python-paho-mqtt_1.2.bb
> > @@ -11,5 +11,5 @@ RDEPENDS_${PN} = "\
> > python-threading \
> >  "
> >
> > -SRC_URI[md5sum] = "a6407b74eb5e5411e157be1de5c11366"
> > -SRC_URI[sha256sum] = "0f7a629efe6e3a2c61b59d3550aa9f
> 2c4529b5689a65fde45e6f1ac36b9a261e"
> > +SRC_URI[md5sum] = "241150b3fcb920ddca4d33181f3238b1"
> > +SRC_URI[sha256sum] = "9100a6aa706ab699d414ec02705a21
> eb66f436184691d0bf1f2a85a6213c6c1f"
> > --
> > 2.7.4
> >
> > --
> > ___
> > Openembedded-devel mailing list
> > openembedded-de...@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-devel
>
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>
> --
> ___
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [oe] Patchwork upgrade tonight

[Michael Halstead]

The new patchwork is in place at https://patchwork.openembedded.org/.
The performance changes appear to be working well. Please e-mail if you
notice any problems.

On 06/30/2016 04:11 PM, Khem Raj wrote:
> On Thu, Jun 30, 2016 at 4:03 PM, Michael Halstead
> <mhalst...@linuxfoundation.org> wrote:
>> Please reach out if you have concerns.
> 
> Hi Mike
> 
> I have been playing with the new instance no issues so far. Send a
> note when you bring down the system and again another when its all up.
> 
There should have been no down time. Both systems remain running and the
cut over was done with a DNS change.

-- 
Michael Halstead
Linux Foundation / SysAdmin
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Patchwork upgrade tonight

[Michael Halstead]

After 2 weeks of testing and some performance tuning we are going to
proceed with the Patchwork upgrade. Data entered into the current
version in the next few hours may need to be re-entered after the upgrade.

All features of the current Patchwork install work in the new version.
So while there are still issues surrounding detection of patch series
there are no known regressions. Series detection can be addressed after
the upgrade.

The rollback plan can be executed very quickly if needed.

Please reach out if you have concerns.

-- 
Michael Halstead
Linux Foundation / SysAdmin
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] Patchwork users: Help test new version

[Michael Halstead]

Hello,

OpenEmbedded is nearly ready to upgrade to a new version of Patchwork.
The new version offers several new features that will allow OpenEmbedded
to improve developer workflow and automated checks on incoming patches.

If you are a Patchwork user please visit
https://patchwork-next.openembedded.org/ and take a look. If you find
anything amiss please e-mail me directly and include patchwork in the
subject line.

Thank you for your help upgrading this important system!

-- 
Michael Halstead
Linux Foundation / SysAdmin
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] oecommit ml

[Michael Halstead]

I'll get that fixed asap. Probably about 2 hours.
On Nov 16, 2015 1:52 PM, "Martin Jansa" <martin.ja...@gmail.com> wrote:

> On Fri, Nov 13, 2015 at 02:03:07PM -0800, Michael Halstead wrote:
> >
> > On 11/13/2015 01:50 PM, Khem Raj wrote:
> > >> On Nov 13, 2015, at 1:45 PM, Michael Halstead <
> mich...@yoctoproject.org> wrote:
> > >>
> > >> Bitbake is disabled with the note:
> > >>
> > >> # interferes with patchwork sice it sends emails after the patches are
> > >> closed
> > >> # we could re-enable it if the mails went to someother ml may be
> > >> bitbake-commits
> > >>
> > >> This happens because it was mailing
> bitbake-de...@lists.openembedded.org
> > >>
> > >> We can mail openembedded-comm...@lists.openembedded.org which would
> work
> > >> fine. Or I can create a bitbake-comm...@lists.openembedded.org.
> Which is
> > >> better?
> > > I think mailing to openembedded-comm...@lists.openembedded.org might
> be ok. with [bitbake] in message subject for filtering help.
> >
> > I've altered the script to include [reponame] in the subject of all
> > e-mails and enabled for bitbake.
>
> Seems to be causing some new warnings when pushing to the repo:
>
> OE @ ~/meta-openembedded $ git push origin master
> Counting objects: 204, done.
> Delta compression using up to 8 threads.
> Compressing objects: 100% (193/193), done.
> Writing objects: 100% (204/204), 38.00 KiB | 0 bytes/s, done.
> Total 204 (delta 147), reused 0 (delta 0)
> remote: Scalar found where operator expected at /home/git/git-notify line
> 140, near "$subject"
> remote: (Missing semicolon on previous line?)
> remote: Global symbol "@openembedded" requires explicit package name at
> /home/git/git-notify line 60.
> remote: syntax error at /home/git/git-notify line 140, near "$subject "
> remote: Execution of /home/git/git-notify aborted due to compilation
> errors.
> remote: E: failed to find patch for rev
> 7df2b574f1c4ad445b165878cb2ceffca2e0.
> remote: E: failed to find patch for rev
> ea5bc66444a1e9b5fb330d8a6d42dc95e4bc9500.
> remote: E: failed to find patch for rev
> 1ec69e6b3891c01734e57a908a2a675128f126eb.
> remote: E: failed to find patch for rev
> a1d3dce036f80867d30993742d55abb17c6bc057.
> ...
>
> --
> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] oecommit ml

[Michael Halstead]

On 11/13/2015 01:50 PM, Khem Raj wrote:
>> On Nov 13, 2015, at 1:45 PM, Michael Halstead <mich...@yoctoproject.org> 
>> wrote:
>>
>> Bitbake is disabled with the note:
>>
>> # interferes with patchwork sice it sends emails after the patches are
>> closed
>> # we could re-enable it if the mails went to someother ml may be
>> bitbake-commits
>>
>> This happens because it was mailing bitbake-de...@lists.openembedded.org
>>
>> We can mail openembedded-comm...@lists.openembedded.org which would work
>> fine. Or I can create a bitbake-comm...@lists.openembedded.org. Which is
>> better?
> I think mailing to openembedded-comm...@lists.openembedded.org might be ok. 
> with [bitbake] in message subject for filtering help.

I've altered the script to include [reponame] in the subject of all
e-mails and enabled for bitbake.


Michael Halstead
Yocto Project / SysAdmin


>
>> Michael Halstead
>> Yocto Project / SysAdmin
>>
>> On 11/13/2015 01:41 PM, Khem Raj wrote:
>>>> On Nov 13, 2015, at 1:39 PM, Michael Halstead <mich...@yoctoproject.org> 
>>>> wrote:
>>>>
>>>> It seems git-notify was sending mail as "c...@cia.navi.cx" and that was
>>>> causing the mail server to get added to blacklists so it was disabled.
>>>> I've changed the script and re-enabled it for:
>>>>
>>>> openembedded-core
>>>> meta-openembedded
>>>> OpenEmbedded (but I don't know if we need it)
>>> bitbake too plz.
>>>
>>>> Michael Halstead
>>>> Yocto Project / SysAdmin
>>>>
>>>> On 11/13/2015 12:47 PM, Khem Raj wrote:
>>>>>> On Nov 13, 2015, at 3:59 AM, Martin Jansa <martin.ja...@gmail.com> wrote:
>>>>>>
>>>>>> On Thu, Nov 12, 2015 at 06:14:14PM -0500, Trevor Woerner wrote:
>>>>>>> It seems I missed some announcement. At first I thought I had been
>>>>>>> unsubscribed from the openembedded-commits mailing list (since I haven't
>>>>>>> received any emails on that list since about the end of September). So I
>>>>>>> looked up http://lists.openembedded.org/pipermail/openembedded-commits/
>>>>>>> and it seems to have gone quiet about that time too.
>>>>>> I've already asked Paul and Michael few times on IRC in last few weeks.
>>>>>>
>>>>>> I haven't received any reply from Michael, adding him to To, now.
>>>>> I see that git-notify hooks have been disabled explicitly for all repos 
>>>>> in update.secondary file. thats why the messages are not being
>>>>> sent. We can enable them but I would like to know the reason they were 
>>>>> disabled in first place. Since we do not have this under some
>>>>> sort of revision history, I can not find information for them as well. So 
>>>>> we need this info before we enable them back.
>>>>>
>>>>>>> I liked being able to watch the commits to see what was going in, and to
>>>>>>> check if my patches were added (before sending "ping"s, without having
>>>>>>> to "git pull" and search). Is there a new workflow for seeing what's
>>>>>>> going in?
>>>>>> Yes, I find them useful too (e.g. to report issue with commit which was
>>>>>> recently merged) or in general to know that it's worth doing "git pull".
>>>>>>
>>>>>> --
>>>>>> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>>>>>> --
>>>>>> ___
>>>>>> Openembedded-core mailing list
>>>>>> Openembedded-core@lists.openembedded.org
>>>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>




signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] oecommit ml

[Michael Halstead]

It seems git-notify was sending mail as "c...@cia.navi.cx" and that was
causing the mail server to get added to blacklists so it was disabled.
I've changed the script and re-enabled it for:

openembedded-core
meta-openembedded
OpenEmbedded (but I don't know if we need it)

Michael Halstead
Yocto Project / SysAdmin

On 11/13/2015 12:47 PM, Khem Raj wrote:
>> On Nov 13, 2015, at 3:59 AM, Martin Jansa <martin.ja...@gmail.com> wrote:
>>
>> On Thu, Nov 12, 2015 at 06:14:14PM -0500, Trevor Woerner wrote:
>>> It seems I missed some announcement. At first I thought I had been
>>> unsubscribed from the openembedded-commits mailing list (since I haven't
>>> received any emails on that list since about the end of September). So I
>>> looked up http://lists.openembedded.org/pipermail/openembedded-commits/
>>> and it seems to have gone quiet about that time too.
>> I've already asked Paul and Michael few times on IRC in last few weeks.
>>
>> I haven't received any reply from Michael, adding him to To, now.
>
> I see that git-notify hooks have been disabled explicitly for all repos in 
> update.secondary file. thats why the messages are not being
> sent. We can enable them but I would like to know the reason they were 
> disabled in first place. Since we do not have this under some
> sort of revision history, I can not find information for them as well. So we 
> need this info before we enable them back.
>
>>> I liked being able to watch the commits to see what was going in, and to
>>> check if my patches were added (before sending "ping"s, without having
>>> to "git pull" and search). Is there a new workflow for seeing what's
>>> going in?
>> Yes, I find them useful too (e.g. to report issue with commit which was
>> recently merged) or in general to know that it's worth doing "git pull".
>>
>> --
>> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>> --
>> ___
>> Openembedded-core mailing list
>> Openembedded-core@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/openembedded-core


-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] oecommit ml

[Michael Halstead]

Bitbake is disabled with the note:

# interferes with patchwork sice it sends emails after the patches are
closed
# we could re-enable it if the mails went to someother ml may be
bitbake-commits

This happens because it was mailing bitbake-de...@lists.openembedded.org

We can mail openembedded-comm...@lists.openembedded.org which would work
fine. Or I can create a bitbake-comm...@lists.openembedded.org. Which is
better?

Michael Halstead
Yocto Project / SysAdmin

On 11/13/2015 01:41 PM, Khem Raj wrote:
>> On Nov 13, 2015, at 1:39 PM, Michael Halstead <mich...@yoctoproject.org> 
>> wrote:
>>
>> It seems git-notify was sending mail as "c...@cia.navi.cx" and that was
>> causing the mail server to get added to blacklists so it was disabled.
>> I've changed the script and re-enabled it for:
>>
>> openembedded-core
>> meta-openembedded
>> OpenEmbedded (but I don't know if we need it)
> bitbake too plz.
>
>> Michael Halstead
>> Yocto Project / SysAdmin
>>
>> On 11/13/2015 12:47 PM, Khem Raj wrote:
>>>> On Nov 13, 2015, at 3:59 AM, Martin Jansa <martin.ja...@gmail.com> wrote:
>>>>
>>>> On Thu, Nov 12, 2015 at 06:14:14PM -0500, Trevor Woerner wrote:
>>>>> It seems I missed some announcement. At first I thought I had been
>>>>> unsubscribed from the openembedded-commits mailing list (since I haven't
>>>>> received any emails on that list since about the end of September). So I
>>>>> looked up http://lists.openembedded.org/pipermail/openembedded-commits/
>>>>> and it seems to have gone quiet about that time too.
>>>> I've already asked Paul and Michael few times on IRC in last few weeks.
>>>>
>>>> I haven't received any reply from Michael, adding him to To, now.
>>> I see that git-notify hooks have been disabled explicitly for all repos in 
>>> update.secondary file. thats why the messages are not being
>>> sent. We can enable them but I would like to know the reason they were 
>>> disabled in first place. Since we do not have this under some
>>> sort of revision history, I can not find information for them as well. So 
>>> we need this info before we enable them back.
>>>
>>>>> I liked being able to watch the commits to see what was going in, and to
>>>>> check if my patches were added (before sending "ping"s, without having
>>>>> to "git pull" and search). Is there a new workflow for seeing what's
>>>>> going in?
>>>> Yes, I find them useful too (e.g. to report issue with commit which was
>>>> recently merged) or in general to know that it's worth doing "git pull".
>>>>
>>>> --
>>>> Martin 'JaMa' Jansa jabber: martin.ja...@gmail.com
>>>> --
>>>> ___
>>>> Openembedded-core mailing list
>>>> Openembedded-core@lists.openembedded.org
>>>> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>




signature.asc
Description: OpenPGP digital signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] layers.openembedded.org data lost between June 26th 08:30 UTC - June 27th 17:15 UTC

[Michael Halstead]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

While restoring data for another project the
http://layers.openembedded.org database was reverted to a previous
state. Any data entered between June 26th 08:30 UTC and June 27th
17:15 UTC was lost. If you submitted a layer during the last few days
you may need to re-submit it. Please check that your layer is present.

Thank you,

- -- 
Michael Halstead
Yocto Project / SysAdmin
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJTsEAGAAoJEH9hAclg9EfIXDIIAKAFhNN55PKLNWKiyySU5Vnl
coAUtLLzQXig12C7dpSVymq4j0COElnz4e/qsCO/RDKk1dnoja3qO9Q6V8oUByHV
tlvJ7g+X3Xl8RszBV4Q6Ad9K7WXUKMjiVeTfzk7sj9q8OiVJKmtzu0gIp16qpCW8
qR2KwNLfBO+bTWs5zdZ8Z2eYi4Fkgfaw67l/01ED+RocDRCQHdqWkgdRJNhgqo7w
ZTzam3fJOtlRzzJFuhN6h6Mu/GJbpFGOrJJ0CxcX1VMBMr02XjlEjz6AXOaWHRyK
M2y7KkBfOMkreqFrjAMy6hz44IEEwKPRcwLaBzEqs20JQ+yxtamLtfHSDcSyWCM=
=N9le
-END PGP SIGNATURE-
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] Fetch/Unpack performance dependent on git version

[Michael Halstead]

On 04/19/2014 03:40 PM, Richard Purdie wrote:
 I thought it might be worth highlighting to people that the performance
 of the git fetcher *and* the unpack process is highly dependant on the
 version of git.

 Firstly, all versions of git 1.6+ appear to default to injecting an
 fsync() after fetching objects. fsync() usage significantly hurts our
 builds. It is also a bit pointless in our usecase, we can however
 disable it with a simple tweak to the fetcher:

 -ud.basecmd = data.getVar(FETCHCMD_git, d, True) or git
 +ud.basecmd = data.getVar(FETCHCMD_git, d, True) or git -c 
 core.fsyncobjectfiles=0

 Secondly, for older versions of git, git clone is running repository
 coverage checks even for local cloning. E.g.:

 git version 1.8.3.2 on my system:

 $ bitbake linux-yocto -c fetch
 $ time bitbake linux-yocto -c unpack
 51.33user 1.93system 1:09.27elapsed 76%CPU (0avgtext+0avgdata 
 779380maxresident)k

 after updating to git 1.9.2:

 $ bitbake linux-yocto -c fetch
 $ time bitbake linux-yocto -c unpack
 4.28user 0.63system 0:04.36elapsed 112%CPU (0avgtext+0avgdata 
 260692maxresident)k

 so 16 times faster!

 The commit in question for anyone interested:

 https://github.com/git/git/commit/125a05fd0b45416558923b753f6418c24208d443

 Michael/Beth: Can we please upgrade the autobuilder to a daisy release
 buildtools tarball which has git 1.9.x in it? This should massively
 speed up certain parts of the autobuilder.
The new buildtools are installed at /opt/poky/1.6 and I've updated
~pokybuild/.bashrc to source them. Restarting all the buildslaves should
put them to use. I'll restart all of them that aren't building
currently. opensuse131-a.yp, on the current nightly, is the only one
occupied at the moment.

Michael Halstead
Yocto Project / System Administrator



 Stefan: Could you see which version of git is on the performance
 benchmark machine? A run with the daisy build tools tarball would be
 extremely interesting if its before 1.9.

 Cheers,

 Richard







smime.p7s
Description: S/MIME Cryptographic Signature
-- 
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] openembedded-core@lists.openembedded.org moved to new hardware

[Michael Halstead]

openembedded-core@lists.openembedded.org and the other OE lists are now
on new hardware at the OSL in Corvallis Oregon USA. The move has just
completed and I am monitoring for trouble. I expect there will be a few
early issues to work out. Please e-mail me directly or find halstead in
IRC on Freenode.net if you discover an issue.

-- 
Michael Halstead
Yocto Project / System Administrator




smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

[OE-core] OpenEmbedded lists moved to new hardware

[Michael Halstead]

This mailing list has been moved from linuxtogo.org to new hardware at
the OSL in Corvallis Oregon USA. The move has just completed and I am
monitoring for trouble. I expect there will be a few early issues to
work out. Please e-mail me directly or find halstead in IRC on
Freenode.net if you discover an issue.

If you have an @openembedded.org e-mail address please pay extra
attention to it this week.

-- 
Michael Halstead
Yocto Project / System Administrator




smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Re: [OE-core] [denzil] qt 4.8.0 is not available from source anymore

[Michael Halstead]

On 02/11/2013 06:57 AM, Andrei Gherzan wrote:



 On Mon, Feb 11, 2013 at 4:43 PM, Paul Eggleton
 paul.eggle...@linux.intel.com mailto:paul.eggle...@linux.intel.com
 wrote:

 On Monday 11 February 2013 16:01:10 Andrei Gherzan wrote:
  On Mon, Feb 11, 2013 at 3:10 PM, Sarbu, Florin-Ionut (Florin) 
  florin.sa...@windriver.com mailto:florin.sa...@windriver.com
 wrote:
   On Monday, February 11, 2013 02:51 AM Andrei Gherzan wrote:
   
In denzil SRC_URI for qt4.8.0 uses:
   
 http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-${PV}.tar.g
 
 http://get.qt.nokia.com/qt/source/qt-everywhere-opensource-src-$%7BPV%7D.tar.g
z
   
 This source seems to be outdated and replaced by:
http://releases.qt-project.org/qt4/source/
   
 The problem is that the new location doesn't include the
 4.8.0 release.
 qt-everywhere-opensource-src-4.6.4.tar.gz
 qt-everywhere-opensource-src-4.8.1.tar.gz
 qt-everywhere-opensource-src-4.8.2.tar.gz
 qt-everywhere-opensource-src-4.8.3.tar.gz
 qt-everywhere-opensource-src-4.8.4.tar.gz
   
 So right now qt4 in denzil is not fetch-able anymore.
  
Use git
 
  We are not talking about switching of sources. I want to know
 why 4.8.0 is
  not on yocto mirror.

 It should be there, not sure why it isn't.

 Michael, could you please upload qt 4.8.0 and anything else
 downloaded by
 bitbake -c fetchall world for the denzil-7.0.2 release into the
 mirror?

I ran fetchall world and poky 7.0.2 uses
qt-everywhere-opensource-src-4.7.4.tar.gz which was already present at
http://downloads.yoctoproject.org/mirror/sources/. Every file downloaded
was already present on the mirror.

I downloaded qt-everywhere-opensource-src-4.8.0.tar.gz from a Fedora
Project mirror and added it to
http://downloads.yoctoproject.org/mirror/sources/ so we'd have it.

Michael Halstead
Yocto Project / System Administrator




 Thank you.

 -- 
 *Andrei Gherzan*
 m: +40.744.478.414 |  f: +40.31.816.28.12



smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] WebHob Mailing List Setup

[Michael Halstead]

On 01/09/2013 08:31 AM, Philip Balister wrote:
 On 01/09/2013 10:22 AM, Richard Purdie wrote:
 Various people at various times have expressed an interest in webhob
 which will be a web interface to bitbake's functionality as an evolution
 of the capabilities of the current hob UI. There are some people looking
 at the design of it and who are actively working on figuring out what it
 should look like, what it needs to do, who it needs to serve and some
 other key questions. They will also likely start implementing the
 functionality soon.

 In the interests of collaboration, we've setup the mailing list:

 https://lists.yoctoproject.org/listinfo/webhob
 Is there a gmane archive?

 Philip
Not yet but soon. Gmane archives usually take three to five days to set up.


Michael Halstead
Yocto Project / Sys Admin



 which is where the design and initial implementation discussions are
 going to happen. If you are interested please join the list.

 I've cross posted this to ensure people know about it. Please take
 discussion and replies up on the webhob list itself.

 Cheers,

 Richard


 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] Download of bitbake doesn't work properly

[Michael Halstead]

On 12/12/2012 06:40 AM, Paul Eggleton wrote:
 On Wednesday 12 December 2012 15:17:05 Giuseppe Condorelli wrote:
 Hi, just to highlight that I'm unable to download the bitbake tar files.
 It seems that cgit.openembedded.org suffers of some problem in that case.

 Please can you verify?
 Yep, I also get a 503 error whenever I try these, for example:
 http://cgit.openembedded.org/bitbake/snapshot/bitbake-1.17.0.tar.gz

 Tom/Michael, would you mind looking into this?
I disabled tarball downloads with a temporary code in order to keep the
site online. The number of download requests was causing all pages to
timeout.

I'll put these back online and monitor to make sure the situation has
improved.


Michael Halstead
Yocto Project / Sys Admin



 Thanks,
 Paul





smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] meta-cloud layer

[Michael Halstead]

On 12/03/2012 08:00 AM, Saul Wold wrote:
 On 12/03/2012 07:20 AM, Prica, Mihai wrote:
 -Original Message-
 From: openembedded-core-boun...@lists.openembedded.org
 [mailto:openembedded-core-boun...@lists.openembedded.org] On Behalf
 Of David Nyström
 Sent: Saturday, December 01, 2012 10:44 PM
 To: Michael Halstead
 Cc: oe-core layer
 Subject: Re: [OE-core] meta-cloud layer

 On 12/01/2012 12:23 AM, Michael Halstead wrote:
 On 11/30/2012 12:17 PM, Raymond Danks wrote:
 On 11/30/2012 11:03 AM, Michael Halstead wrote:
 On 11/30/2012 09:26 AM, Bruce Ashfield wrote:



 On Fri, Nov 30, 2012 at 12:15 PM, Saul Wold s...@linux.intel.com
 mailto:s...@linux.intel.com wrote:

   On 11/30/2012 03:29 AM, David Nyström wrote:

   On 11/29/2012 02:54 PM, Richard Purdie wrote:

   On Thu, 2012-11-29 at 06:44 -0700, Raymond Danks
 wrote:

   Thanks for looping me in here David. The initial
   goal for the meta-xen
   layer was in fact to encompass Xen Cloud Platform.
As such, the intent
   was to contain both hypervisor and user-space
   applications.  Indeed, the
   xen distribution itself includes xm/libxl;
   hypervisor abstraction would
   be somewhat tedious in my opinion.

   The layer just received commits for expanding the
   libvirt build to
   support qemu.  The commonalities and shared
 packaged
   between xen, qemu,
   and kvm implementations are such that I would also
   agree that meta-xen
   should be expanded/renamed to encompass all
   virtualization types; I also
   support the move to meta-virtualization.


   meta-virtualization sounds good, let co-op on this so we
   don't duplicate
   work.

   If everyone is OK with this, I will have Michael Halstead
 create
   a repo, please send him your keys so that you will have write
   access to it.


 This works for me. If Michael already has our keys, do we need to
 resend or can a local copy happen ?
 I already have keys for,

 David Nystrom df:2d:b1:59:f3:d7:73:fc:59:36:7b:cf:85:28:a7:50
 Bruce Ashfield  4f:93:90:b2:c7:a1:45:21:f2:47:31:6f:60:f9:60:02

 Either of you can currently add
 g...@git.yoctoproject.org:meta-virtualization as a git remote and
 start the repository. Once we have initial code and the maintainers
 and patch submission guidelines in the readme I can publicly list the
 new repository.

 I require an ssh public key for Raymond Danks.
 Thanks Michael.  I got your response and was able to push meta-xen to
 the newly created repository on meta-virtualization.  I added one
 commit to tweak the README and conf/layer.conf for the new name.


 We also need a short description for the listing on
 git.yoctoproject.org. I could be something similar to, but better
 than, Layer enabling virtualization support. 
 How about Layer enabling hypervisor, virtualization tool stack, and
 cloud support.

 Sounds good to me. Thank you.
 Also - I referenced the mail alias meta-virtualization at yoctoproject
 in the README.  When you publish this, can we use something like that
 as well?

 I can add a private list for meta-virtualizat...@yoctoproject.org. Who
 shall I add to membership?


 I would like to be added, since it seems I can't add myself at
 https://lists.yoctoproject.org/listinfo

 Best Regards,
 David

 I would like to be added as well to the private list.

 Just to be clear to all this is not a private list, there was some
 issue I think with getting it initialized, it is visiable and
 available to all from the https://lists.yoctoproject.org/listinfo URL,
 and it is getting added to the main list of Mailing lists today.

 Sorry for any confusion.

 Sau!

This was a misunderstanding on my part. I thought this was a simple mail
alias for the maintainers. A full list has been set up and can be seen
at https://lists.yoctoproject.org/ or
https://lists.yoctoproject.org/listinfo. Anyone can subscribe. I'm also
working on getting this list added to Gmane for fans for NNTP.


-- 
Michael Halstead
Yocto Project / Sys Admin



 Thanks,
 Mihai


 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

 ___
 Openembedded-core mailing list
 Openembedded-core@lists.openembedded.org
 http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core








smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] meta-cloud layer

[Michael Halstead]

On 11/30/2012 09:26 AM, Bruce Ashfield wrote:



 On Fri, Nov 30, 2012 at 12:15 PM, Saul Wold s...@linux.intel.com
 mailto:s...@linux.intel.com wrote:

 On 11/30/2012 03:29 AM, David Nyström wrote:

 On 11/29/2012 02:54 PM, Richard Purdie wrote:

 On Thu, 2012-11-29 at 06:44 -0700, Raymond Danks wrote:

 Thanks for looping me in here David. The initial goal
 for the meta-xen
 layer was in fact to encompass Xen Cloud Platform.  As
 such, the intent
 was to contain both hypervisor and user-space
 applications.  Indeed, the
 xen distribution itself includes xm/libxl; hypervisor
 abstraction would
 be somewhat tedious in my opinion.

 The layer just received commits for expanding the
 libvirt build to
 support qemu.  The commonalities and shared packaged
 between xen, qemu,
 and kvm implementations are such that I would also
 agree that meta-xen
 should be expanded/renamed to encompass all
 virtualization types; I also
 support the move to meta-virtualization.


 meta-virtualization sounds good, let co-op on this so we don't
 duplicate
 work.

 If everyone is OK with this, I will have Michael Halstead create a
 repo, please send him your keys so that you will have write access
 to it.


 This works for me. If Michael already has our keys, do we need to
 resend or can
 a local copy happen ?
I already have keys for,

David Nystrom df:2d:b1:59:f3:d7:73:fc:59:36:7b:cf:85:28:a7:50
Bruce Ashfield  4f:93:90:b2:c7:a1:45:21:f2:47:31:6f:60:f9:60:02

Either of you can currently add
g...@git.yoctoproject.org:meta-virtualization as a git remote and start
the repository. Once we have initial code and the maintainers and patch
submission guidelines in the readme I can publicly list the new repository.

I require an ssh public key for Raymond Danks.


We also need a short description for the listing on
git.yoctoproject.org. I could be something similar to, but better than,
Layer enabling virtualization support. 

-- 
Michael Halstead
Yocto Project / Sys Admin



 Cheers,

 Bruce
  


 Sau!


 As far as a meta-cloud layer is concerned, I'm not
 sure I am
 knowledgeable enough in this area to weigh in.  I'm
 currently
 researching a filesystem implementation for OpenStack
 and have stumbled
 across Ceph/RBD and Gluster modules that look
 promising. On top of this,
 XCP is documented to include support for VastSky and
 can be integrated
 with DRBD.  And, the storage and hypervisor are only
 two pieces of the
 puzzle for a cloud implementation!


 Cool !
 I know, the meta-cloud name is quite/too ambitious, it was
 not meant
 to be a one week effort. But why aim low :).

 I think I would encourage you to also include
 OpenStack in a
 meta-virtualization layer until it has matured to the
 point where
 abstraction is more warranted.


 Agree.

 Since you've already created a presence
 at github, would it be possible to rename your layer to
 meta-virtualization and absorb the entire meta-xen
 layer?  I can push
 any changes for Xen/XCP here, it sounds like it is a
 central place for
 libvirt and could also contain Bruce's kernel
 modifications.

 Alternatively, I can create a meta-virtualization
 project.  In any case,
 those on the To and CC list should receive access to
 this layer as a
 starting point.

 Just my two cents.  :)


 I'd like to offer to host this combined layer (whatever we
 decide to
 call it) on git.yoctoproject.org
 http://git.yoctoproject.org if that would help people
 and people
 are interested. My only concern is in the area of
 maintainership, we
 need to clearly define who maintains what and what the
 patch submission
 process is in the README.


 Thanks,

 Sounds good to centralize everything, since Raymond is the
 majority code
 contributor, perhaps he, if willing, can maintain the
 meta-virtualization layer.
 If you want a co/sub-maintainer I'll be happy to help out.


 Cheers,

 Richard

Re: [OE-core] meta-cloud layer

[Michael Halstead]

On 11/30/2012 12:17 PM, Raymond Danks wrote:
 On 11/30/2012 11:03 AM, Michael Halstead wrote:
 On 11/30/2012 09:26 AM, Bruce Ashfield wrote:



 On Fri, Nov 30, 2012 at 12:15 PM, Saul Wold s...@linux.intel.com
 mailto:s...@linux.intel.com wrote:

 On 11/30/2012 03:29 AM, David Nyström wrote:

 On 11/29/2012 02:54 PM, Richard Purdie wrote:

 On Thu, 2012-11-29 at 06:44 -0700, Raymond Danks wrote:

 Thanks for looping me in here David. The initial
 goal for the meta-xen
 layer was in fact to encompass Xen Cloud Platform.
  As such, the intent
 was to contain both hypervisor and user-space
 applications.  Indeed, the
 xen distribution itself includes xm/libxl;
 hypervisor abstraction would
 be somewhat tedious in my opinion.

 The layer just received commits for expanding the
 libvirt build to
 support qemu.  The commonalities and shared packaged
 between xen, qemu,
 and kvm implementations are such that I would also
 agree that meta-xen
 should be expanded/renamed to encompass all
 virtualization types; I also
 support the move to meta-virtualization.


 meta-virtualization sounds good, let co-op on this so we
 don't duplicate
 work.

 If everyone is OK with this, I will have Michael Halstead create
 a repo, please send him your keys so that you will have write
 access to it.


 This works for me. If Michael already has our keys, do we need to
 resend or can
 a local copy happen ?
 I already have keys for,

 David Nystrom df:2d:b1:59:f3:d7:73:fc:59:36:7b:cf:85:28:a7:50
 Bruce Ashfield  4f:93:90:b2:c7:a1:45:21:f2:47:31:6f:60:f9:60:02

 Either of you can currently add
 g...@git.yoctoproject.org:meta-virtualization as a git remote and
 start the repository. Once we have initial code and the maintainers
 and patch submission guidelines in the readme I can publicly list the
 new repository.

 I require an ssh public key for Raymond Danks.
 Thanks Michael.  I got your response and was able to push meta-xen to
 the newly created repository on meta-virtualization.  I added one
 commit to tweak the README and conf/layer.conf for the new name.


 We also need a short description for the listing on
 git.yoctoproject.org. I could be something similar to, but better
 than, Layer enabling virtualization support. 
 How about Layer enabling hypervisor, virtualization tool stack, and
 cloud support.

Sounds good to me. Thank you.
 Also - I referenced the mail alias meta-virtualization at yoctoproject
 in the README.  When you publish this, can we use something like that
 as well?

I can add a private list for meta-virtualizat...@yoctoproject.org. Who
shall I add to membership?


-- 
Michael Halstead
Yocto Project / Sys Admin



 Thanks again,
 Ray

 -- 
 Michael Halstead
 Yocto Project / Sys Admin


 Cheers,

 Bruce
  


 Sau!


 As far as a meta-cloud layer is concerned, I'm not
 sure I am
 knowledgeable enough in this area to weigh in.  I'm
 currently
 researching a filesystem implementation for
 OpenStack and have stumbled
 across Ceph/RBD and Gluster modules that look
 promising. On top of this,
 XCP is documented to include support for VastSky and
 can be integrated
 with DRBD.  And, the storage and hypervisor are only
 two pieces of the
 puzzle for a cloud implementation!


 Cool !
 I know, the meta-cloud name is quite/too ambitious, it was
 not meant
 to be a one week effort. But why aim low :).

 I think I would encourage you to also include
 OpenStack in a
 meta-virtualization layer until it has matured to
 the point where
 abstraction is more warranted.


 Agree.

 Since you've already created a presence
 at github, would it be possible to rename your layer to
 meta-virtualization and absorb the entire meta-xen
 layer?  I can push
 any changes for Xen/XCP here, it sounds like it is a
 central place for
 libvirt and could also contain Bruce's kernel
 modifications.

 Alternatively, I can create a meta-virtualization
 project.  In any case,
 those on the To and CC list should receive access to
 this layer as a
 starting point.

 Just my two cents.  :)


 I'd like to offer to host this combined layer (whatever

Re: [OE-core] [PATCH] bash: Add fix for cross compile issues

[Michael Halstead]

On 11/14/2012 05:30 AM, Richard Purdie wrote:
 On Wed, 2012-11-14 at 13:24 +, Richard Purdie wrote:
 On Wed, 2012-11-14 at 13:30 +0100, Martin Jansa wrote:
 On Tue, Nov 13, 2012 at 01:59:19PM +, Richard Purdie wrote:
 Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
 ---
 diff --git a/meta/recipes-extended/bash/bash-4.2/crossfix.patch 
 b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 new file mode 100644
 index 000..f587c34
 --- a/dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 @@ -0,0 +1,28 @@
 Are you using some special tool to generate git patches or some weird
 git version?
 Basically, the data from cgit in the web interface is broken and that is
 causing this.

 Patches from you where you add some file usually does not apply here,
 It's caused by:
 --- a/dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 which usually looks like
 --- /dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 Right, there is a bug in cgit. I'm not sure if anyone fancies trying to
 find/fix it?
 Actually, its not hard to find:

 http://hjemli.net/git/cgit/tree/ui-patch.c


 In header(), the:
   htmlf(\n--- a/%s\n, path1);
   htmlf(+++ b/%s\n, path2);
 needs to be conditional on is_null_sha1(sha1)/is_null_sha1(sha2) with
 the alternative of:
   htmlf(\n--- /%s\n, path1);
   htmlf(+++ /%s\n, path2);
 which there are a variety of ways to achieve...

 Michael: Fancy fixing that on the server and sending a patch
 upstream? :)

 Cheers,

 Richard

I'm happy to. I've fixed the code you've tracked down and recompiled for
git.yoctoproject.org. You can see the result at
https://git.yoctoproject.org/cgit/cgit.cgi/poky/patch/?id=ed234aca98d0867c7b32801fc63820b19cf67df9
but I am still working on fixing the shared UI for this view
https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ed234aca98d0867c7b32801fc63820b19cf67df9.


Once I have both fixes I'll upgrade http://cgit.openembedded.org/ with
the new version and submit my patch upstream.

-- 
Michael Halstead
Yocto Project / Sys Admin





smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] [PATCH] bash: Add fix for cross compile issues

[Michael Halstead]

On 11/14/2012 11:45 AM, Michael Halstead wrote:
 On 11/14/2012 05:30 AM, Richard Purdie wrote:
 On Wed, 2012-11-14 at 13:24 +, Richard Purdie wrote:
 On Wed, 2012-11-14 at 13:30 +0100, Martin Jansa wrote:
 On Tue, Nov 13, 2012 at 01:59:19PM +, Richard Purdie wrote:
 Signed-off-by: Richard Purdie richard.pur...@linuxfoundation.org
 ---
 diff --git a/meta/recipes-extended/bash/bash-4.2/crossfix.patch 
 b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 new file mode 100644
 index 000..f587c34
 --- a/dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 @@ -0,0 +1,28 @@
 Are you using some special tool to generate git patches or some weird
 git version?
 Basically, the data from cgit in the web interface is broken and that is
 causing this.

 Patches from you where you add some file usually does not apply here,
 It's caused by:
 --- a/dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 which usually looks like
 --- /dev/null
 +++ b/meta/recipes-extended/bash/bash-4.2/crossfix.patch
 Right, there is a bug in cgit. I'm not sure if anyone fancies trying to
 find/fix it?
 Actually, its not hard to find:

 http://hjemli.net/git/cgit/tree/ui-patch.c


 In header(), the:
  htmlf(\n--- a/%s\n, path1);
  htmlf(+++ b/%s\n, path2);
 needs to be conditional on is_null_sha1(sha1)/is_null_sha1(sha2) with
 the alternative of:
  htmlf(\n--- /%s\n, path1);
  htmlf(+++ /%s\n, path2);
 which there are a variety of ways to achieve...

 Michael: Fancy fixing that on the server and sending a patch
 upstream? :)

 Cheers,

 Richard

 I'm happy to. I've fixed the code you've tracked down and recompiled for
 git.yoctoproject.org. You can see the result at
 https://git.yoctoproject.org/cgit/cgit.cgi/poky/patch/?id=ed234aca98d0867c7b32801fc63820b19cf67df9
 but I am still working on fixing the shared UI for this view
 https://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=ed234aca98d0867c7b32801fc63820b19cf67df9.


 Once I have both fixes I'll upgrade http://cgit.openembedded.org/ with
 the new version and submit my patch upstream.

I've submitted the patch upstream and installed a fixed copy of cgit on
cgit.openembedded.org. Please let me know if any errors in the
formatting remain.

Michael Halstead
Yocto Project / Sys Admin




smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] Best way to update gnu-config?

[Michael Halstead]

On 10/03/2012 07:51 AM, Marcin Juszkiewicz wrote:
 W dniu 18.09.2012 11:36, Richard Purdie pisze:
 On Tue, 2012-09-18 at 11:29 +0200, Marcin Juszkiewicz wrote:
 W dniu 18.09.2012 11:08, Richard Purdie pisze:

 The trouble was that upstream was in cvs. It was the only reason we
 still had a dependency on cvs and we decided we wanted to kill it
 which
 isn't something I regret.

 There is git mirror hosted on gnu.org servers which can be used instead
 of cvs. OE-Core already has git-native.

 I remember the problem now, this was a circular dependency nightmare
 (git-native depends on gnu-config-native and vice versa).

 Can you share a tarball of the updated (unpatched) upstream version
 and
 we'll put it into place alongside the other tarball on the server.

 http://people.linaro.org/~hrw/aarch64/gnu-config-20120814.tar.bz2

 11:29 hrw@puchatek$ sha256sum gnu-config-20120814.tar.bz2
 44f99a8e76f3e8e4fec0bb5ad4762f8e44366168554ce66cb85afbe2ed3efd8b
 gnu-config-20120814.tar.bz2

 Michael (cc'd) should be able to do this. Once that is done you should
 be able to send a patch as usual to update to the new version.

 Ok.

 Thanks, Michael should be able to take care of this later today (he's US
 based).

 Michael: any update on it?

I'm sorry this is a case of bad e-mail filtering.

I've added this tarball at
http://downloads.yoctoproject.org/releases/gnu-config/ is that correct?

Michael Halstead
Yocto Project / Sys Admin





smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core

Re: [OE-core] libmatchbox fetch error

[Michael Halstead]

On 07/08/2011 02:52 PM, Richard Purdie wrote:

On Fri, 2011-07-08 at 16:16 -0400, Cliff Brake wrote:

I'm trying to get some basic oe-core builds going (core-image-sato)
and am running into:

ERROR: Logfile of failure stored in:
/scratch/oe/openembedded-core/build/tmp-eglibc/work/i586-oe-linux/libmatchbox-1.9-r8/temp/log.do_fetch.24235
Log data follows:
| NOTE: fetch 
http://projects.o-hand.com/matchbox/sources/libmatchbox/1.9/libmatchbox-1.9.tar.gz
| ERROR: Function 'Fetcher failure for URL:
'http://projects.o-hand.com/matchbox/sources/libmatchbox/1.9/libmatchbox-1.9.tar.gz'.
Unable to fetch URL
http://projects.o-hand.com/matchbox/sources/libmatchbox/1.9/libmatchbox-1.9.tar.gz
from any source.' failed
NOTE: package libmatchbox-1.9-r8: task do_fetch: Failed
ERROR: Task 1884
(/scratch/oe/openembedded-core/meta/recipes-graphics/libmatchbox/libmatchbox_1.9.bb,
do_fetch) failed with exit code '1'

It seems like the matchbox site is in flux right now.  Is there a
stable place to get the download?

At the very least the yocto mirrors have those pieces on them. I don't
know what has happened to those urls but I'll try and find out.

Cheers,

Richard

Those files were moved when we converted the matchbox-project site from 
Wordpress to static HTML for security reasons. The files have been 
restored. Thank you for bringing this to my attention.


Michael Halstead




smime.p7s
Description: S/MIME Cryptographic Signature
___
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core