Date   

[meta-security][PATCH 2/2] ecryptfs-utils: search nspr header files in ${STAGING_INCDIR}/nspr directory

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
index e45ee0b..d8cd06f 100644
--- a/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
+++ b/recipes-security/ecryptfs-utils/ecryptfs-utils_111.bb
@@ -41,7 +41,7 @@ PACKAGECONFIG[nss] = "--enable-nss,--disable-nss,nss,"
PACKAGECONFIG[pam] = "--enable-pam,--disable-pam,libpam,"

do_configure_prepend() {
- export NSS_CFLAGS="-I${STAGING_INCDIR}/nspr4 -I${STAGING_INCDIR}/nss3"
+ export NSS_CFLAGS="-I${STAGING_INCDIR}/nspr -I${STAGING_INCDIR}/nss3"
export NSS_LIBS="-L${STAGING_BASELIBDIR} -lssl3 -lsmime3 -lnss3 -lsoftokn3 -lnssutil3"
export KEYUTILS_CFLAGS="-I${STAGING_INCDIR}"
export KEYUTILS_LIBS="-L${STAGING_LIBDIR} -lkeyutils"
--
2.17.1


[meta-security][PATCH 1/2] swtpm: fix configure error

Armin Kuster
 

checking for whether to build with seccomp profile... configure: error: "Is libseccomp-devel installed? -- could not get cflags for libseccomp"

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb | 1 +
1 file changed, 1 insertion(+)

diff --git a/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb b/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
index f3a53dd..35c77c8 100644
--- a/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
+++ b/meta-tpm/recipes-tpm/swtpm/swtpm_0.2.0.bb
@@ -31,6 +31,7 @@ PACKAGECONFIG[openssl] = "--with-openssl, --without-openssl, openssl"
PACKAGECONFIG[gnutls] = "--with-gnutls, --without-gnutls, gnutls"
PACKAGECONFIG[selinux] = "--with-selinux, --without-selinux, libselinux"
PACKAGECONFIG[cuse] = "--with-cuse, --without-cuse, fuse"
+PACKAGECONFIG[seccomp] = "--with-seccomp, --without-seccomp, libseccomp"

EXTRA_OECONF += "--with-tss-user=${TSS_USER} --with-tss-group=${TSS_GROUP}"

--
2.17.1


Re: Yocto Project Status WW04'20

Ross Burton
 

On Sun, 2 Feb 2020 at 13:35, Adrian Bunk <bunk@stusta.de> wrote:
Would it be possible to also create a yocto-devel or yocto-core
mailing list for discussing development of Yocto?
What would it cover that isn't already covered in other lists?

Ross


Re: Yocto Project Status WW04'20

Alexander Kanavin
 

Why separate them? I’d rather have newbies and experts in the same room.

Alex

On 2 Feb 2020, at 14.28, Adrian Bunk <bunk@stusta.de> wrote:

On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
...
* We have created a "documentation" list and a "licensing" list on the
yocto project mailing list infrastructure. We believe these topics would
benefit from dedicated discussions, the people involved usually aren't
interested in bulk email as would be found on other lists. The new lists can
be found at: <https://lists.yoctoproject.org/g/licensing/join>
https://lists.yoctoproject.org/g/licensing/join and
<https://lists.yoctoproject.org/g/docs/join>
https://lists.yoctoproject.org/g/docs/join
...
Would it be possible to also create a yocto-devel or yocto-core
mailing list for discussing development of Yocto?

Currently the yocto list is a mixture of core development list and forum
for newbie user questions, with no easy way to have them separate.

Thanks
Adrian


Re: Yocto Project Status WW04'20

Adrian Bunk
 

On Tue, Jan 28, 2020 at 08:01:23AM -0800, Stephen Jolley wrote:
...
* We have created a "documentation" list and a "licensing" list on the
yocto project mailing list infrastructure. We believe these topics would
benefit from dedicated discussions, the people involved usually aren't
interested in bulk email as would be found on other lists. The new lists can
be found at: <https://lists.yoctoproject.org/g/licensing/join>
https://lists.yoctoproject.org/g/licensing/join and
<https://lists.yoctoproject.org/g/docs/join>
https://lists.yoctoproject.org/g/docs/join
...
Would it be possible to also create a yocto-devel or yocto-core
mailing list for discussing development of Yocto?

Currently the yocto list is a mixture of core development list and forum
for newbie user questions, with no easy way to have them separate.

Thanks
Adrian


Difference between: "poky-glibc-i686-core-image-sato-cortexa8hf-neon-toolchain" and "poky-glibc-i686-core-image-sato-cortexa8hf-neon-beaglebone-yocto-toolchain" #yocto

Milun Jovanovic
 

I apologize community for disturb but I have one simple question
A colleague has left company and now I have a job to update tool-chain from 2.2.2 to something newer.
The latest8by date) release of toolchain with the  same name appears in 2.6.4  release.
There is something that little confuses me , actually I see "my"  processor  in 3.0.1 release but it appears extra  "beaglebone" sting in toolchain.
The question is : May I use 3.0.1 toolchain for cortex8hf ?
Does  presence of beglebone board name makes difference for cortexa8hf  in 3.0.1?

http://downloads.yoctoproject.org/releases/yocto/yocto-2.6.4/toolchain/i686/poky-glibc-i686-core-image-sato-cortexa8hf-neon-toolchain-2.6.4.sh

http://downloads.yoctoproject.org/releases/yocto/yocto-3.0.1/toolchain/i686/poky-glibc-i686-core-image-sato-cortexa8hf-neon-beaglebone-yocto-toolchain-3.0.1.sh

Thank you in advance
Milun


Re: Sad news about Scott Rifenbark

Nicholas Krause
 



On 1/31/20 4:04 PM, Richard Purdie wrote:
I'm sorry to have to pass on the sad news that Scott Rifenbark, our
tech writer for the project passed away on Wednesday after a battle
with cancer.

I remember interviewing Scott over 10 years ago when forming a team at
Intel to work on what became the Yocto Project, he was with it from the
start. He warned me he wasn't an entirely traditional tech writer but I
warned we weren't aiming to be a traditional project either. It was a
great match. He stayed with the project ever since in one way or
another, he enjoyed working on the project and we enjoyed working with
him.

The concept of having a tech writer as part of the team was a decision
I'm proud of and it shows in the material supporting the project today
but that success belongs to Scott and his approach to it. Someone else
put that best, "He would first try the procedure or instructions before
documenting it, I was really impressed". He was hands on and wanted
things to be understandable and correct, a huge challenge with some of
the complexities we deal with.

Outside of the project he had interesting hobbies and travelled quite a
bit, those stories were good over beer and I have many fond memories.

Our documentation stands in his memory and its fitting some of his
character will always be in those words.

Scott will be hugely missed by us all.


Richard,
As someone who's been on and off with the project I've always found the documentation was
some of the best documentation I've ever seen rivaling that of the compiler manuals and 
wikis for LLVM and GCC in terms of being complete technical documents or the ISA manuals. 

Sorry to hear one if not the major tech writer behind it has passed and I've been spoiled
by the great documentation or the parts he wrote,
Nick

      

    


Re: [meta-openssl102-fips][PATCH] openssh: Fix patch to properly apply on 7.9 version found in warrior

Mark Hatle
 

Thanks for the pull request.. pushed.

--Mark

On 1/29/20 9:08 PM, Mark Hatle wrote:


On 1/29/20 8:49 PM, Mark Hatle wrote:
Should this be applied only to the warrior branch? I don't typically build
warrior branch, but I'm happy to accept patches if you can verify it's working
properly.
I tried to apply this patch, but unfortunately it's corrupt. Likely by an
exchange server or outlook.

If you can, you can generate a pull request at:

https://github.com/mhatle/meta-openssl102-fips

I prefer mailing list, but I realize sometime employers infrastructure can make
email more problematic then it otherwise should be..

--Mark

--Mark

On 1/29/20 12:47 PM, Davis, Michael wrote:
Signed-off-by: Michael Davis <michael.davis@essvote.com>
---
.../openssh/0001-openssh-8.0p1-fips.patch | 18 +++++++++++-------
1 file changed, 11 insertions(+), 7 deletions(-)

diff --git a/recipes-connectivity/openssh/openssh/0001-openssh-8.0p1-fips.patch
b/recipes-connectivity/openssh/openssh/0001-openssh-8.0p1-fips.patch
index 30534c7..5ff4eff 100644
--- a/recipes-connectivity/openssh/openssh/0001-openssh-8.0p1-fips.patch
+++ b/recipes-connectivity/openssh/openssh/0001-openssh-8.0p1-fips.patch
@@ -270,10 +270,10 @@ Index: git/readconf.c
===================================================================
--- git.orig/readconf.c
+++ git/readconf.c
-@@ -2077,17 +2077,18 @@ fill_default_options(Options * options)
- all_mac = mac_alg_list(',');
+@@ -2178,18 +2178,19 @@ fill_default_options(Options * options)
all_kex = kex_alg_list(',');
all_key = sshkey_alg_list(0, 0, 1, ',');
+ all_sig = sshkey_alg_list(0, 1, 1, ',');
-#define ASSEMBLE(what, defaults, all) \
+#define ASSEMBLE(what, defaults, fips_defaults, all) \
do { \
@@ -288,11 +288,13 @@ Index: git/readconf.c
- ASSEMBLE(kex_algorithms, KEX_SERVER_KEX, all_kex);
- ASSEMBLE(hostbased_key_types, KEX_DEFAULT_PK_ALG, all_key);
- ASSEMBLE(pubkey_key_types, KEX_DEFAULT_PK_ALG, all_key);
-+ ASSEMBLE(ciphers, KEX_CLIENT_ENCRYPT, KEX_FIPS_ENCRYPT, all_cipher);
-+ ASSEMBLE(macs, KEX_CLIENT_MAC, KEX_FIPS_MAC, all_mac);
-+ ASSEMBLE(kex_algorithms, KEX_CLIENT_KEX, KEX_DEFAULT_KEX_FIPS, all_kex);
+- ASSEMBLE(ca_sign_algorithms, SSH_ALLOWED_CA_SIGALGS, all_sig);
++ ASSEMBLE(ciphers, KEX_SERVER_ENCRYPT, KEX_FIPS_ENCRYPT, all_cipher);
++ ASSEMBLE(macs, KEX_SERVER_MAC, KEX_FIPS_MAC, all_mac);
++ ASSEMBLE(kex_algorithms, KEX_SERVER_KEX, KEX_DEFAULT_KEX_FIPS, all_kex);
+ ASSEMBLE(hostbased_key_types, KEX_DEFAULT_PK_ALG, KEX_FIPS_PK_ALG, all_key);
+ ASSEMBLE(pubkey_key_types, KEX_DEFAULT_PK_ALG, KEX_FIPS_PK_ALG, all_key);
++ ASSEMBLE(ca_sign_algorithms, SSH_ALLOWED_CA_SIGALGS, KEX_FIPS_PK_ALG, all_sig);
#undef ASSEMBLE
free(all_cipher);
free(all_mac);
@@ -314,10 +316,10 @@ Index: git/servconf.c
===================================================================
--- git.orig/servconf.c
+++ git/servconf.c
-@@ -198,17 +198,18 @@ assemble_algorithms(ServerOptions *o)
- all_mac = mac_alg_list(',');
+@@ -209,18 +209,19 @@ assemble_algorithms(ServerOptions *o)
all_kex = kex_alg_list(',');
all_key = sshkey_alg_list(0, 0, 1, ',');
+ all_sig = sshkey_alg_list(0, 1, 1, ',');
-#define ASSEMBLE(what, defaults, all) \
+#define ASSEMBLE(what, defaults, fips_defaults, all) \
do { \
@@ -332,12 +334,14 @@ Index: git/servconf.c
- ASSEMBLE(hostkeyalgorithms, KEX_DEFAULT_PK_ALG, all_key);
- ASSEMBLE(hostbased_key_types, KEX_DEFAULT_PK_ALG, all_key);
- ASSEMBLE(pubkey_key_types, KEX_DEFAULT_PK_ALG, all_key);
+- ASSEMBLE(ca_sign_algorithms, SSH_ALLOWED_CA_SIGALGS, all_sig);
+ ASSEMBLE(ciphers, KEX_SERVER_ENCRYPT, KEX_FIPS_ENCRYPT, all_cipher);
+ ASSEMBLE(macs, KEX_SERVER_MAC, KEX_FIPS_MAC, all_mac);
+ ASSEMBLE(kex_algorithms, KEX_SERVER_KEX, KEX_DEFAULT_KEX_FIPS, all_kex);
+ ASSEMBLE(hostkeyalgorithms, KEX_DEFAULT_PK_ALG, KEX_FIPS_PK_ALG, all_key);
+ ASSEMBLE(hostbased_key_types, KEX_DEFAULT_PK_ALG, KEX_FIPS_PK_ALG, all_key);
+ ASSEMBLE(pubkey_key_types, KEX_DEFAULT_PK_ALG, KEX_FIPS_PK_ALG, all_key);
++ ASSEMBLE(ca_sign_algorithms, SSH_ALLOWED_CA_SIGALGS, KEX_FIPS_PK_ALG, all_sig);
#undef ASSEMBLE
free(all_cipher);
free(all_mac);
--
2.24.1


*Disclaimer*

The information contained in this communication from the sender is confidential.
It is intended solely for use by the recipient and others authorized to receive
it. If you are not the recipient, you are hereby notified that any disclosure,
copying, distribution or taking action in relation of the contents of this
information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been
automatically archived by *Mimecast Ltd*, an innovator in Software as a Service
(SaaS) for business. Providing a *safer* and *more useful* place for your human
generated data. Specializing in; Security, archiving and compliance. To find out
more Click Here <http://www.mimecast.com/products/>.








Sad news about Scott Rifenbark

Richard Purdie
 

I'm sorry to have to pass on the sad news that Scott Rifenbark, our
tech writer for the project passed away on Wednesday after a battle
with cancer.

I remember interviewing Scott over 10 years ago when forming a team at
Intel to work on what became the Yocto Project, he was with it from the
start. He warned me he wasn't an entirely traditional tech writer but I
warned we weren't aiming to be a traditional project either. It was a
great match. He stayed with the project ever since in one way or
another, he enjoyed working on the project and we enjoyed working with
him.

The concept of having a tech writer as part of the team was a decision
I'm proud of and it shows in the material supporting the project today
but that success belongs to Scott and his approach to it. Someone else
put that best, "He would first try the procedure or instructions before
documenting it, I was really impressed". He was hands on and wanted
things to be understandable and correct, a huge challenge with some of
the complexities we deal with.

Outside of the project he had interesting hobbies and travelled quite a
bit, those stories were good over beer and I have many fond memories.

Our documentation stands in his memory and its fitting some of his
character will always be in those words.

Scott will be hugely missed by us all.


Re: QA Cycle report for build (yocto-3.1_M2.rc1)

Armin Kuster
 

Sangeeta,

On 1/30/20 11:46 PM, Sangeeta Jain wrote:
Hello All,

This is the full report for yocto-3.1_M2.rc1:  
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.  
No new defects are found in this cycle.
starce ptest failed (BUG id:13765). 

Note: failure for test_ltp_help, test_stap, test_mmc_mount, test_usb_mount is observed on Beaglebone, edgerouter and mpc8315erdb. 
Please bug the test_mmc and test_usb as I am the one who added those storage test.

TIA,
armin
QA team is analysing more on failures. 

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13765

Thanks,
Sangeeta



-----Original Message-----
From: Pokybuild User <pokybuild@...>
Sent: Thursday, 23 January, 2020 5:25 AM
To: yocto@...
Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
<apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan,
Aaron Chun Yew <aaron.chun.yew.chan@...>;
richard.purdie@...; akuster808@...;
sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...>
Subject: QA notification for completed autobuilder build (yocto-3.1_M2.rc1)


A build flagged for QA (yocto-3.1_M2.rc1) was completed on the autobuilder
and is available at:


    https://autobuilder.yocto.io/pub/releases/yocto-3.1_M2.rc1


Build hash information:

bitbake: d5a4a352723258b4d499d3a51f340109c4f36f60
meta-gplv2: 6107be140fdec204586850ea1f7e4b968be7670b
meta-intel: 0c092dde58bb688dca787c653ee7a3282d58aeab
meta-mingw: e3dadc9f28c24a8d182121d0246b3d9ec048846a
oecore: 15049c610bcfd0a3e161379651b5ea117ea02715
poky: ca3993cc4b13d4e661228cee6fb9448adfd0a4ba



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@...





      


Re: Yocto [thud], [zeus] do_fetch and do_unpack failures with offline/online svn build! #yocto #python

Khem Raj
 

On 1/31/20 4:02 AM, georgi.georgiev via Lists.Yoctoproject.Org wrote:
Hello Community,
This is the third time I am asking for support on this issue. This time I decided to use the web form.
In our project we have a requirement to be able to build the project offline. E.g. on the field without any network connection. When we are connected with the recipe mentioned below we don't have issues:

svn: E170013: Unable to connect to a repository at URL 'http://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys/trunk'
svn: E670003: Temporary failure in name resolution

can you try checking out the repo out side of fetcher and see if the machine can fetch the url you are using in SRC_URI ?

*SUMMARY = "PACMan - Parameter And Configuration MANager"*
*LICENSE = "CLOSED"*
*inherit systemd useradd*
*REQUIRED_DISTRO_FEATURES = "systemd"*
*# SVN revision*
*PV = "121026"*
*# Name of SVN project*
*PACMAN_PROJ_NAME="SOCPACManEnvEngKeys"*
*SRC_URI = "svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/${PACMAN_PROJ_NAME};module=trunk;protocol=http;externals=allowed;rev=${PV}"*
*SRC_URI += "file://ww-authpacman.service"*
*SRC_URI += "file://ww-pacman.service"*
*S = "${WORKDIR}/trunk/"*
*# ${PN}-sys: content related to system, which goes to base rootfs (only .service file and symlinks)*
*# ${PN}:      real content which may go to separate partition*
*PACKAGES =+ " ${PN}-sys"*
.........
When disconnect the network, erase sstate-cache, cache and tmp I see log file attached (log.do_fetch.32757) and the following output:
*ERROR: ww-pacman-121026-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="11412"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/w23698/projects/proj_dvp2/build_dvp2/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/w23698/projects/proj_dvp2/sources/poky/scripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot/usr/bin/crossscripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/bin:/home/w23698/projects/proj_dvp2/sources/poky/bitbake/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/hosttools"; export HOME="/home/w23698"; /usr/bin/env svn --non-interactive --trust-server-cert update --no-auth-cache -r 121026 failed with exit code 1, output:*
*Updating '.':*
*svn: E170013: Unable to connect to a repository at URL 'http://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys/trunk'*
*svn: E670003: Temporary failure in name resolution*
*ERROR: ww-pacman-121026-r0 do_fetch: Fetcher failure for URL: 'svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/SOCPACManEnvEngKeys;module=trunk;protocol=http;externals=allowed;rev=121026'. Unable to fetch URL from any source.*
*ERROR: Logfile of failure stored in: /home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/temp/log.do_fetch.32757*
*ERROR: Task (/home/w23698/projects/proj_dvp2/build_dvp2/../sources/meta-ww-dvp2/recipes-ww/ww-pacman/ww-pacman.bb:do_fetch) failed with exit code '1'*
When remove the '\' character in SRC_URI, e.g. to become:
*SRC_URI = "svn://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/${PACMAN_PROJ_NAME};module=trunk;protocol=http;externals=allowed;rev=${PV}"*
In connected and not connected to network do_fetch() passes successfully but I see one and same error (log.do_unpack.25226) output:
*ERROR: ww-pacman-121026-r0 do_unpack: Unpack failure for URL: 'svn://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys;module=trunk;protocol=http;externals=allowed;rev=121026'. Unpack command PATH="/home/w23698/projects/proj_dvp2/build_dvp2/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/w23698/projects/proj_dvp2/sources/poky/scripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot/usr/bin/crossscripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/bin:/home/w23698/projects/proj_dvp2/sources/poky/bitbake/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/hosttools" tar xz --no-same-owner -f /home/w23698/projects/proj_dvp2/build_dvp2/downloads/trunk_cocosubversion_.svn.Embedded.Valve&Actuator.DVPII.trunk.SOCPACManEnvEngKeys_121026_.tar.gz failed with return value 127*
*ERROR: Logfile of failure stored in: /home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/temp/log.do_unpack.25226*
*ERROR: Task (/home/w23698/projects/proj_dvp2/build_dvp2/../sources/meta-ww-dvp2/recipes-ww/ww-pacman/ww-pacman.bb:do_unpack) failed with exit code '1'
*
I don't it this matters but, the build machine is baremetal Ubuntu 18.04.3 LTS. In all cases the packed tar.gz remain in downloads directory with one name!
Cordially,
Georgi


[meta-qt5, zeus-next, python3-pyqt5] QtChart can't be imported

Adrian
 

Hi,

I use python3-pyqt5 from meta-qt5 (in zeus-next). I get an error in python3 when I try to import QtChart module (from PyQt5 import QtChart). Has anybody experience the same issue and knows a fix? The deployed image comes with qtchart packages.

I have created an issue on the layer's issue tracker (link), but so far no reply.

Regards,

Adrian


Still missing ubi after added and_config,ubifs

JH
 

Hi,

How can I build u-boot for running on RAM? I add UBOOT_CONFIG[nand] =
"mx6ull_14x14_evk_nand_config,ubifs", but I still got errors in
u-boot:

Unknown command 'ubi' - try 'help'
Unknown command 'ubi' - try 'help'
Unknown command 'ubi' - try 'help'

What I could be missing ubi command in u-boot?

Thank you.

- jh


Re: Yocto [thud], [zeus] do_fetch and do_unpack failures with offline/online svn build! #yocto #python

Mikko Rapeli
 

Hi,

I can't comment on svn fetcher but I use subversion via http
fetcher. This way the local download cache can have the exact same file
and builds can continue off line. One major gotcha is that all files
uploaded to svn must have unique and versioned file names. Updating the
same file to different content will result in using the old cache file version.

Maybe this helps,

-Mikko


Yocto [thud], [zeus] do_fetch and do_unpack failures with offline/online svn build! #yocto #python

Georgi Georgiev
 

Hello Community,
This is the third time I am asking for support on this issue. This time I decided to use the web form.
In our project we have a requirement to be able to build the project offline. E.g. on the field without any network connection. When we are connected with the recipe mentioned below we don't have issues:

SUMMARY = "PACMan - Parameter And Configuration MANager"
LICENSE = "CLOSED"
inherit systemd useradd
REQUIRED_DISTRO_FEATURES = "systemd"
# SVN revision
PV = "121026"
# Name of SVN project
PACMAN_PROJ_NAME="SOCPACManEnvEngKeys"
SRC_URI = "svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/${PACMAN_PROJ_NAME};module=trunk;protocol=http;externals=allowed;rev=${PV}"
SRC_URI += "file://ww-authpacman.service"
SRC_URI += "file://ww-pacman.service"
S = "${WORKDIR}/trunk/"
# ${PN}-sys: content related to system, which goes to base rootfs (only .service file and symlinks)
# ${PN}:      real content which may go to separate partition
PACKAGES =+ " ${PN}-sys"
.........
When disconnect the network, erase sstate-cache, cache and tmp I see log file attached (log.do_fetch.32757) and the following output:

ERROR: ww-pacman-121026-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"; export SSH_AGENT_PID="11412"; export SSH_AUTH_SOCK="/run/user/1000/keyring/ssh"; export PATH="/home/w23698/projects/proj_dvp2/build_dvp2/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/w23698/projects/proj_dvp2/sources/poky/scripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot/usr/bin/crossscripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/bin:/home/w23698/projects/proj_dvp2/sources/poky/bitbake/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/hosttools"; export HOME="/home/w23698"; /usr/bin/env svn --non-interactive --trust-server-cert update --no-auth-cache -r 121026 failed with exit code 1, output:
Updating '.':
svn: E170013: Unable to connect to a repository at URL 'http://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys/trunk'
svn: E670003: Temporary failure in name resolution
ERROR: ww-pacman-121026-r0 do_fetch: Fetcher failure for URL: 'svn://cocosubversion/svn/Embedded/Valve\&Actuator/DVPII/trunk/SOCPACManEnvEngKeys;module=trunk;protocol=http;externals=allowed;rev=121026'. Unable to fetch URL from any source.
ERROR: Logfile of failure stored in: /home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/temp/log.do_fetch.32757
ERROR: Task (/home/w23698/projects/proj_dvp2/build_dvp2/../sources/meta-ww-dvp2/recipes-ww/ww-pacman/ww-pacman.bb:do_fetch) failed with exit code '1'

When remove the '\' character in SRC_URI, e.g. to become:

SRC_URI = "svn://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/${PACMAN_PROJ_NAME};module=trunk;protocol=http;externals=allowed;rev=${PV}"

In connected and not connected to network do_fetch() passes successfully but I see one and same error (log.do_unpack.25226) output: 

ERROR: ww-pacman-121026-r0 do_unpack: Unpack failure for URL: 'svn://cocosubversion/svn/Embedded/Valve&Actuator/DVPII/trunk/SOCPACManEnvEngKeys;module=trunk;protocol=http;externals=allowed;rev=121026'. Unpack command PATH="/home/w23698/projects/proj_dvp2/build_dvp2/tmp/sysroots-uninative/x86_64-linux/usr/bin:/home/w23698/projects/proj_dvp2/sources/poky/scripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin/arm-poky-linux-gnueabi:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot/usr/bin/crossscripts:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/usr/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/sbin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/recipe-sysroot-native/bin:/home/w23698/projects/proj_dvp2/sources/poky/bitbake/bin:/home/w23698/projects/proj_dvp2/build_dvp2/tmp/hosttools" tar xz --no-same-owner -f /home/w23698/projects/proj_dvp2/build_dvp2/downloads/trunk_cocosubversion_.svn.Embedded.Valve&Actuator.DVPII.trunk.SOCPACManEnvEngKeys_121026_.tar.gz failed with return value 127
ERROR: Logfile of failure stored in: /home/w23698/projects/proj_dvp2/build_dvp2/tmp/work/cortexa9hf-neon-poky-linux-gnueabi/ww-pacman/121026-r0/temp/log.do_unpack.25226
ERROR: Task (/home/w23698/projects/proj_dvp2/build_dvp2/../sources/meta-ww-dvp2/recipes-ww/ww-pacman/ww-pacman.bb:do_unpack) failed with exit code '1'

I don't it this matters but, the build machine is baremetal Ubuntu 18.04.3 LTS. In all cases the packed tar.gz remain in downloads directory with one name!

Cordially,
Georgi


Re: [yocto-autobuilder2][PATCH] config.py: remove mpc8315-rdb

Richard Purdie
 

On Thu, 2020-01-30 at 16:19 -0800, akuster wrote:
Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
config.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/config.py b/config.py
index 7dbd5e7..b210275 100644
--- a/config.py
+++ b/config.py
@@ -51,7 +51,6 @@ trigger_builders_wait_shared = [
"qemux86-64", "qemux86-64-alt",
"qemux86-64-x32", "qemux86-world",
"edgerouter",
- "mpc8315e-rdb",
"genericx86", "genericx86-alt",
"genericx86-64", "genericx86-64-alt",
"beaglebone", "beaglebone-alt",
@@ -70,14 +69,14 @@ trigger_builders_wait_quick = trigger_builders_wait_shared + [
]

trigger_builders_wait_full = trigger_builders_wait_shared + [
- "qemumips-alt", "edgerouter-alt", "mpc8315e-rdb-alt", "qemuppc-alt", "qemux86-world-alt",
+ "qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora", "oe-selftest-centos",
"qemux86-64-ptest", "buildperf-ubuntu1604", "buildperf-centos7", "qemux86-64-ltp",
"qemuarm64-ptest", "qemuarm64-ltp", "meta-intel"
]

trigger_builders_wait_releases = {
- "sumo" : trigger_builders_wait_shared + ["qemumips-alt", "edgerouter-alt", "mpc8315e-rdb-alt", "qemuppc-alt", "qemux86-world-alt",
+ "sumo" : trigger_builders_wait_shared + ["qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-centos"]
}
You can't do that if you still want to build it in older releases...

Cheers,

Richard


QA Cycle report for build (yocto-3.1_M2.rc1)

Sangeeta Jain
 

Hello All,

This is the full report for yocto-3.1_M2.rc1:
https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/?h=intel-yocto-testresults

======= Summary ========
No high milestone defects.
No new defects are found in this cycle.
starce ptest failed (BUG id:13765).

Note: failure for test_ltp_help, test_stap, test_mmc_mount, test_usb_mount is observed on Beaglebone, edgerouter and mpc8315erdb.
QA team is analysing more on failures.

======= Bugs ========
https://bugzilla.yoctoproject.org/show_bug.cgi?id=13765

Thanks,
Sangeeta

-----Original Message-----
From: Pokybuild User <pokybuild@debian10-ty-1.yocto.io>
Sent: Thursday, 23 January, 2020 5:25 AM
To: yocto@lists.yoctoproject.org
Cc: otavio@ossystems.com.br; yi.zhao@windriver.com; Sangal, Apoorv
<apoorv.sangal@intel.com>; Yeoh, Ee Peng <ee.peng.yeoh@intel.com>; Chan,
Aaron Chun Yew <aaron.chun.yew.chan@intel.com>;
richard.purdie@linuxfoundation.org; akuster808@gmail.com;
sjolley.yp.pm@gmail.com; Jain, Sangeeta <sangeeta.jain@intel.com>
Subject: QA notification for completed autobuilder build (yocto-3.1_M2.rc1)


A build flagged for QA (yocto-3.1_M2.rc1) was completed on the autobuilder
and is available at:


https://autobuilder.yocto.io/pub/releases/yocto-3.1_M2.rc1


Build hash information:

bitbake: d5a4a352723258b4d499d3a51f340109c4f36f60
meta-gplv2: 6107be140fdec204586850ea1f7e4b968be7670b
meta-intel: 0c092dde58bb688dca787c653ee7a3282d58aeab
meta-mingw: e3dadc9f28c24a8d182121d0246b3d9ec048846a
oecore: 15049c610bcfd0a3e161379651b5ea117ea02715
poky: ca3993cc4b13d4e661228cee6fb9448adfd0a4ba



This is an automated message from the Yocto Project Autobuilder
Git: git://git.yoctoproject.org/yocto-autobuilder2
Email: richard.purdie@linuxfoundation.org



Re: [meta-selinux][PATCH 1/2] python: move appends to a dynamic-layer

Joe MacDonald
 

Thanks for these, Jeremy, I'd just been prepping the same patches today,
but since yours are on-list, I'm merging them.

-J.

[[yocto] [meta-selinux][PATCH 1/2] python: move appends to a dynamic-layer] On 20.01.30 (Thu 15:28) Jeremy Puhlman wrote:

Signed-off-by: Jeremy Puhlman <jpuhlman@mvista.com>
---
conf/layer.conf | 2 ++
.../recipes-devtools}/python/files/sitecustomize.py | 0
.../python2-layer/recipes-devtools}/python/python_%.bbappend | 0
.../python2-layer/recipes-devtools}/python/python_selinux.inc | 0
4 files changed, 2 insertions(+)
rename {recipes-devtools => dynamic-layers/python2-layer/recipes-devtools}/python/files/sitecustomize.py (100%)
rename {recipes-devtools => dynamic-layers/python2-layer/recipes-devtools}/python/python_%.bbappend (100%)
rename {recipes-devtools => dynamic-layers/python2-layer/recipes-devtools}/python/python_selinux.inc (100%)

diff --git a/conf/layer.conf b/conf/layer.conf
index 226a75a..cdee27a 100644
--- a/conf/layer.conf
+++ b/conf/layer.conf
@@ -11,6 +11,8 @@ BBFILES_DYNAMIC += "openembedded-layer:${LAYERDIR}/dynamic-layers/openembedded-l
networking-layer:${LAYERDIR}/dynamic-layers/networking-layer/*/*/*.bbappend \
virtualization-layer:${LAYERDIR}/dynamic-layers/virtualization-layer/recipes*/*/*.bb \
virtualization-layer:${LAYERDIR}/dynamic-layers/virtualization-layer/recipes*/*/*.bbappend \
+ meta-python2:${LAYERDIR}/dynamic-layers/python2-layer/recipes*/*/*.bb \
+ meta-python2:${LAYERDIR}/dynamic-layers/python2-layer/recipes*/*/*.bbappend \
"

BBFILE_COLLECTIONS += "selinux"
diff --git a/recipes-devtools/python/files/sitecustomize.py b/dynamic-layers/python2-layer/recipes-devtools/python/files/sitecustomize.py
similarity index 100%
rename from recipes-devtools/python/files/sitecustomize.py
rename to dynamic-layers/python2-layer/recipes-devtools/python/files/sitecustomize.py
diff --git a/recipes-devtools/python/python_%.bbappend b/dynamic-layers/python2-layer/recipes-devtools/python/python_%.bbappend
similarity index 100%
rename from recipes-devtools/python/python_%.bbappend
rename to dynamic-layers/python2-layer/recipes-devtools/python/python_%.bbappend
diff --git a/recipes-devtools/python/python_selinux.inc b/dynamic-layers/python2-layer/recipes-devtools/python/python_selinux.inc
similarity index 100%
rename from recipes-devtools/python/python_selinux.inc
rename to dynamic-layers/python2-layer/recipes-devtools/python/python_selinux.inc
--
2.20.1
--
-Joe MacDonald.
:wq


[yocto-autobuilder2][PATCH] config.py: remove mpc8315-rdb

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
config.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/config.py b/config.py
index 7dbd5e7..b210275 100644
--- a/config.py
+++ b/config.py
@@ -51,7 +51,6 @@ trigger_builders_wait_shared = [
"qemux86-64", "qemux86-64-alt",
"qemux86-64-x32", "qemux86-world",
"edgerouter",
- "mpc8315e-rdb",
"genericx86", "genericx86-alt",
"genericx86-64", "genericx86-64-alt",
"beaglebone", "beaglebone-alt",
@@ -70,14 +69,14 @@ trigger_builders_wait_quick = trigger_builders_wait_shared + [
]

trigger_builders_wait_full = trigger_builders_wait_shared + [
- "qemumips-alt", "edgerouter-alt", "mpc8315e-rdb-alt", "qemuppc-alt", "qemux86-world-alt",
+ "qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-fedora", "oe-selftest-centos",
"qemux86-64-ptest", "buildperf-ubuntu1604", "buildperf-centos7", "qemux86-64-ltp",
"qemuarm64-ptest", "qemuarm64-ltp", "meta-intel"
]

trigger_builders_wait_releases = {
- "sumo" : trigger_builders_wait_shared + ["qemumips-alt", "edgerouter-alt", "mpc8315e-rdb-alt", "qemuppc-alt", "qemux86-world-alt",
+ "sumo" : trigger_builders_wait_shared + ["qemumips-alt", "edgerouter-alt", "qemuppc-alt", "qemux86-world-alt",
"oe-selftest-ubuntu", "oe-selftest-debian", "oe-selftest-centos"]
}

--
2.17.1


[yocto-autobuilder-helper][PATCH] yocto-autobuilder-helper: remove mpc8315 from configs

Armin Kuster
 

Signed-off-by: Armin Kuster <akuster808@gmail.com>
---
config.json | 8 --------
scripts/publish-artefacts | 12 +-----------
2 files changed, 1 insertion(+), 19 deletions(-)

diff --git a/config.json b/config.json
index cf7710a..f7e2b84 100644
--- a/config.json
+++ b/config.json
@@ -327,14 +327,6 @@
"MACHINE" : "qemuppc",
"TEMPLATE" : "altcfg-qemu"
},
- "mpc8315e-rdb" : {
- "MACHINE" : "mpc8315e-rdb",
- "TEMPLATE" : "arch-hw"
- },
- "mpc8315e-rdb-alt" : {
- "MACHINE" : "mpc8315e-rdb",
- "TEMPLATE" : "altcfg-hw"
- },
"qemux86" : {
"MACHINE" : "qemux86",
"TEMPLATE" : "arch-qemu",
diff --git a/scripts/publish-artefacts b/scripts/publish-artefacts
index 75ed1b5..f642fac 100755
--- a/scripts/publish-artefacts
+++ b/scripts/publish-artefacts
@@ -15,7 +15,7 @@ md5sums(){
TMPDIR=$WORKDIR/tmp

case "$target" in
- "qemuarm"|"qemuarm64"|"qemumips64"|"qemumips"|"qemuppc"|"qemux86"|"qemux86-64"|"edgerouter"|"mpc8315e-rdb"|"genericx86"|"genericx86-64"|"beaglebone")
+ "qemuarm"|"qemuarm64"|"qemumips64"|"qemumips"|"qemuppc"|"qemux86"|"qemux86-64"|"edgerouter"|"genericx86"|"genericx86-64"|"beaglebone")
mkdir -p $DEST/toolchain/i686
mkdir -p $DEST/toolchain/x86_64
md5sums $TMPDIR/deploy/sdk
@@ -107,21 +107,11 @@ case "$target" in
md5sums $TMPDIR/deploy/images/qemuppc
cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/qemuppc/*qemuppc* $DEST/machines/qemu/qemuppc
;;
- "mpc8315e-rdb")
- mkdir -p $DEST/machines/mpc8315e-rdb
- md5sums $TMPDIR/deploy/images/mpc8315e-rdb
- cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/mpc8315e-rdb/*mpc8315* $DEST/machines/mpc8315e-rdb
- ;;
"qemuppc-alt")
mkdir -p $DEST/machines/qemu/qemuppc-alt
md5sums $TMPDIR/deploy/images/qemuppc
cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/qemuppc/*qemuppc* $DEST/machines/qemu/qemuppc-alt
;;
- "mpc8315e-rdb-alt")
- mkdir -p $DEST/machines/mpc8315e-rdb-alt
- md5sums $TMPDIR/deploy/images/mpc8315e-rdb
- cp -R --no-dereference --preserve=links $TMPDIR/deploy/images/mpc8315e-rdb/*mpc8315* $DEST/machines/mpc8315e-rdb-alt
- ;;
"wic")
mkdir -p $DEST/machines/qemu/qemux86
md5sums $TMPDIR/deploy/wic_images/qemux86
--
2.17.1

7221 - 7240 of 55458