Re: [yocto] download.yoctoproject.org - Certificate expired

hi Guilhem, On Sun, Oct 13, 2019 at 12:00 PM Guilhem Saurel wrote: > > Hi, > > The certificate installed on https://download.yoctoproject.org expired about 4 > days ago. Is anyone else experiencing the same issue? Is a new certificate > going > to be installed ? thanks for reporting the issue.

Re: [yocto] Kernel patches pulled from BSP definition file are not applied

> From: Bruce Ashfield > > On Fri, Oct 11, 2019 at 1:11 PM Diego Santa Cruz > wrote: > > > > Can anyone provide some advice as to what would be the recommended way > to apply kernel patches listed in a mybsp-patches.scc file for a BSP? > > > > The way to do this, is to put your BSP definition

[yocto] No SELinux security context (/etc/crontab)

Hi, I have enabled SELinux in my yocto project(warrior branch) but cron is not functioning because of some SELinux context isuue. I am using minimum SELinux policy. Here is the error from `/var/log/messages` Oct 9 04:50:01 panther2 cron.info crond[261]: ((null)) No SELinux security contex

[yocto] [OE-core][opkg-utils ] Bug 13528 : adding SPDX license identifier

Hi guys, https://bugzilla.yoctoproject.org/show_bug.cgi?id=13528 I'm about to work on that bug however most of the script in opkg-utils dir are un-licenced and there's no hint for me to decide what SPDX Identifier to add. The doubt concerns those script : makePackage opkg-build opkg-buildpackage

Re: [yocto] Where to get kconfig-frontends package?

Hello! Thank you very much for helpful answer. So, we switch the source to this. *Matous Pokorny* Embedded System Developer *DataVision s.r.o.* Ukrajinska 2a 101 00 Praha 10 Czech Republic GSM: (+420) 723 280 471 matous.poko...@datavision.cz čt 10. 10. 2019 v 11:07 odesílatel Peter Kjellerste

[yocto] Partitioning SD cards

Hello, I am working on a custom platform where U-Boot will be programmed into an SPI NOR flash device and the ext4 file systems will be in a removable microSD card. The Linux kernel itself will be stored in the /boot directory of the root file system. The customer wants the (16GB) microSD c

Re: [yocto] [opkg-devel] [OE-core][opkg-utils ] Bug 13528 : adding SPDX license identifier

Hi, GPL-2.0-only was applied to script without previous Licences and GPL-2.0-or-later to those mentioning it, however I'm wondering if I should also add a SPDX id to the makefile ? Here's first attempt without identifier to the Makefile. Best regards, On Fri, Oct 11, 2019 at 6:45 PM wrote:

Re: [yocto] Partitioning SD cards

Maciej wrote... How do I stop the wic generation process including the FAT formatted “boot” partition? This depends on the wic (.wks) file you are using. I have been using the default one (sdimage-bootpart.wks)? What is the best strategy for partitioning / formatting / mounting the second pa

Re: [yocto] Partitioning SD cards

On 14.10.2019 14:13, Andy Pont wrote: > Hello, > > I am working on a custom platform where U-Boot will be programmed into > an SPI NOR flash device and the ext4 file systems will be in a > removable microSD card.  The Linux kernel itself will be stored in the > /boot directory of the root file sys

Re: [yocto] Partitioning SD cards

I wrote... I have created a “wic” directory in my custom layer and copied sdimage-bootpart.wks into it as sdimage-project.wks without making any changes but “wic list image” throws an error with the new .wks file: UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb0 in position 37: inval

Re: [yocto] No SELinux security context (/etc/crontab)

There SE Linux policy included in meta-selinux is just a starting point. It's expected that you will have to update/customize it. With that said, these types of issues, we will accept patches for them. --Mark On 10/10/19 5:06 AM, Oriya, Raxesh wrote: > Hi, > >   > > I have enabled SELinux in

Re: [yocto] Kernel patches pulled from BSP definition file are not applied

On Mon, Oct 14, 2019 at 5:50 AM Diego Santa Cruz wrote: > > > From: Bruce Ashfield > > > > On Fri, Oct 11, 2019 at 1:11 PM Diego Santa Cruz > > wrote: > > > > > > > Can anyone provide some advice as to what would be the recommended way > > to apply kernel patches listed in a mybsp-patches.scc fi

[yocto] NooB: qemu-native compile error during bitbake core-image-sato

Hello list, First time here so, hi there :-) I'm new to yocto but not new to linux. I'm following the Yocto Project Quick Build manual (https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html) on an Arch (Manjaro) machine (uname -r: 4.19.79-1-MANJARO). I know Man

[yocto] Yocto Project Newcomer & Unassigned Bugs - Help Needed

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on the triage page under the appropriate heading: https://wiki.yoctoproject.org/wiki/Bug_Triage#New

Re: [yocto] NooB: qemu-native compile error during bitbake core-image-sato

On 14/10/2019 17:20, p...@iae.nl wrote: Hello list, First time here so, hi there :-) I'm new to yocto but not new to linux. I'm following the Yocto Project Quick Build manual (https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoprojectqs.html) on an Arch (Manjaro) machine (

[yocto] [layerindex-web] Enabled zeus, not working...

I added the zeus branch on the layers.openembedded.org today and it's not showing up and being indexed. Any idea why? On my own personal layer index I did it and it worked fine. So it may be something related to the configuration. Below are the errors from the update log: Oct. 14, 2019, 7:13 p

Re: [yocto] NooB: qemu-native compile error during bitbake core-image-sato

On 14-10-2019 18:54, Ross Burton wrote: On 14/10/2019 17:20, p...@iae.nl wrote: Hello list, First time here so, hi there :-) I'm new to yocto but not new to linux. I'm following the Yocto Project Quick Build manual (https://www.yoctoproject.org/docs/2.7.1/brief-yoctoprojectqs/brief-yoctoproje

Re: [yocto] NooB: qemu-native compile error during bitbake core-image-sato

On 14/10/2019 22:32, myken wrote: For future reference, how could I have found this answer? I searched like crazy but never found any reference that qemu is "old" and my kernel is "new". By recognising where the failure was, knowing that glibc changed, and that qemu needs to be fixed, then fi

Re: [yocto] [layerindex-web] Enabled zeus, not working...

Hi Mark On Tuesday, 15 October 2019 10:21:29 AM NZDT Mark Hatle wrote: > I added the zeus branch on the layers.openembedded.org today and it's not > showing up and being indexed. Any idea why? The bitbake branch wasn't correctly specified - it needed to be set to "1.44" (grabbed from https://wi

Re: [yocto] [layerindex-web] Enabled zeus, not working...

On 10/14/19 5:08 PM, Paul Eggleton wrote: > Hi Mark > > On Tuesday, 15 October 2019 10:21:29 AM NZDT Mark Hatle wrote: >> I added the zeus branch on the layers.openembedded.org today and it's not >> showing up and being indexed. Any idea why? > > The bitbake branch wasn't correctly specified

[yocto] [meta-security][PATCH] suricata: fix compile issue

cp: cannot stat '/./tmp-glibc/work/core2-32-oe-linux/suricata/4.1.5-r0/rules': No such file or directory | WARNING: exit code 1 from a shell command. Signed-off-by: Armin Kuster --- recipes-ids/suricata/suricata_4.1.5.bb | 3 --- 1 file changed, 3 deletions(-) diff --git a/recipes-ids/su

[yocto] [meta-security][PATCH] checksec: add missing rdepends to readelf

update test to check for depends Signed-off-by: Armin Kuster --- lib/oeqa/runtime/cases/checksec.py | 1 + recipes-security/checksec/checksec_2.1.0.bb | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/lib/oeqa/runtime/cases/checksec.py b/lib/oeqa/runtime/cases/check

[yocto] [Yocto] QA cycle report for yocto-3.0_rc2

Hello all, This is the full QA report for YP 3.0 RC2: https://git.yoctoproject.org/cgit/cgit.cgi/yocto-testresults-contrib/tree/3.0_RC2?h=intel-yocto-testresults === Summary No high milestone defects. Two new defects are found in this cycle, mpc8315e-rdb: the stap oeqa test causes O