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

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

Hi Alexander, Thanks for your clarification. 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

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

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

All, The below were the owners of enhancements or bugs closed during the last

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

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

"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

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

This looks good. I am fine with releasing this.

Thanks you, that was the issue...

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

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)

Thanks Matthias, 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

Hi! 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 /

Hi Alexander, Thanks for your advice. Yes, the UBI/UBIFS is used in NAND partitions, I guess you alluded there is no need use the backup, right? If I do need to use a backup, it won't need another

Make the volatiles file name starts with digital. Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-scanners/clamav/clamav_0.101.5.bb | 2 +- 1 file changed, 1 insertion(+), 1

Make the volatiles file name starts with digital. Signed-off-by: Yi Zhao <yi.zhao@...> --- recipes-ids/suricata/suricata_4.1.9.bb | 2 +- 1 file changed, 1 insertion(+), 1

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