Date   

M+ & H bugs with Milestone Movements WW04

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13888

Toaster is not starting for Django-3

randy.macleod@...

david.reyna@...

3.1.5

3.1.6

 

14031

Exception: KeyError: 'getpwuid(): uid not found: 1000' after 3.1.1 to 3.1.2 update

randy.macleod@...

steve@...

3.1.5

3.1.6

 

14114

Implement proper sphinx docs publishing

randy.macleod@...

nicolas.dechesne@...

3.3 M2

3.3 M3

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW04!

Stephen Jolley
 

All,

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

Who

Count

anuj.mittal@...

2

akuster808@...

1

richard.purdie@...

1

david.reyna@...

1

Grand Total

5

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 WW04 of who have open medium or higher bugs and enhancements against YP 3.3.   There are 67 possible work days left until the final release candidates for YP 3.3 needs to be released.

Who

Count

richard.purdie@...

35

ross@...

26

david.reyna@...

21

bluelightning@...

18

bruce.ashfield@...

15

akuster808@...

12

timothy.t.orling@...

12

mark.morton@...

11

JPEWhacker@...

11

kai.kang@...

10

sakib.sajal@...

10

trevor.gamblin@...

9

Qi.Chen@...

6

randy.macleod@...

5

raj.khem@...

5

mingli.yu@...

5

hongxu.jia@...

5

yi.zhao@...

4

idadelm@...

4

chee.yang.lee@...

4

stacygaikovaia@...

4

alejandro@...

3

mostthingsweb@...

3

ydirson@...

2

matthewzmd@...

2

jeanmarie.lemetayer@...

2

pokylinux@...

2

saul.wold@...

2

nicolas.dechesne@...

2

jaewon@...

2

anuj.mittal@...

2

yifan.yu@...

2

sangeeta.jain@...

2

dorindabassey@...

1

aehs29@...

1

mister_rs@...

1

kamensky@...

1

kergoth@...

1

jon.mason@...

1

shachar@...

1

pbarker@...

1

liezhi.yang@...

1

dl9pf@...

1

Martin.Jansa@...

1

twoerner@...

1

kexin.hao@...

1

joe.slater@...

1

mhalstead@...

1

matt.hoosier@...

1

mark.hatle@...

1

mshah@...

1

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Yocto Project Status WW04`21

Stephen Jolley
 

Current Dev Position: YP 3.3 M3 development

Next Deadline: 1st March 2021 YP 3.3 M3 build 

 

Next Team Meetings:

 

Key Status/Updates:

  • YP 3.3 M2 is currently in QA and we are now in the final development milestone M3 for 3.3
  • YP 3.1.5 was released.
  • We have a new simple system to help with the SWAT process, “SwatBot”, https://swatbot.yoctoproject.org/ . This aims to simplify the SWAT process by listing the exact list of issues which need to be triaged and tracks the resolutions. It will mainly be of use to anyone participating in the SWAT process but mentioned here as people may see mention of it.
  • Intermittent autobuilder issues continue to occur and with more invasive changes and higher rebuild rates, the numbers are increasing again. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT
  • An interesting idea came up in discussion with Kernel CI about potentially sharing YP autobuilder results into their system. There is an open bug for anyone interested in helping with or tracking this: https://bugzilla.yoctoproject.org/show_bug.cgi?id=14196. It could also be an interesting use case for generating an SBOM with our output artefacts.

 

Ways to contribute:

 

YP 3.3 Milestone Dates:

  • YP 3.3 M2 built and in QA
  • YP 3.3 M2 Release date 2021/01/29
  • YP 3.3 M3 build date 2021/03/01
  • YP 3.3 M3 Release date 2021/03/12
  • YP 3.3 M4 build date 2021/04/05
  • YP 3.3 M4 Release date 2021/04/30

 

Planned upcoming dot releases:

  • YP 3.1.5 was released.
  • YP 3.2.2 build date 2021/02/08
  • YP 3.2.2 release date 2021/02/19
  • YP 3.1.6 build date 2021/02/22
  • YP 3.1.6 release date 2021/03/05
  • YP 3.1.7 build date 2021/03/22
  • YP 3.1.7 release date 2021/04/02

 

Tracking Metrics:

 

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:

https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!]

 

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 337 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@...

 


[meta-rockchip][PATCH v2] rock-pi-4: Split our variant machines

Joshua Watt
 

Splits out the three variants of the rock-pi-4 (A, B & C) into their own
machines. Unfortunately, it is not possible to have a single machine
that works for all three, as there isn't any known ways for the
bootloader to distinguish them. The old rock-pi-4 machine is kept around
for use with older kernels

Signed-off-by: Joshua Watt <JPEWhacker@gmail.com>
---
conf/machine/include/rk3399.inc | 2 +-
conf/machine/include/rock-pi-4.inc | 22 ++++++++++++++++++++++
conf/machine/rock-pi-4.conf | 22 ++++------------------
conf/machine/rock-pi-4a.conf | 11 +++++++++++
conf/machine/rock-pi-4b.conf | 11 +++++++++++
conf/machine/rock-pi-4c.conf | 11 +++++++++++
6 files changed, 60 insertions(+), 19 deletions(-)
create mode 100644 conf/machine/include/rock-pi-4.inc
create mode 100644 conf/machine/rock-pi-4a.conf
create mode 100644 conf/machine/rock-pi-4b.conf
create mode 100644 conf/machine/rock-pi-4c.conf

diff --git a/conf/machine/include/rk3399.inc b/conf/machine/include/rk3399.inc
index 4019988..f6b7826 100644
--- a/conf/machine/include/rk3399.inc
+++ b/conf/machine/include/rk3399.inc
@@ -5,8 +5,8 @@ SOC_FAMILY = "rk3399"

DEFAULTTUNE ?= "cortexa72-cortexa53-crypto"

-require conf/machine/include/tune-cortexa72-cortexa53.inc
require conf/machine/include/soc-family.inc
+require conf/machine/include/tune-cortexa72-cortexa53.inc
require conf/machine/include/rockchip-defaults.inc

KBUILD_DEFCONFIG ?= "defconfig"
diff --git a/conf/machine/include/rock-pi-4.inc b/conf/machine/include/rock-pi-4.inc
new file mode 100644
index 0000000..9c21084
--- /dev/null
+++ b/conf/machine/include/rock-pi-4.inc
@@ -0,0 +1,22 @@
+# Add a common override for all Rock Pi 4 machines
+MACHINEOVERRIDES =. "rock-pi-4:"
+
+require conf/machine/include/rk3399.inc
+
+RK_BOOT_DEVICE = "mmcblk1"
+WKS_FILE ?= "rock-pi-4.wks"
+IMAGE_FSTYPES += "wic wic.bmap"
+
+WKS_FILE_DEPENDS ?= " \
+ mtools-native \
+ dosfstools-native \
+ virtual/bootloader \
+ virtual/kernel \
+ "
+IMAGE_BOOT_FILES ?= "\
+ ${KERNEL_IMAGETYPE} \
+ "
+
+SERIAL_CONSOLES = "1500000;ttyS2"
+
+MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
diff --git a/conf/machine/rock-pi-4.conf b/conf/machine/rock-pi-4.conf
index 5231abf..23bbfc3 100644
--- a/conf/machine/rock-pi-4.conf
+++ b/conf/machine/rock-pi-4.conf
@@ -4,26 +4,12 @@
#@TYPE: Machine
#@NAME: Rock Pi 4 RK3399
#@DESCRIPTION: Rock Pi 4 is a Raspberry Pi 4 Alternative based on Rockchip RK3399 Processor.
+#
+# NOTE: This machine is for Kernels before 5.10. If you are using an newer kernel
+# see rock-pi-4{a,b,c}.conf

-require conf/machine/include/rk3399.inc
+require conf/machine/include/rock-pi-4.inc

KERNEL_DEVICETREE = "rockchip/rk3399-rock-pi-4.dtb"
UBOOT_MACHINE = "rock-pi-4-rk3399_defconfig"

-RK_BOOT_DEVICE = "mmcblk1"
-WKS_FILE ?= "rock-pi-4.wks"
-IMAGE_FSTYPES += "wic wic.bmap"
-
-WKS_FILE_DEPENDS ?= " \
- mtools-native \
- dosfstools-native \
- virtual/bootloader \
- virtual/kernel \
- "
-IMAGE_BOOT_FILES ?= "\
- ${KERNEL_IMAGETYPE} \
- "
-
-SERIAL_CONSOLES = "1500000;ttyS2"
-
-MACHINE_EXTRA_RRECOMMENDS += "kernel-modules"
diff --git a/conf/machine/rock-pi-4a.conf b/conf/machine/rock-pi-4a.conf
new file mode 100644
index 0000000..abe2336
--- /dev/null
+++ b/conf/machine/rock-pi-4a.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: Rock Pi 4A RK3399
+#@DESCRIPTION: Rock Pi 4 is a Raspberry Pi 4 Alternative based on Rockchip RK3399 Processor.
+#
+# NOTE: This machine is for Kernel 5.10 and later. If you are using an older
+# kernel, see rock-pi-4.conf
+
+require conf/machine/include/rock-pi-4.inc
+
+KERNEL_DEVICETREE = "rockchip/rk3399-rock-pi-4a.dtb"
+UBOOT_MACHINE = "rock-pi-4-rk3399_defconfig"
diff --git a/conf/machine/rock-pi-4b.conf b/conf/machine/rock-pi-4b.conf
new file mode 100644
index 0000000..587fb32
--- /dev/null
+++ b/conf/machine/rock-pi-4b.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: Rock Pi 4B RK3399
+#@DESCRIPTION: Rock Pi 4 is a Raspberry Pi 4 Alternative based on Rockchip RK3399 Processor.
+#
+# NOTE: This machine is for Kernel 5.10 and later. If you are using an older
+# kernel, see rock-pi-4.conf
+
+require conf/machine/include/rock-pi-4.inc
+
+KERNEL_DEVICETREE = "rockchip/rk3399-rock-pi-4b.dtb"
+UBOOT_MACHINE = "rock-pi-4-rk3399_defconfig"
diff --git a/conf/machine/rock-pi-4c.conf b/conf/machine/rock-pi-4c.conf
new file mode 100644
index 0000000..3af26ff
--- /dev/null
+++ b/conf/machine/rock-pi-4c.conf
@@ -0,0 +1,11 @@
+#@TYPE: Machine
+#@NAME: Rock Pi 4C RK3399
+#@DESCRIPTION: Rock Pi 4 is a Raspberry Pi 4 Alternative based on Rockchip RK3399 Processor.
+#
+# NOTE: This machine is for Kernel 5.10 and later. If you are using an older
+# kernel, see rock-pi-4.conf
+
+require conf/machine/include/rock-pi-4.inc
+
+KERNEL_DEVICETREE = "rockchip/rk3399-rock-pi-4c.dtb"
+UBOOT_MACHINE = "rock-pi-4c-rk3399_defconfig"
--
2.30.0


Re: [meta-rockchip][PATCH] rock-pi-4: Split our variant machinesy

Joshua Watt
 

On Mon, Jan 25, 2021 at 5:15 PM Trevor Woerner <twoerner@gmail.com> wrote:

Is there any way to make this work with both new (4.10, -dev, -tiny, -rt) and
old (5.4) kernels? What if we left the old rock-pi-4 MACHINE for the 5.4
kernel and required one of the new ones for 5.10?
Ya, we can keep the old machine around for the old kernels


OpenEmbedded Happy Hour January 27 5pm/1700 UTC

Denys Dmytriyenko
 

Hi,

Just a reminder about our upcoming OpenEmbedded Happy Hour on January 27 for
Europe/US timezones @ 1700/5pm UTC (12pm ET):

https://www.openembedded.org/wiki/Calendar
https://www.timeanddate.com/worldclock/fixedtime.html?msg=OpenEmbedded+Happy+Hour+January+27&iso=20210127T17

--
Regards,
Denys Dmytriyenko <denis@denix.org>
PGP: 0x420902729A92C964 - https://denix.org/0x420902729A92C964
Fingerprint: 25FC E4A5 8A72 2F69 1186 6D76 4209 0272 9A92 C964


Re: [meta-rockchip][PATCH] rock-pi-4: Split our variant machinesy

Trevor Woerner
 

Is there any way to make this work with both new (4.10, -dev, -tiny, -rt) and
old (5.4) kernels? What if we left the old rock-pi-4 MACHINE for the 5.4
kernel and required one of the new ones for 5.10?


Re: [meta-rockchip][PATCH] linux-yocto: Remove Rock Pi 4 patch for serial

Trevor Woerner
 

On Mon 2021-01-25 @ 04:42:35 PM, Joshua Watt wrote:

On 1/25/21 4:34 PM, Trevor Woerner wrote:
On Sat 2021-01-23 @ 03:05:25 PM, Joshua Watt wrote:
Upstream OE Core has moved to Kernel 5.10 which fixed this problem, so
remove the patch for 5.8
Thanks, I've already pushed a patch for this one.
Ya, I saw that. We should probably remove the .patch file also.
D'oh! Thanks.


Re: [meta-rockchip][PATCH] linux-yocto: Remove Rock Pi 4 patch for serial

Joshua Watt
 

On 1/25/21 4:34 PM, Trevor Woerner wrote:
On Sat 2021-01-23 @ 03:05:25 PM, Joshua Watt wrote:
Upstream OE Core has moved to Kernel 5.10 which fixed this problem, so
remove the patch for 5.8
Thanks, I've already pushed a patch for this one.
Ya, I saw that. We should probably remove the .patch file also.


Re: [meta-rockchip][PATCH] linux-yocto: Remove Rock Pi 4 patch for serial

Trevor Woerner
 

On Sat 2021-01-23 @ 03:05:25 PM, Joshua Watt wrote:
Upstream OE Core has moved to Kernel 5.10 which fixed this problem, so
remove the patch for 5.8
Thanks, I've already pushed a patch for this one.


Re: [meta-tensorflow][PATCH 8/25] tensorflow-estimator: 1.13 -> 2.4

Randy MacLeod
 

On 2021-01-25 1:57 p.m., Belisko Marek wrote:
Hi Randy,
On Thu, Jan 7, 2021 at 9:47 PM Randy MacLeod
<randy.macleod@windriver.com> wrote:

On 2021-01-07 1:47 p.m., Belisko Marek wrote:
Marek,
Does this happen if you use the master branch?
Yes this comes from master branch.
Hi Marek,

Is it:
A) Comes from master and is a problem on dunfell or
B) it is reproducible on the master branch?

Given that you said:
> I'm getting issue when building tensorflow-estimator (I add small
> changes to be able to build this patches on top of dunfell) ...

I suspect it's A only. Right?

What are your small changes.

Hongxu may take a quick look but we generally can't afford to
investigate all combinations of recipe/branchs as I'm sure you
can appreciate.
I have done some small changes and now have tensorflow from master
working on top of dunfell.
Hi Marek,

That's good to hear!

Would you be interested in sharing changes
back and integrate to repo?
I suspect it's not much work to merge the fixes
and maintain the branch, but I'll leave it up to Hongxu.

../Randy



If you can reproduce the error on master without or even with your
changes then that's a different story.

Good luck and Happy New Year!

--
# Randy MacLeod
# Wind River Linux
Thanks and BR,
marek

--
# Randy MacLeod
# Wind River Linux


Re: [meta-tensorflow][PATCH 8/25] tensorflow-estimator: 1.13 -> 2.4

Marek Belisko
 

Hi Randy,

On Thu, Jan 7, 2021 at 9:47 PM Randy MacLeod
<randy.macleod@windriver.com> wrote:

On 2021-01-07 1:47 p.m., Belisko Marek wrote:
Marek,
Does this happen if you use the master branch?
Yes this comes from master branch.
Hi Marek,

Is it:
A) Comes from master and is a problem on dunfell or
B) it is reproducible on the master branch?

Given that you said:
> I'm getting issue when building tensorflow-estimator (I add small
> changes to be able to build this patches on top of dunfell) ...

I suspect it's A only. Right?

What are your small changes.

Hongxu may take a quick look but we generally can't afford to
investigate all combinations of recipe/branchs as I'm sure you
can appreciate.
I have done some small changes and now have tensorflow from master
working on top of dunfell. Would you be interested in sharing changes
back and integrate to repo?

If you can reproduce the error on master without or even with your
changes then that's a different story.

Good luck and Happy New Year!

--
# Randy MacLeod
# Wind River Linux
Thanks and BR,

marek


#yocto #armv6 #raspberrypi #neon #raspberrypi #neon #yocto #armv6

safouane maaloul
 

Hello folks, i am trying to compile my image but we could see that i am missing neon fpu in my image. I can't use this feature because i have a raspberry pi zero w and i have armv6 on this raspberrypi. I noticed that we don't the neon feature on armv6 so i wish that you can help me to find a work around this problem. Thanks in advance.

Best regards,

Safouane

this is an exemple of the error i get when i run the build :

| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:12:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/recipe-sysroot-native/usr/lib/arm-poky-linux-gnueabi/gcc/arm-poky-linux-gnueabi/10.2.0/include/arm_neon.h:10373:1: error: inlining failed in call to 'always_inline' 'vld1q_s32': target specific option mismatch
| 10373 | vld1q_s32 (const int32_t * __a)
|       | ^~~~~~~~~
| In file included from /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/encoder/arm/neon/quantize_neon.c:20:
| /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/git/av1/common/arm/mem_neon.h:525:24: note: called from here
|   525 |   const int32x4_t v0 = vld1q_s32(buf);
|       |                        ^~~~~~~~~~~~~~
| ninja: build stopped: subcommand failed.
| WARNING: /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.11087:155 exit 1 from 'eval ${DESTDIR:+DESTDIR=${DESTDIR} }VERBOSE=1 cmake --build '/workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/build' "$@" -- ${EXTRA_OECMAKE_BUILD}'
| WARNING: Backtrace (BB generated script):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.11087, line 155
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.11087, line 149
|       #3: do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.11087, line 144
|       #4: main, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/tmp/work/arm1176jzfshf-vfp-poky-linux-gnueabi/aom/2.0.0-r0/temp/run.do_compile.11087, line 168
|
| Backtrace (metadata-relative locations):
|       #1: cmake_runcmake_build, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 205
|       #2: cmake_do_compile, /workdir/tep-cam-rpi-yocto/rpi-build-gatesgarth/../../poky/meta/classes/cmake.bbclass, line 209
|       #3: do_compile, autogenerated, line 2


Re: insmod - huawei E3372h kernel module

Zoltan Kerenyi Nagy
 

Hi,

If I intentionally typo in the defconfig file:

USB_NET_HUAWEI_CDC_NCM_cat=y
USB_NET_DRIVERS=y
USB_USBNET=y

The bitbake -f linux command doesn't recognize the change. It means to me that any change in this will not have an effect.

--
Zolee


Re: Points to consider while moving to new yocto versions

Robert Berger
 

Hi,

My comments are in-line

On 25/01/2021 10:07, amaya jindal wrote:
Hi All,
We are planning to move to New yocto from current one that is krogoth yocto to some updated one.
I would consider it "best practice" to somewhat try to stay up to date with recent yocto versions and plan for this from the beginning of your project.

What I mean is to have a "stable release" and a "next release" which is being used in your nightly builds and tests.

This will make it significantly easier to make version upgrades.

We are not thinking to move to gates-garth or some other major release but the releases than can have easily support for arm.
I am not sure what you mean by that?

Which versions make it easier/more difficult to support arm?

It's more a question of which chip/kernel/boot loader,...

Please support and help.
Points need to take care to port to new yocto version.
Ssince you use a completely outdated and end of life version[1] it might require quite some effort to update, but through pain we learn ;)

[1] https://wiki.yoctoproject.org/wiki/Releases

Which chip do you use?

Is it supported by an upstream kernel/boot loader?

Which (additional) layers do you use?

Are these layers supported by the same version as the Yocto version you want to move to?

How about your own recipes?

Are they compatible with upstream yocto?

Regards,
Rohit
Regards,

Robert


Re: NPM Fetcher & License collection in Yocto Zeus

Oliver Westermann
 

Hey,

 

I figured to squeeze in a test and it seems that this is solved in Dunfell, at least I can’t trigger it even when trying and the folder structure used in the work directory has changed -> No issues there I guess.

 

For Zeus: I’ve checked https://git.yoctoproject.org/cgit/cgit.cgi/poky/log/?h=zeus and it seems that there are no new commits. From https://wiki.yoctoproject.org/wiki/Releases zeus is in the Community phase.
Does this mean no new commits -> Add it to some kind of “known issues” page? Or does it make sense to provide a patch for the zeus branch?

 

Best regards, Olli

 

Von: Jean-Marie Lemetayer <jeanmarie.lemetayer@...>
Gesendet: Freitag, 22. Januar 2021 11:31
An: Westermann, Oliver <Oliver.Westermann@...>
Cc: yocto@...
Betreff: [EXTERNAL] Re: [yocto] NPM Fetcher & License collection in Yocto Zeus

 

Hi Olivier,

 

Thanks for your implication :)

 

I think the modification you want to make resides in the npm class file:

 

But, starting with dunfell, the npm related mechanism have been reworked and also the npm class:

 

Is it possible to test if you have the same issue with dunfell ?

 

Best Regards,

Jean-Marie

 

On Fri, Jan 22, 2021 at 10:00 AM Oliver Westermann <oliver.westermann@...> wrote:

Hey,

We’ve upgraded to zeus some time ago and also updated some of our recipes around node-red and it’s nodes. Before I created my own class to easily fetch several nodes, now we used devtool to create those recipes. In zeus, this happens using the npm:// fetcher.

This worked fine, but we sometimes had QA errors, hard to reproduce. Sometimes on some peoples PC, the license files were missing when do_populate_lic was running.

ERROR: node-red-contrib-socketio-1.0.7-r0 do_populate_lic: QA Issue: node-red-contrib-socketio: LIC_FILES_CHKSUM points to an invalid file: /data/workspace/yocto-build/build/cognex-myna/tmp/work/aarch64-poky-linux/node-red-contrib-socketio/1.0.7-r0/npmpkg/node_modules/
socket.io/node_modules/@types/cookie/LICENSE [license-checksum]

Turned out that do_unpack would download the dependencies of the node-red-module (so in the example above, node-red-contrib-socketio depends on
socket.io), but do_install would package those away/clean them up.
Since they go into the resulting package, we still have to list those licenses, so I fixed it by adding

do_install[depends] += "${PN}:do_populate_lic"

to my packages to fix the order.

However I would like to fix this upstream, but couldn't find the correct source location to add this dependency. Can sb help me figure this out as I would like to contribute
😉

Best regards, Olli


Re: Points to consider while moving to new yocto versions

Erik Boto
 

Hi,

I'd start by looking at the relevant documentation section,
https://www.yoctoproject.org/docs/latest/ref-manual/ref-manual.html#general-migration-considerations.
There you can also find a per-release summary of changes that are
worth knowing when moving to that release.

Moving from krogoth to e.g. gatesgarth is quite a jump, so I'd expect
that it might require some effort. If you don't intend to follow along
new version, you might want to consider using dunfell which is the
current LTS version.

Cheers,
Erik

On Mon, Jan 25, 2021 at 9:07 AM amaya jindal <amayajindal786@gmail.com> wrote:

Hi All,

We are planning to move to New yocto from current one that is krogoth yocto to some updated one. We are not thinking to move to gates-garth or some other major release but the releases than can have easily support for arm.

Please support and help.

Points need to take care to port to new yocto version.

Regards,
Rohit



Re: QA notification for completed autobuilder build (yocto-3.3_M2.rc1)

Sangeeta Jain
 

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.3_M2.rc1. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. Beaglebone

ETA for completion is next Thursday, January 28.

Thanks,
Sangeeta

-----Original Message-----
From: yocto@lists.yoctoproject.org <yocto@lists.yoctoproject.org> On Behalf
Of Pokybuild User
Sent: Thursday, 21 January, 2021 1:05 PM
To: yocto@lists.yoctoproject.org
Cc: qa-build-notification@lists.yoctoproject.org
Subject: [yocto] QA notification for completed autobuilder build (yocto-
3.3_M2.rc1)


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


https://autobuilder.yocto.io/pub/releases/yocto-3.3_M2.rc1


Build hash information:

bitbake: 01e901c44ab0f496606b1d45c8953dc54970204c
meta-arm: a8f32f990a0d9dc1db310892c70d5a994c698b32
meta-gplv2: 6e8e969590a22a729db1ff342de57f2fd5d02d43
meta-intel: b4e5d33affeaa223459c0935a853485137b4591d
meta-kernel: 8349870943ba44bbd688656897372e881f32c741
meta-mingw: 352d8b0aa3c7bbd5060a4cc2ebe7c0e964de4879
oecore: 79821d5a185e25384f5b6b5158b238bbee17c79e
poky: b5e634644b69a968a93aad0dd0502cf479d3973a



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


2141 - 2160 of 54213