Re: [yocto] [meta-security][PATCH 1/2] oe-selftest: add running cve checker

2019-06-14 Thread akuster808
Chen, On 6/14/19 1:13 AM, ChenQi wrote: > Hi Armin, > > I just noticed this selftest case. > Have you considered putting it into oe-core? Yes I have. That was the first place I wanted to put it but Richard and Ross have reservations about doing that so it sits in meta-security until we can get it

[yocto] Early Registration Deadline: Yocto Project DevDay NA 2019

2019-06-14 Thread Volosincu, Andreea S
Time is almost up for the Yocto Project DevDay NA 2019 early registration. Register separately or add it to your OSS NA registration. https://www.cvent.com/events/yocto-dev-day-north-america-2019/registration-cfa8da9b8d0b43bdb92f3e81493ca2ce.aspx?fqp=true Thanks! Yocto Project Advocacy Team --

Re: [yocto] dnf causing build failure

2019-06-14 Thread Larry Brown
So I got the ${B} from the original openssh recipe so I'm not sure what that variable equates to now. But I changed to ${D} and had to change some other aspects as well. What I didn't understand is that the recipe is installing the files into a folder (package folder) that is ultimately packaged

[yocto] nativesdk-expect configure error

2019-06-14 Thread Martin Townsend
Hi, I'm seeing the following do_configure error when building nativesdk-expect, this is in Rocko but the recipe doesn't look like it's changed much in master. checking for Tcl public headers... configure: error: tcl.h not found. Please specify its location with --with-tclinclude | NOTE: The

[yocto] Build failure on kernel-devsrc

2019-06-14 Thread Adam Lee
At some point I noticed I *must* clean kernel-devsrc before I can build my image with Kernel changes. I suppose this isn't normal and expect it rebuild what's necessary as part of the image build. Has anyone seen this before? Build Configuration: BB_VERSION = "1.36.0" BUILD_SYS

[yocto] [ptest-runner][PATCH v2 3/4] utils: Ensure pipes are read after exit

2019-06-14 Thread Randy MacLeod
From: Richard Purdie There was a race in the code where the pipes may not be read after the process has exited and data may be left behind in them. This change to ordering ensures the pipes are read after the exit code has been read meaning no data can be left behind and the logs should be

[yocto] [ptest-runner][PATCH v2 4/4] utils: ensure child can be session leader

2019-06-14 Thread Randy MacLeod
When running the run-execscript bash ptest as a user rather than root, a warning: bash: cannot set terminal process group (16036): Inappropriate ioctl for device bash: no job control in this shell contaminates the bash log files causing the test to fail. This happens only when run under

[yocto] [ptest-runner][PATCH v2] 3 old patches + utils: ensure child can be session leader

2019-06-14 Thread Randy MacLeod
My patch needs Richards previous 3 patches so I've added them here. I've cleaned up the patch a bit since v1; mostly it's indentation and other cosmetic changes. I have added a bit more error handling and I've renamed get_slave_pty to setup_slave_pty to more accurately reflect what the function

[yocto] [ptest-runner][PATCH v2 2/4] use process groups when spawning

2019-06-14 Thread Randy MacLeod
From: Richard Purdie Rather than just killing the process we've swawned, set the process group for spawned children and then kill the group of processes. Signed-off-by: Richard Purdie Upstream-Status: Pending [code being tested] --- utils.c | 3 ++- 1 file changed, 2 insertions(+), 1

[yocto] [ptest-runner][PATCH v2 1/4] utils: Ensure stdout/stderr are flushed

2019-06-14 Thread Randy MacLeod
From: Richard Purdie There is no guarantee that the data written with fwrite will be flushed to the buffer. If stdout and stderr are the same thing, this could lead to interleaved writes. The common case is stdout output so flush the output pipes when writing to stderr. Also flush stdout before

Re: [yocto] dnf causing build failure

2019-06-14 Thread Alexander Kanavin
Should be ${D}, not ${B} in do_install. Alex On Fri, 14 Jun 2019 at 15:53, Larry Brown wrote: > I've created a recipe that simply copies files into a folder of the > image. Basically in this form: > > -- > > SUMMARY = "Some text" > HOMEPAGE

[yocto] dnf causing build failure

2019-06-14 Thread Larry Brown
I've created a recipe that simply copies files into a folder of the image. Basically in this form: -- SUMMARY = "Some text" HOMEPAGE = "" LICENSE = "CLOSED" LIC_FILES_CHKSUM = "" DEPENDS = "openssl" do_install () { install -m 0644

Re: [yocto] [meta-swupdate] failed update leads to kernel panic

2019-06-14 Thread Stefano Babic
Hi Moritz, On 14/06/19 12:19, Moritz Porst wrote: > (Sorry, the answer should go to everyone) > Thanks for your response, unfortunately it didn't work out for me. > Because I am not 100% sure whether I did the correct thing I describe it: > In my layer I went to recipes-kernel/kernel/files, here

Re: [yocto] [meta-swupdate] failed update leads to kernel panic

2019-06-14 Thread Moritz Porst
(Sorry, the answer should go to everyone) Thanks for your response, unfortunately it didn't work out for me. Because I am not 100% sure whether I did the correct thing I describe it: In my layer I went to recipes-kernel/kernel/files, here I added a file defconfig which I filled with the

[yocto] Can't build SDK while shrinking shadow tools

2019-06-14 Thread Jérémy Singy
Hi, I'm facing a problem by trying to shrink the size of our root filesystem. To avoid installing some unneeded tools such as adduser, groupadd, nologin, etc. I just created as usual a shadow_%.bbappend in our layer which removes the content using do_install_append: # do not install

Re: [yocto] [meta-swupdate] failed update leads to kernel panic

2019-06-14 Thread Zoran Stojsavljevic
> However if I abort the update while running (i.e. simulating a power cut) > and then reboot I end up in a kernel panic: "Unable to mount rootfs on > unknown block". My understanding is that I should at least end up in a > busybox or that the update is retried, but this does not happen. You

[yocto] [meta-swupdate] failed update leads to kernel panic

2019-06-14 Thread Moritz Porst
Hello,   I am currently having trouble to get swupdate working properly. My problem: I can execute swupdate -i normally and if the update fits I have no problem. However if I abort the update while running (i.e. simulating a power cut) and then reboot I end up in a kernel panic: "Unable to

Re: [yocto] [meta-security][PATCH 1/2] oe-selftest: add running cve checker

2019-06-14 Thread ChenQi
Hi Armin, I just noticed this selftest case. Have you considered putting it into oe-core? Best Regards, Chen Qi On 05/10/2019 11:09 AM, Armin Kuster wrote: Signed-off-by: Armin Kuster --- lib/oeqa/selftest/cases/cvechecker.py | 27 +++ 1 file changed, 27

Re: [yocto] QA notification for completed autobuilder build (yocto-2.8_M1.rc2)

2019-06-14 Thread Jain, Sangeeta
QA cycle report for 2.8 M1 RC2: 1. No high milestone defects. 2. Test results are available at following location: • For results of all automated tests, please refer to results at public AB [1] • For other test results, refer to git repo "