Date   

Reproducible builds and RPM packages

Anders Montonen
 

Hi,

When going from Zeus to Dunfell, I noticed that all files on the rootfs had timestamps long in the past, which I assume is from reproducible builds now being on by default. While that is a good thing, running “rpm -V” on any installed package now reports that the mtime differs. Is this the intentional behavior?

Regards,
Anders Montonen


Re: Install Yocto image and backup

Richard Weinberger
 

On Tue, Nov 3, 2020 at 10:17 AM JH <jupiter.hce@gmail.com> wrote:
The reason we don't update kernel and rootfs because the size of
kernel and rootfs is too large, it is hard to download 60MB image OTA
via 4G CAT M1. If we are going to change to use 4G CAT1 or higher
speed, I'll use either RAUC or SWUpdate, which one is the most popular
for embedded system using uboot and UBFIS?
You don't need a full download.
In the past I've used binary diffs with great success.

So if the update size is your biggest concern, the tradeoff of
computing and applying
the binary diff might be worth it.

--
Thanks,
//richard


Re: Install Yocto image and backup

JH
 

Hi Alexander,

Thanks for your clarification.

If your kernel and rootfs partition is just one UBIFS in a bigger UBI volume,
then no. Single bad blocks affecting the UBIFS partitions would be handled
by the underlying UBI. You should however consider using ubihealthd or
something similar to become aware of badblocks over time and handle them before it's
too late and you can not boot from the rootfs anymore, especially if it is read only and not
touched for writing in normal operation.
Yes, I use one UBIFS for 4 partitions, RO rootfs, RO kernel, RO DTB
and RW application, no write for RO partitions, that should be safe, I
feel relieved.

your device is somehow connected to a network. So what I suggested was having
two rootfs partitions. One is active and the device boots from it (A), and the
other one acts as inactive (B). When you update, write the new rootfs to the
inactive partition and then just switch over and boot B instead. You might add
a third partition for recovery or factory reset. Only the active partition
would be used in the running system and can still be readonly there.
The reason we don't update kernel and rootfs because the size of
kernel and rootfs is too large, it is hard to download 60MB image OTA
via 4G CAT M1. If we are going to change to use 4G CAT1 or higher
speed, I'll use either RAUC or SWUpdate, which one is the most popular
for embedded system using uboot and UBFIS?

Thank you very much.

Kind regards,

- jupiter


Reminder: Yocto Project Technical Team Meeting @ Monthly from 8am on the first Tuesday (PDT)

Stephen Jolley
 

All,

 

Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (11/3) 

 

Yocto Project Technical Team Meeting: We encourage people attending the meeting to logon and announce themselves on the Yocto Project IRC chancel during the meeting (optional):

Yocto IRC: http://webchat.freenode.net/?channels=#yocto

 

Wiki: https://www.yoctoproject.org/public-virtual-meetings/

 

When            Monthly from 8am to 9am on the first Tuesday Pacific Time

Where           Zoom Meeting: https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09

 

We are tracking the minutes at: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit?pli=1 Please request access if you want to assist in editing them.  The world should have view access.

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


M+ & H bugs with Milestone Movements WW44

Stephen Jolley
 

All,

YP M+ or high bugs which moved to a new milestone in WW44 are listed below:

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

5322

Global DNS fallback mechanism not present in poky distro

kai.kang@...

kai.kang@...

3.2 M4

3.3 M1

 

11766

nobody group added by systemd sysusers.d

randy.macleod@...

yi.zhao@...

3.3

3.3 M1

 

 

yi.zhao@...

yi.zhao@...

3.2 M4

3.3

 

11906

rpmbuild: Can not build packages on qemu target

hongxu.jia@...

hongxu.jia@...

3.2 M4

3.3 M3

 

12279

enhance manifest not found warning

kai.kang@...

kai.kang@...

3.2 M4

3.3 M2

 

12342

lib32-core-image-sato -ctestimage failed due to wrong package names

kai.kang@...

kai.kang@...

3.2 M4

3.3 M1

 

12917

Warnings from nightly-multilib builds (build-deps)

kai.kang@...

kai.kang@...

3.2 M4

3.3 M1

 

13508

Meson detects googletest installed on system

randy.macleod@...

hongxu.jia@...

3.3 M4

3.3 M2

 

 

hongxu.jia@...

hongxu.jia@...

3.2 M4

3.3 M4

 

13631

core-image-full-cmdline qemumips systemd boot failure

kai.kang@...

kai.kang@...

3.2 M4

3.3 M2

 

13841

quilt ptest intermittent failure

randy.macleod@...

joe.slater@...

3.3

3.3 M2

 

 

joe.slater@...

joe.slater@...

3.2 M4

3.3

 

14020

environment-setup script in multilib eSDK doesn't work for multilib variant

liezhi.yang@...

liezhi.yang@...

3.2 M4

3.3 M1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Enhancements/Bugs closed WW44!

Stephen Jolley
 

All,

The below were the owners of enhancements or bugs closed during the last week!

Who

Count

stacy.gaikovaia@...

2

ross@...

2

anuj.mittal@...

1

jay.shen.teoh@...

1

shantanoo_desai@...

1

raj.khem@...

1

steve@...

1

Grand Total

9

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Current high bug count owners for Yocto Project 3.3

Stephen Jolley
 

All,

Below is the list as of top 50 bug owners as of the end of WW44 of who have open medium or higher bugs and enhancements against YP 3.3.   There are 121 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who

Count

richard.purdie@...

31

david.reyna@...

22

ross@...

19

bluelightning@...

19

bruce.ashfield@...

19

JPEWhacker@...

13

sakib.sajal@...

11

timothy.t.orling@...

11

mark.morton@...

11

trevor.gamblin@...

9

akuster808@...

9

kai.kang@...

8

Qi.Chen@...

6

stacy.gaikovaia@...

5

mostthingsweb@...

4

mingli.yu@...

4

rpjday@...

4

randy.macleod@...

4

raj.khem@...

4

idadelm@...

4

chee.yang.lee@...

4

alejandro@...

3

ydirson@...

3

hongxu.jia@...

3

yi.zhao@...

3

jpuhlman@...

2

matthewzmd@...

2

jeanmarie.lemetayer@...

2

saul.wold@...

2

jaewon@...

2

kergoth@...

2

mark.hatle@...

2

michael@...

2

jon.mason@...

2

jbb5044@...

1

joe.slater@...

1

Martin.Jansa@...

1

dl9pf@...

1

liu.ming50@...

1

kexin.hao@...

1

aehs29@...

1

maxime.roussinbelanger@...

1

jason.wessel@...

1

liezhi.yang@...

1

apoorvsangal@...

1

kai.ruhnau@...

1

fede@...

1

anuj.mittal@...

1

ankur.tyagi85@...

1

matt.ranostay@...

1

Grand Total

267

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Yocto Project Newcomer & Unassigned Bugs - Help Needed

Stephen Jolley
 

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#Newcomer_Bugs  Also please review: https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded and how to create a bugzilla account at: https://bugzilla.yoctoproject.org/createaccount.cgi

The idea is these bugs should be straight forward for a person to help work on who doesn't have deep experience with the project.  If anyone can help, please take ownership of the bug and send patches!  If anyone needs help/advice there are people on irc who can likely do so, or some of the more experienced contributors will likely be happy to help too.

 

Also, the triage team meets weekly and does its best to handle the bugs reported into the Bugzilla. The number of people attending that meeting has fallen, as have the number of people available to help fix bugs. One of the things we hear users report is they don't know how to help. We (the triage team) are therefore going to start reporting out the currently 325 unassigned or newcomer bugs.

 

We're hoping people may be able to spare some time now and again to help out with these.  Bugs are split into two types, "true bugs" where things don't work as they should and "enhancements" which are features we'd want to add to the system.  There are also roughly four different "priority" classes right now, “3.2”, “3.3, "3.99" and "Future", the more pressing/urgent issues being in "3.2" and then “3.3”.

 

Please review this link and if a bug is something you would be able to help with either take ownership of the bug, or send me (sjolley.yp.pm@...) an e-mail with the bug number you would like and I will assign it to you (please make sure you have a Bugzilla account).  The list is at: https://wiki.yoctoproject.org/wiki/Bug_Triage_Archive#Unassigned_or_Newcomer_Bugs

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

* Email:              sjolley.yp.pm@...

 


Re: #yocto -zeus #yocto

Konrad Weihmann
 

"github.com[0: 140.82.114.4]: errno=Connection timed out" indicates either a temporary issue with github (unlikely) or with your network setup.
Already tried a different network path from your dev-machine to the inet? Just to rule out any proxy/MITM instances.

It's also likely that git port is somehow blocked in your setup - try changing "protocol=git" to "protocol=https" in the recipe and check if it is working.
And if have a talk with your IT or internet provider afterwards.

On 02.11.20 21:31, Monsees, Steven C (US) via lists.yoctoproject.org wrote:
github.com[0: 140.82.114.4]: errno=Connection timed out


#yocto -zeus #yocto

Monsees, Steven C (US)
 

 

Attempting to move to zeus…

Build with zeus 3.0.4, using “bitbake –k”, all other downloads for kernel/image were successful…

 

Can someone tell why I am getting the following 4 errors and how best to resolve ?

 

 

Loading cache: 100% |###############################################################################################| Time: 0:00:00

Loaded 3642 entries from dependency cache.

NOTE: Resolving any missing task queue dependencies

 

Build Configuration:

BB_VERSION           = "1.44.0"

BUILD_SYS            = "x86_64-linux"

NATIVELSBSTRING      = "rhel-7.8"

TARGET_SYS           = "x86_64-poky-linux"

MACHINE              = "sbcb-default"

DISTRO               = "limws"

DISTRO_VERSION       = "3.0.4"

TUNE_FEATURES        = "m64 corei7"

TARGET_FPU           = ""

meta                

meta-poky            = "my_yocto_3.0.4:f2eb22a8783f1eecf99bd4042695bab920eed00e"

meta-perl           

meta-python         

meta-filesystems    

meta-networking     

meta-initramfs      

meta-oe              = "zeus:2b5dd1eb81cd08bc065bc76125f2856e9383e98b"

meta-intel           = "zeus:d9942d4c3a710406b051852de7232db03c297f4e"

meta-intel           = "v2019.02:f635a364c55f1fb12519aff54924a0a5b947091e"

 

Initialising tasks: 100% |##########################################################################################| Time: 0:00:03

Sstate summary: Wanted 316 Found 296 Missed 20 Current 1793 (93% match, 99% complete)

NOTE: Executing Tasks

NOTE: Setscene tasks completed

WARNING: ovmf-native-edk2-stable201905-r0 do_fetch: Failed to fetch URL gitsm://github.com/tianocore/edk2.git;branch=master;protocol=git, attempting MIRRORS if available

ERROR: ovmf-native-edk2-stable201905-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-3LFubab4k2,guid=5c19cfb5af3a9248c3a7a8bb5f7eedd1"; export SSH_AGENT_PID="22978"; export SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export PATH="/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts/native-intercept:/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/usr/bin/x86_64-linux:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/usr/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/recipe-sysroot-native/bin:/disk0/scratch/smonsees/yocto/workspace_3/poky/bitbake/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/hosttools"; export HOME="/ede/smonsees"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/tianocore/edk2.git /disk0/scratch/smonsees/yocto/workspace_3/downloads/intel/git2/github.com.tianocore.edk2.git --progress failed with exit code 128, output:

Cloning into bare repository '/disk0/scratch/smonsees/yocto/workspace_3/downloads/intel/git2/github.com.tianocore.edk2.git'...

 

fatal: unable to connect to github.com:

github.com[0: 140.82.114.4]: errno=Connection timed out

 

 

ERROR: ovmf-native-edk2-stable201905-r0 do_fetch: Fetcher failure for URL: 'gitsm://github.com/tianocore/edk2.git;branch=master;protocol=git'. Unable to fetch URL from any source.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/x86_64-linux/ovmf-native/edk2-stable201905-r0/temp/log.do_fetch.1158

ERROR: Task (virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch) failed with exit code '1'

WARNING: ovmf-edk2-stable201905-r0 do_fetch: Failed to fetch URL gitsm://github.com/tianocore/edk2.git;branch=master;protocol=git, attempting MIRRORS if available

ERROR: ovmf-edk2-stable201905-r0 do_fetch: Fetcher failure: Fetch command export PSEUDO_DISABLED=1; unset _PYTHON_SYSCONFIGDATA_NAME; export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-3LFubab4k2,guid=5c19cfb5af3a9248c3a7a8bb5f7eedd1"; export SSH_AGENT_PID="22978"; export SSH_AUTH_SOCK="/run/user/11588/keyring/ssh"; export PATH="/disk0/scratch/smonsees/yocto/workspace_3/poky/scripts:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot-native/usr/bin/x86_64-poky-linux:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot/usr/bin/crossscripts:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot-native/usr/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot-native/usr/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot-native/sbin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/recipe-sysroot-native/bin:/disk0/scratch/smonsees/yocto/workspace_3/poky/bitbake/bin:/disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/hosttools"; export HOME="/ede/smonsees"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://github.com/tianocore/edk2.git /disk0/scratch/smonsees/yocto/workspace_3/downloads/intel/git2/github.com.tianocore.edk2.git --progress failed with exit code 128, output:

Cloning into bare repository '/disk0/scratch/smonsees/yocto/workspace_3/downloads/intel/git2/github.com.tianocore.edk2.git'...

 

fatal: unable to connect to github.com:

github.com[0: 140.82.112.3]: errno=Connection timed out

 

 

ERROR: ovmf-edk2-stable201905-r0 do_fetch: Fetcher failure for URL: 'gitsm://github.com/tianocore/edk2.git;branch=master;protocol=git'. Unable to fetch URL from any source.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_3/meta-bae/meta-limws/builds/sbcb-default/tmp/work/corei7-64-poky-linux/ovmf/edk2-stable201905-r0/temp/log.do_fetch.1182

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch) failed with exit code '1'

NOTE: Tasks Summary: Attempted 5885 tasks of which 5868 didn't need to be rerun and 2 failed.

 

Summary: 2 tasks failed:

  virtual:native:/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch

  /disk0/scratch/smonsees/yocto/workspace_3/poky/meta/recipes-core/ovmf/ovmf_git.bb:do_fetch

Summary: There were 3 WARNING messages shown.

Summary: There were 4 ERROR messages shown, returning a non-zero exit code.

 


Re: QA notification for completed autobuilder build (yocto-3.2.rc2)

Khem Raj
 

On Sun, Nov 1, 2020 at 8:18 PM Sangeeta Jain <sangeeta.jain@intel.com> wrote:

Hello all,

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

======= Summary ========
No new defects are found.
No high milestone defects.

Bugs verified:

BUG id:14106 - [QA 3.2 RC1] failure in ptest : glib-2.0.glib/gdatetime.test
Verified Fixed.

Existing bugs observed in this release:

BUG id:14051 - [QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind
Updated with 17 ptests passed, 1 ptest still failing
No new failures.


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


This looks good. I am fine with releasing this.

Thanks,
Sangeeta

-----Original Message-----
From: Pokybuild User <pokybuild@fedora30-ty-1.yocto.io>
Sent: Tuesday, 27 October, 2020 4:15 PM
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.2.rc2)


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


https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc2


Build hash information:

bitbake: fec2b85689bba1d26ad6f376bc11cc29bb27cbe5
meta-arm: 2d3ded053ae0774b9c7254bdc084451438b2150a
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 4ee7bc0ab408db7388374e86920ffa378b7b4535
meta-kernel: dbf8bdfa6683404e5071feb47ef6aa347cab1b01
meta-mingw: d2809d7c93bdb46014e1f8b3b0a4f42030078905
oecore: d3114ca369792201a5316c1ede29eb72f0868d35
poky: 5d75168a13d00253460020e536b2a87833ec67d2



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




Re: #yocto #yocto

Monsees, Steven C (US)
 


Thanks you, that was the issue...


Re: #yocto #yocto

Martin Jansa
 

your 2nd meta-intel probably still has:
LICENSE_PATH += "${LAYERDIR}/custom-licenses"
in layer.conf without having this directory included in the layer?

On Mon, Nov 2, 2020 at 1:37 PM Monsees, Steven C (US) via lists.yoctoproject.org <steven.monsees=baesystems.com@...> wrote:

I am not sure I am following ...

#1 is the actual package being built, #2 is the mods to the recipes for the image I am building...

    (1)    ./workspace_1/poky/../meta-intel

    (2)    ./workspace_1/poky/../meta-1/meta-2/meta-intel
These directories share the same name, but the local.conf for #2 requires a unique BBFILE_COLLECTIONS name now ?

If I change the BBFILE_COLLECTIONS name to be unique,  I see the following error:

--- Starting bitbake server pid 12022 at 2020-11-02 07:19:06.133802 ---
ERROR: Unable to parse Var <AVAILABLE_LICENSES[:=]>
Traceback (most recent call last):
  File "Var <AVAILABLE_LICENSES[:=]>", line 1, in <module>
  File "/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/license.bbclass", line 275, in available_licenses(d=<bb.data_smart.DataSmart object at 0x7fc921cbdda0>):
         for lic_dir in lic_dirs:
    >        licenses += os.listdir(lic_dir)
    
bb.data_smart.ExpansionError: Failure expanding variable AVAILABLE_LICENSES[:=], expression was ${@' '.join(available_licenses(d))} which triggered exception FileNotFoundError: [Errno 2] No such file or directory: '/disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/meta-intel/custom-licenses'



 





Re: #yocto #yocto

Monsees, Steven C (US)
 


I am not sure I am following ...

#1 is the actual package being built, #2 is the mods to the recipes for the image I am building...

    (1)    ./workspace_1/poky/../meta-intel

    (2)    ./workspace_1/poky/../meta-1/meta-2/meta-intel
These directories share the same name, but the local.conf for #2 requires a unique BBFILE_COLLECTIONS name now ?

If I change the BBFILE_COLLECTIONS name to be unique,  I see the following error:

--- Starting bitbake server pid 12022 at 2020-11-02 07:19:06.133802 ---
ERROR: Unable to parse Var <AVAILABLE_LICENSES[:=]>
Traceback (most recent call last):
  File "Var <AVAILABLE_LICENSES[:=]>", line 1, in <module>
  File "/disk0/scratch/smonsees/yocto/workspace_3/poky/meta/classes/license.bbclass", line 275, in available_licenses(d=<bb.data_smart.DataSmart object at 0x7fc921cbdda0>):
         for lic_dir in lic_dirs:
    >        licenses += os.listdir(lic_dir)
    
bb.data_smart.ExpansionError: Failure expanding variable AVAILABLE_LICENSES[:=], expression was ${@' '.join(available_licenses(d))} which triggered exception FileNotFoundError: [Errno 2] No such file or directory: '/disk0/scratch/smonsees/yocto/workspace_3/poky/../meta-bae/meta-limws/meta-intel/custom-licenses'



 


Re: Install Yocto image and backup

JH
 

Thanks Matthias,

The A/B partitioning is very common and I would argue, it is the
simplest way if you want you OTA Update to be safe in regards of any
errors (user unplugging etc.) that may happen during write / switching
to new software. If you can spare the extra partitions on your NAND, my
advice would be to do it exactly that way, and use a common tool for
that (i.e. swupate, rauc, ... ).
We don't have OTA update for RO kernel and rootfs yet, I'll take the
advice for running OTA A/B partitioning when the requirement is
coming.

Thank you all for your kind responses.

Kind regards,

- jupiter


Re: Install Yocto image and backup

Matthias Schoepfer
 

Hi!

On 11/2/20 10:16 AM, JH wrote:
If I do need to use a backup, it won't need another NAND chip, it will
be another UBI/UBIFS partition. But I would like as simple as possible
if no backup is a common practice.
The A/B partitioning is very common and I would argue, it is the simplest way if you want you OTA Update to be safe in regards of any errors (user unplugging etc.) that may happen during write / switching to new software. If you can spare the extra partitions on your NAND, my advice would be to do it exactly that way, and use a common tool for that (i.e. swupate, rauc, ... ).

Regards,

  Matthias


Re: Install Yocto image and backup

JH
 

Hi Alexander,

Thanks for your advice.

In my opinion two things are common practice:

1) Using a layer on top of raw NAND, like UBI/UBIFS nowadays, so bad blocks
can be handled properly in a layer below your rootfs.
Yes, the UBI/UBIFS is used in NAND partitions, I guess you alluded
there is no need use the backup, right?

2) Using an A/B scheme for updating and using a well tested framework for
that (instead of self written shell scripts). You don't need another NAND chip
for that, just multiple partitions. You can still have your kernel/rootfs read-only at runtime.
If I do need to use a backup, it won't need another NAND chip, it will
be another UBI/UBIFS partition. But I would like as simple as possible
if no backup is a common practice.

Thank you very much.

Kind regards,

- jupiter


[meta-security][PATCH 2/2] clamav: unify volatiles file name

Yi Zhao
 

Make the volatiles file name starts with digital.

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
recipes-scanners/clamav/clamav_0.101.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-scanners/clamav/clamav_0.101.5.bb b/recipes-scanners/clamav/clamav_0.101.5.bb
index 47fbae4..7dad263 100644
--- a/recipes-scanners/clamav/clamav_0.101.5.bb
+++ b/recipes-scanners/clamav/clamav_0.101.5.bb
@@ -86,7 +86,7 @@ do_install_append_class-target () {

install -m 644 ${WORKDIR}/clamd.conf ${D}/${sysconfdir}
install -m 644 ${WORKDIR}/freshclam.conf ${D}/${sysconfdir}
- install -m 0644 ${WORKDIR}/volatiles.03_clamav ${D}${sysconfdir}/default/volatiles/volatiles.03_clamav
+ install -m 0644 ${WORKDIR}/volatiles.03_clamav ${D}${sysconfdir}/default/volatiles/03_clamav
sed -i -e 's#${STAGING_DIR_HOST}##g' ${D}${libdir}/pkgconfig/libclamav.pc
rm ${D}/${libdir}/libclamav.so
if [ "${INSTALL_CLAMAV_CVD}" = "1" ]; then
--
2.17.1


[meta-security][PATCH 1/2] suricata: unify volatiles file name

Yi Zhao
 

Make the volatiles file name starts with digital.

Signed-off-by: Yi Zhao <yi.zhao@windriver.com>
---
recipes-ids/suricata/suricata_4.1.9.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-ids/suricata/suricata_4.1.9.bb b/recipes-ids/suricata/suricata_4.1.9.bb
index 135871c..3f7beaa 100644
--- a/recipes-ids/suricata/suricata_4.1.9.bb
+++ b/recipes-ids/suricata/suricata_4.1.9.bb
@@ -55,7 +55,7 @@ do_install_append () {
oe_runmake install-rules DESTDIR=${D}

install -d ${D}${sysconfdir}/suricata ${D}${sysconfdir}/default/volatiles
- install -m 0644 ${WORKDIR}/volatiles.03_suricata ${D}${sysconfdir}/default/volatiles/volatiles.03_suricata
+ install -m 0644 ${WORKDIR}/volatiles.03_suricata ${D}${sysconfdir}/default/volatiles/03_suricata

install -m 0644 ${S}/threshold.config ${D}${sysconfdir}/suricata

--
2.17.1


Re: QA notification for completed autobuilder build (yocto-3.2.rc2)

Sangeeta Jain
 

Hello all,

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

======= Summary ========
No new defects are found.
No high milestone defects.

Bugs verified:

BUG id:14106 - [QA 3.2 RC1] failure in ptest : glib-2.0.glib/gdatetime.test
Verified Fixed.

Existing bugs observed in this release:

BUG id:14051 - [QA 3.2 M3 RC1] failure in ptest : valgrind.drd and valgrind.helgrind
Updated with 17 ptests passed, 1 ptest still failing
No new failures.


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


Thanks,
Sangeeta

-----Original Message-----
From: Pokybuild User <pokybuild@fedora30-ty-1.yocto.io>
Sent: Tuesday, 27 October, 2020 4:15 PM
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.2.rc2)


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


https://autobuilder.yocto.io/pub/releases/yocto-3.2.rc2


Build hash information:

bitbake: fec2b85689bba1d26ad6f376bc11cc29bb27cbe5
meta-arm: 2d3ded053ae0774b9c7254bdc084451438b2150a
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: 4ee7bc0ab408db7388374e86920ffa378b7b4535
meta-kernel: dbf8bdfa6683404e5071feb47ef6aa347cab1b01
meta-mingw: d2809d7c93bdb46014e1f8b3b0a4f42030078905
oecore: d3114ca369792201a5316c1ede29eb72f0868d35
poky: 5d75168a13d00253460020e536b2a87833ec67d2



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


1241 - 1260 of 52467