Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
OK I would be fine to go with this assertion and perhaps monitor it closely to be classified as intermittent or something one off. From: Richard Purdie Date: Wednesday, April 20, 2022 at 7:19 AM To: Raj, Khem , qa-build-notificat...@lists.yoctoproject.org , yocto@lists.yoctoproject.org Cc: Yocto TSC , Mittal, Anuj Subject: Re: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1) On Wed, 2022-04-20 at 14:14 +, Raj, Khem wrote: > Is the sato-sdk on qemuppc also intermittent issue It doesn't usually happen and works fine in other builds so it is intermittent. Whether it is one of our "known" intermittent issues, I don't know. I couldn't get any real information from the system about why it failed. We have better logging in master. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56825): https://lists.yoctoproject.org/g/yocto/message/56825 Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-raspberrypi][PATCH] bluez-firmware-rpidistro: add compatibility to oe-core/create-spdx
Hi, On Thu, 14 Apr 2022, at 13:36, Davide Gardenal wrote: > Add do_create_spdx dependency to fix error when LICENCE is not found > > Signed-off-by: Davide Gardenal I have pulled this patch in https://github.com/agherzan/meta-raspberrypi/pull/1053. Thanks, Andrei -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56824): https://lists.yoctoproject.org/g/yocto/message/56824 Mute This Topic: https://lists.yoctoproject.org/mt/90463066/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [meta-raspberrypi][PATCH] meta-raspberrypi: u-boot: remove the randundant patch
Hi,
On Wed, 20 Apr 2022, at 03:03, Meng Li wrote:
> This patch had been merged into u-boot upstream. Its commit is
> 29f7d05a347a("dm: core: Move ofdata_to_platdata() call earlier").
> So, remove the randundant patch to avoid building error.
>
> Signed-off-by: Meng Li
I have pulled this patch in
https://github.com/agherzan/meta-raspberrypi/pull/1053.
Thanks,
Andrei
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56823): https://lists.yoctoproject.org/g/yocto/message/56823
Mute This Topic: https://lists.yoctoproject.org/mt/90576652/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
On Wed, 2022-04-20 at 14:14 +, Raj, Khem wrote: > Is the sato-sdk on qemuppc also intermittent issue It doesn't usually happen and works fine in other builds so it is intermittent. Whether it is one of our "known" intermittent issues, I don't know. I couldn't get any real information from the system about why it failed. We have better logging in master. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56822): https://lists.yoctoproject.org/g/yocto/message/56822 Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
Is the sato-sdk on qemuppc also intermittent issue From: t...@lists.yoctoproject.org on behalf of Richard Purdie Sent: Wednesday, April 20, 2022 12:29:29 AM To: qa-build-notificat...@lists.yoctoproject.org ; yocto@lists.yoctoproject.org Cc: Yocto TSC ; Mittal, Anuj Subject: [EXTERNAL] Re: [tsc] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1) On Wed, 2022-04-20 at 06:02 +, Pokybuild User wrote: > A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and > is available at: > > > > https://urldefense.com/v3/__https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1__;!!CQl3mcHX2A!XITvSVzpVXHE-hKopFwPzKrqpC-fi6MhLyNlACbodEIHW7S3PBGSenxMWW9GU4pG$ > > > Build hash information: > > bitbake: d01d8326331cfe59208674cfc53aa26c0028b313 > meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62 > meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20 > meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58 > meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f > meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d > meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e > meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e > oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660 > poky: eee9fba7b4d5d7a268a495688039027390894e6d 3.3.6 built but there were two issues. One was a qemu boot test failure for core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't any, qemu never seemed to start but nothing to indicate why. Since the other tests for ppc passed, I think this is one of our general intermittent problems on ppc and we should ignore it. The other was some valgrind ptest failures. Those are known intermittent issues and I believe also not significant from a release perspective. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56821): https://lists.yoctoproject.org/g/yocto/message/56821 Mute This Topic: https://lists.yoctoproject.org/mt/90584701/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] SRC_URI from AWS codecommit with user and password #yocto
Hi All, I have an application writing in Qt/QML for specific embedded target, The repo for this application is maintained in AWS codecommit which has user and password . How to mentioned in the recipe SRC_URI to fetch from the repo which has user/password. I dont have SSH access for the same. Let me know if you need more details. tried this https://www.yoctoproject.org/pipermail/yocto/2014-April/019135.html no luck. Regards, Vijay -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56820): https://lists.yoctoproject.org/g/yocto/message/56820 Mute This Topic: https://lists.yoctoproject.org/mt/90582260/21656 Mute #yocto:https://lists.yoctoproject.org/g/yocto/mutehashtag/yocto Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] package and booting an initramfs image
Please, read carefully thru this yocto @ thread. https://www.yoctoproject.org/pipermail/yocto/2018-July/041680.html Zee ___ On Tue, Apr 19, 2022 at 8:27 PM wrote: > > I have a need to package my kernel, dtb, and rootfs manually and then boot > this as an initramfs. I'm not sure which files from the deploy/images > directory to use. I see there is an rootfs.cpio.gz file so I'm starting with > that. If I unpack that I see the kernel Image and dtb in the /boot folder and > what appears to be a filesystem in the rest. If I try to boot this as my > kernel in u-boot I get this > Bad Linux ARM64 Image magic! > ** No partition table - mmc 2 ** > ** No partition table - mmc 2 ** > > Does this cpio.gz file have everything I need? How do I boot with it and > enter an initramfs? > > > -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56819): https://lists.yoctoproject.org/g/yocto/message/56819 Mute This Topic: https://lists.yoctoproject.org/mt/90568270/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] IPv6 Autogeneration Not Persisting
I'm trying to auto-generate IPv6 for interfaces on a ZPE Systems device but not able to. It keeps reverting to a value of '1' after a reboot even though the config file clearly has '3'. Anyone run into something similar? root@device:/home/admin# cat /proc/version Linux version 5.4.137-yocto-standard (oe-user@oe-host) (gcc version 9.3.0 (GCC)) #1 SMP PREEMPT Sat Jul 31 06:19:39 UTC 2021 root@device:/home/admin# sysctl net.ipv6.conf.sfp0.addr_gen_mode net.ipv6.conf.sfp0.addr_gen_mode = 1 root@device:/home/admin# cat /etc/sysctl.conf | grep net.ipv6.conf.sfp0.addr_gen_mode net.ipv6.conf.sfp0.addr_gen_mode=3 Nabeel -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56818): https://lists.yoctoproject.org/g/yocto/message/56818 Mute This Topic: https://lists.yoctoproject.org/mt/90581433/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
[yocto] [meta-security][PATCH] Add EROFS support to dm-verity-img class
Add support for the EROFS image, and it's compressed options, to the
dm-verity-img.bbclass setup, theoretically this is a simple addition to
the list of types however there is a quirk in how Poky handles the
filesystems in poky/meta/classes/image_types.bbclass.
Specifically the 'IMAGE_CMD' and 'IMAGE_FSTYPES' use a hyphen, e.g.
erofs-lz4, however in the image_type bbclass the task for that would be
"do_image_erofs_lz4", replacing the hyphen with an underscore.
As the dm-verity-img.bbclass adds a dependency to the wic image creation
on the do_image_* task then it fails as there is no
"do_image_erofs-lz4", so simply replace the hypen with an underscore.
---
classes/dm-verity-img.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/classes/dm-verity-img.bbclass b/classes/dm-verity-img.bbclass
index 16d395b..cc6a7f5 100644
--- a/classes/dm-verity-img.bbclass
+++ b/classes/dm-verity-img.bbclass
@@ -60,7 +60,7 @@ verity_setup() {
veritysetup --data-block-size=1024 --hash-offset=$SIZE format $OUTPUT
$OUTPUT | tail -n +2 | process_verity
}
-VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity"
+VERITY_TYPES = "ext2.verity ext3.verity ext4.verity btrfs.verity erofs.verity
erofs-lz4.verity erofs-lz4hc.verity"
IMAGE_TYPES += "${VERITY_TYPES}"
CONVERSIONTYPES += "verity"
CONVERSION_CMD_verity = "verity_setup ${type}"
@@ -87,6 +87,6 @@ python __anonymous() {
# If we're using wic: we'll have to use partition images and not the rootfs
# source plugin so add the appropriate dependency.
if 'wic' in image_fstypes:
-dep = ' %s:do_image_%s' % (pn, verity_type)
+dep = ' %s:do_image_%s' % (pn, verity_type.replace("-", "_"))
d.appendVarFlag('do_image_wic', 'depends', dep)
}
--
2.26.2
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#56817): https://lists.yoctoproject.org/g/yocto/message/56817
Mute This Topic: https://lists.yoctoproject.org/mt/90580696/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
Re: [yocto] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.3.6.rc1)
On Wed, 2022-04-20 at 06:02 +, Pokybuild User wrote: > A build flagged for QA (yocto-3.3.6.rc1) was completed on the autobuilder and > is available at: > > > https://autobuilder.yocto.io/pub/releases/yocto-3.3.6.rc1 > > > Build hash information: > > bitbake: d01d8326331cfe59208674cfc53aa26c0028b313 > meta-agl: ca53308f8803fb50709b3f17bb1f9e476366bb62 > meta-arm: 878fabbfc720da7d634ed9a2c0e24d4b8845ea20 > meta-aws: 6801abf40bb255a31bce5061c5c6b72f5e2a8f58 > meta-gplv2: 9e119f333cc8f53bd3cf64326f826dbc6ce3db0f > meta-intel: 16bfef2d1e0d0c8c596741d0bbb820541c432f6d > meta-mingw: 422b96cb2b6116442be1f40dfb5bd77447d1219e > meta-openembedded: a970ee45c2335c37041ad1658323481874bb4f0e > oecore: fbbb689c8df7f82644b8a9bc5bb6884bc6516660 > poky: eee9fba7b4d5d7a268a495688039027390894e6d 3.3.6 built but there were two issues. One was a qemu boot test failure for core-image-sato-sdk on qemuppc-alt. I did have a look for logs but there aren't any, qemu never seemed to start but nothing to indicate why. Since the other tests for ppc passed, I think this is one of our general intermittent problems on ppc and we should ignore it. The other was some valgrind ptest failures. Those are known intermittent issues and I believe also not significant from a release perspective. Cheers, Richard -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#56816): https://lists.yoctoproject.org/g/yocto/message/56816 Mute This Topic: https://lists.yoctoproject.org/mt/90579515/21656 Group Owner: yocto+ow...@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
