Date   

Dependencies are not resolved correctly when building the SDK

asconcepcion
 

Hello,

We have a custom package recipe that has a build dependency with another one (defined in yocto with the DEPENDS variable). If we build an image that includes that package, bitbake will build the dependency before building the package, as expected. However, if we build the SDK associated to that image (with bitbake <image> -c populate_sdk), it will fail in building that package because of a missing dependency. Does anyone know what could be causing this behavior?

Thanks.


Re: # yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

Monsees, Steven C (US)
 

 

Never mind this, I worked it out…  thanks anyway.

 

From: yocto@... <yocto@...> On Behalf Of Monsees, Steven C (US) via lists.yoctoproject.org
Sent: Wednesday, August 25, 2021 12:25 PM
To: yocto@...
Subject: [yocto] # yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

 

External Email Alert

This email has been sent from an account outside of the BAE Systems network.

Please treat the email with caution, especially if you are requested to click on a link, decrypt/open an attachment, or enable macros.  For further information on how to spot phishing, access “Cybersecurity OneSpace Page” and report phishing by clicking the button “Report Phishing” on the Outlook toolbar.

 

 

Using zeus, and I am build an image with no issues...

 

I then want to tweak the configuration by pulling in an a ".cfg" file to be able to tweak options depending on use…

 

I add the following to the image ".bb" file:

 

FILESEXTRAPATHS_prepend := "$THISDIR:"

SRC_URI += "file://sbcb-defaultfs-swdebug.cfg"

 

 

sbcb-defaultfs-swdebug.cfg consists of three lines:

 

CONFIG_KPROBES=y

CONFIG_KPROBES_ON_FTRACE=y

CONFIG_DEBUG_INFO=y

 

When I add the above I see the following build issue, how do I relove this ?

 

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: QA Issue: sbcb-defaultfs-swdebug: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum]

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: Fatal QA errors found, failing task.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-swdebug/1.0-r0/temp/log.do_populate_lic.29324

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_1/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-swdebug.bb:do_populate_lic) failed with exit code '1'

 

Thanks,

Steve


# yocto Fatal QA error (LIC_FILES_CHKSUM) [license-checksum]

Monsees, Steven C (US)
 

 

Using zeus, and I am build an image with no issues...

 

I then want to tweak the configuration by pulling in an a ".cfg" file to be able to tweak options depending on use…

 

I add the following to the image ".bb" file:

 

FILESEXTRAPATHS_prepend := "$THISDIR:"

SRC_URI += "file://sbcb-defaultfs-swdebug.cfg"

 

 

sbcb-defaultfs-swdebug.cfg consists of three lines:

 

CONFIG_KPROBES=y

CONFIG_KPROBES_ON_FTRACE=y

CONFIG_DEBUG_INFO=y

 

When I add the above I see the following build issue, how do I relove this ?

 

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: QA Issue: sbcb-defaultfs-swdebug: Recipe file fetches files and does not have license file information (LIC_FILES_CHKSUM) [license-checksum]

ERROR: sbcb-defaultfs-swdebug-1.0-r0 do_populate_lic: Fatal QA errors found, failing task.

ERROR: Logfile of failure stored in: /disk0/scratch/smonsees/yocto/workspace_1/builds2/sbcb-default/tmp/work/sbcb_default-poky-linux/sbcb-defaultfs-swdebug/1.0-r0/temp/log.do_populate_lic.29324

ERROR: Task (/disk0/scratch/smonsees/yocto/workspace_1/poky/../meta-bae/meta-limws/meta-intel/recipes-core/images/sbcb-defaultfs-swdebug.bb:do_populate_lic) failed with exit code '1'

 

Thanks,

Steve


using STAGING_KERNEL_DIR for compiling userspace program

Marek Belisko
 

Hi,

I'm trying to add a recipe for:
https://github.com/bootlin/libva-v4l2-request package. This library
heavily depends on actual kernel headers (see
PR.https://github.com/bootlin/libva-v4l2-request). I've bumped kernel
to 5.14-rc7 nad in recipe I'm trying to use what is suggested:

# This is how linux-libc-headers says to include custom uapi headers
CFLAGS_append += " -I ${STAGING_KERNEL_DIR}/include/uapi -I
${STAGING_KERNEL_DIR}/include "
do_configure[depends] += "virtual/kernel:do_shared_workdir"

Problem is that I see a lot of errors like:
kernel-source/include/linux/cache.h:6:10: fatal error: asm/cache.h: No
such file or directory
| 6 | #include <asm/cache.h>

or
recipe-sysroot/usr/include/bits/stdint-intn.h:27:19: note: previous
declaration of 'int64_t' was here
| 27 | typedef __int64_t int64_t;

I tried to compile this package manually on the host only difference
is that I used headers from 5.14 by make headers_install and
everything compiled fine. Any ideas on how to fix this issue?

Thanks and BR,

marek


--
as simple and primitive as possible
-------------------------------------------------
Marek Belisko - OPEN-NANDRA
Freelance Developer

Ruska Nova Ves 219 | Presov, 08005 Slovak Republic
Tel: +421 915 052 184
skype: marekwhite
twitter: #opennandra
web: http://open-nandra.com


Build a pyinstaller recipe

yasminebenghozzi6@...
 

Hello,

So have anyone been successful at making a pyinstaller recipe in yocto? Or add pyinstaller in the yocto image? 
Please I need help


[meta-tpm][PATCH v2] README: fix mailing lists and a typo

Marta Rybczynska
 

A number of typo fixes:
- tmp->tpm in the DISTRO_FEATURES
- update the mailing list address as it was out of date
- update the distro name in the subject

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-tpm/README | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/meta-tpm/README b/meta-tpm/README
index 4441dd2..2b32a9f 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -5,7 +5,7 @@ The bbappend files for some recipes (e.g. linux-yocto) in this layer need
to have 'tpm' in DISTRO_FEATURES to have effect.
To enable them, add in configuration file the following line.

- DISTRO_FEATURES:append = " tmp"
+ DISTRO_FEATURES:append = " tpm"

If meta-tpm is included, but tpm is not enabled as a
distro feature a warning is printed at parse time:
@@ -57,15 +57,15 @@ other layers needed. e.g.:
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-tpm][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
-$ git config format.subjectPrefix meta-security][PATCH
+$ git config sendemail.to yocto@...
+$ git config format.subjectPrefix meta-tpm][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.

--
2.30.2


[meta-tpm][PATCH] README: fix mailing lists and a typo

Marta Rybczynska
 

A number of typo fixes:
- tmp->tpm in the DISTRO_FEATURES
- update the mailing list address as it was out of date
- update the distro name in the subject

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-tpm/README | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta-tpm/README b/meta-tpm/README
index 4441dd2..5722a92 100644
--- a/meta-tpm/README
+++ b/meta-tpm/README
@@ -5,7 +5,7 @@ The bbappend files for some recipes (e.g. linux-yocto) in this layer need
to have 'tpm' in DISTRO_FEATURES to have effect.
To enable them, add in configuration file the following line.

- DISTRO_FEATURES:append = " tmp"
+ DISTRO_FEATURES:append = " tpm"

If meta-tpm is included, but tpm is not enabled as a
distro feature a warning is printed at parse time:
@@ -57,14 +57,14 @@ other layers needed. e.g.:
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-security][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
+$ git config sendemail.to yocto@...
$ git config format.subjectPrefix meta-security][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.
--
2.30.2


#linux #zeus #yocto #imx6 #bitbake #make #make #linux #zeus #yocto #imx6

noel.neu@...
 

Hi! 

I would like to implement an out-of-tree  ASoC Machine driver in my project. It #includes some in-tree header files such ../codecs/codecX.h. These are however not found when I try to build the recipe. I have followed the example project "hello-mod", but that doesn't require any in-tree header files, so it doesn't help in this case. 

What do I need to do in oder for Bitbake to find these headers ?
Thanks!


Re: oFono Version 1.31 ofonod crash

JH
 

Hi Sergei,

Thanks for the advice, the latest ofono in oe-core master is 1.32, but
I am in branch Hardknott, so I copied ofono 1.32 from master to my
layer running Hardknott branch, but I could not build ofono 1.32 in
Hardknott:

ERROR: ParseError at
/build/oe-cor/../meta-solar/recipes-connectivity/ofono/ofono_1.32.bb:22:
unparsed line: 'SYSTEMD_SERVICE:${PN} = "ofono.service"'

I used ofono 1.30 and connman 1.37 in Zeus, both worked fine , but
both connman 1.39 and ofono 1.31 failed to work properly in oe-core
Hardknott branch, to narrow down if it is ofono issue or Yocto OE
build or other library issue, I was able to build ofono 1.30 for
Hardknott, I can confirm that ofono 1.30 failed just like the 1.31
stuck at the statement add_serial_device.

................
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[2806]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property

If I run ofono 1.30 built from Zeus build, the ofonod would pass
missing OFONO_DRIVER property and kept it work:

......
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem()
/sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:create_modem() driver=ubloxqmi
ofonod[3712]: ../ofono-1.30/src/modem.c:ofono_modem_create() name:
(null), type: ubloxqmi
ofonod[3712]: ../ofono-1.30/plugins/udevng.c:setup_ubloxqmi()
/sys/devices/soc0/soc/2100000.aips-bus/2184200.usb/ci_hdrc.1/usb1/1-1
.....

So I don't think it is an oFono issue, but rather an OE Yocto build or
library issue, can anyone run oFono in oe-core Hardknott branch?

Thank you.

Kind regards,

- jupiter



On 8/22/21, Sergei Golubtsov <s.e.golubtsov@...> wrote:
Hi jupiter,

Please try to update ofono to the latest release. Seems to be a library
incompatibility issue or something like that.

Yours sincerely,
Sergei Golubtsov.


On Sat, Aug 21, 2021 at 4:09 AM Jupiter <jupiter.hce@...> wrote:

Hi,

I build ofono v1.31 from git://git.yoctoproject.org/poky branch
hardknott,

$ cat meta/recipes-connectivity/ofono/ofono_1.31.bb

SUMMARY = "open source telephony"
DESCRIPTION = "oFono is a stack for mobile telephony devices on Linux.
oFono supports speaking to telephony devices through specific drivers,
or with generic AT commands."
HOMEPAGE = "http://www.ofono.org"
BUGTRACKER = "https://01.org/jira/browse/OF"
LICENSE = "GPLv2"
LIC_FILES_CHKSUM = "file://COPYING;md5=eb723b61539feef013de476e68b5c50a \


file://src/ofono.h;beginline=1;endline=20;md5=3ce17d5978ef3445def265b98899c2ee"
DEPENDS = "dbus glib-2.0 udev mobile-broadband-provider-info ell"

SRC_URI = "\
${KERNELORG_MIRROR}/linux/network/${BPN}/${BP}.tar.xz \
file://ofono \
file://0001-mbim-add-an-optional-TEMP_FAILURE_RETRY-macro-copy.patch
\
"
SRC_URI[md5sum] = "1c26340e3c6ed132cc812595081bb3dc"
SRC_URI[sha256sum] =
"a15c5d28096c10eb30e47a68b6dc2e7c4a5a99d7f4cfedf0b69624f33d859e9b"

inherit autotools pkgconfig update-rc.d systemd
gobject-introspection-data

INITSCRIPT_NAME = "ofono"
INITSCRIPT_PARAMS = "defaults 22"
SYSTEMD_SERVICE_${PN} = "ofono.service"

PACKAGECONFIG ??= "\
${@bb.utils.filter('DISTRO_FEATURES', 'systemd', d)} \
${@bb.utils.contains('DISTRO_FEATURES', 'bluetooth', 'bluez', '', d)}
\
"
PACKAGECONFIG[systemd] =
"--with-systemdunitdir=${systemd_unitdir}/system/,--with-systemdunitdir="
PACKAGECONFIG[bluez] = "--enable-bluetooth, --disable-bluetooth, bluez5"

EXTRA_OECONF += "--enable-test --enable-external-ell"

do_install_append() {
install -d ${D}${sysconfdir}/init.d/
install -m 0755 ${WORKDIR}/ofono ${D}${sysconfdir}/init.d/ofono
}

PACKAGES =+ "${PN}-tests"

FILES_${PN} += "${systemd_unitdir}"
FILES_${PN}-tests = "${libdir}/${BPN}/test"

RDEPENDS_${PN} += "dbus"
RDEPENDS_${PN}-tests = "\
python3-core \
python3-dbus \
${@bb.utils.contains('GI_DATA_ENABLED', 'True',
'python3-pygobject', '', d)} \
"

RRECOMMENDS_${PN} += "kernel-module-tun mobile-broadband-provider-info"

The build was fine, but running the v1.31 ofono.service crashed at
udevng.c missing OFONO_DRIVER property, the ofono.service was repeated
to be restarted every 6 seconds:

.....

ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
ofonod[9005]: ../ofono-1.31/plugins/udevng.c:add_serial_device()
Device is missing required OFONO_DRIVER property
......

I am not quite sure if it is ofono 1.31 problem or oe-core
ofono_1.31.bb problem, could anyone have a look at and advise? Let me
know if you need more debug information.

Thank you.

Kind regards,

- jupiter


On 8/20/21, Jupiter <jupiter.hce@...> wrote:
Hi,

I upgraded from Zeus to Hardknotte, I was able to run dbus to get
interface properties, but I failed on Hardknotte ofono 1.31. Has
anyone got oFono 1.31 dbus work?

Thank you.

Kind regards,

- jupiter
_______________________________________________
ofono mailing list -- ofono@...
To unsubscribe send an email to ofono-leave@...

--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


[meta-hardening][PATCH] README: fix mailing lists

Marta Rybczynska
 

The address included in the meta-hardening documentation
does not work and was changed in other places in 2019.

Signed-off-by: Marta Rybczynska <rybczynska@...>
---
meta-hardening/README | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/meta-hardening/README b/meta-hardening/README
index 37a0b7e..191253c 100644
--- a/meta-hardening/README
+++ b/meta-hardening/README
@@ -64,14 +64,14 @@ layers: meta-oe
Maintenance
-----------

-Send pull requests, patches, comments or questions to yocto@...
+Send pull requests, patches, comments or questions to yocto@...

When sending single patches, please using something like:
-'git send-email -1 --to yocto@... --subject-prefix=meta-hardening][PATCH'
+'git send-email -1 --to yocto@... --subject-prefix=meta-hardening][PATCH'

These values can be set as defaults for this repository:

-$ git config sendemail.to yocto@...
+$ git config sendemail.to yocto@...
$ git config format.subjectPrefix meta-hardening][PATCH

Now you can just do 'git send-email origin/master' to send all local patches.
--
2.30.2


[meta-hardening][PATCH] meta-hardening/binutils: harden installation permissions

Marta Rybczynska
 

Compilers and related utils are better restricted on production platforms.
Change permissions of all installed binutils tools to remove access from
users outside of the root group.

This also demonstrates how to restrict file permissions in a hardened
distribution.

Signed-off-by: Marta Rybczynska <marta.rybczynska@...>
---
meta-hardening/recipes-devtools/binutils/binutils_%.bbappend | 3 +++
1 file changed, 3 insertions(+)
create mode 100644 meta-hardening/recipes-devtools/binutils/binutils_%.bbappend

diff --git a/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend b/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend
new file mode 100644
index 0000000..3eb3ad0
--- /dev/null
+++ b/meta-hardening/recipes-devtools/binutils/binutils_%.bbappend
@@ -0,0 +1,3 @@
+do_install_append_class-target () {
+ chmod o-rx ${D}${prefix}/${TARGET_SYS}/bin/*
+}
--
2.30.2


Yocto error while bitbaking a recipe

yasminebenghozzi6@...
 

Hello, 
SO I'm working on a new recipe, while bitbaking it , this happened, and I really don't know what it's about, 

ERROR: Setscene task /home/yasmine/yocto/poky/meta/recipes-core/packagegroups/packagegroup-core-buildessential.bb:do_package in both covered and notcovered.

I'l appreciate your help
 


[meta-mingw] [PATCH] grpc: use the new PACKAGECONFIG to disable shared

Sinan Kaya <okaya@...>
 

There is a new PACKAGECONFIG for grpc to allows us
to selectively enable/disable shared builds.

Signed-off-by: Sinan Kaya <okaya@...>
---
.../openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
index dc0ea42..4cbd1a4 100644
--- a/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
+++ b/dynamic-layers/openembedded-layers/recipes-devtools/grpc/grpc_%.bbappend
@@ -1,5 +1,4 @@
# doesn't build and not required
DEPENDS:remove:mingw32 = "libnsl2"

-EXTRA_OECMAKE:remove:mingw32 = "-DBUILD_SHARED_LIBS=ON"
-EXTRA_OECMAKE:append:mingw32 = " -DBUILD_SHARED_LIBS=OFF"
+PACKAGECONFIG:remove:mingw32 = "shared"
--
2.17.1


Yocto Project Status WW34`21

Stephen Jolley
 

Current Dev Position: YP 3.4 M3 (Feature Freeze)

Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze)

 

Next Team Meetings:

 

Key Status/Updates:

  • We are now at feature freeze for YP 3.4
  • Read-only PRServ and switch to asyncio was merged
  • Rust merging to core is proving problematic due to issues interacting with uninative. These cause many strange autobuilder failures so this issue would have to be addressed in the next day or two in order to be in 3.4.
  • glibc 2.34 and the merge of the various libraries into libc is causing significant problems for pseudo. This issue is causing significant worry as the project will struggle as distros adopt the new glibc version unless we work out how to fix things.
  • The tune file layout change was merged.
  • We are still hoping to get some of the planned SBOM work into 3.4
  • Intermittent issues are ongoing and help is very much welcome on these issues. 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

 

Ways to contribute:

 

YP 3.4 Milestone Dates:

  • YP 3.4 M3 build date 2021/08/23 (Feature Freeze)
  • YP 3.4 M3 Release date 2021/09/03
  • YP 3.4 M4 build date 2021/10/04
  • YP 3.4 M4 Release date 2021/10/29

 

Planned upcoming dot releases:

  • YP 3.1.11 build date 2021/09/13
  • YP 3.1.11 release date 2021/9/24

 

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

 


Re: Update bitbake broken build

Martin Jansa
 

On Tue, Aug 24, 2021 at 12:33 AM JH <jupiter.hce@...> wrote:
Hi,

I updated the bitbake to run git pull in master branch, now it is
broken, what does the following error message mean, how to fix it?

$ bitbake-layers show-layers

NOTE: Starting bitbake server...
ERROR: Variable PROVIDES_prepend contains an operation using the old
override syntax. Please convert this layer/metadata before attempting
to use with a newer bitbake.

Thank you.

Kind regards,

- jupiter




#yocto #dunfell Console Standard input dirty without "tools-sdk" image feature #yocto #dunfell

ivin.lim@...
 


Using dunfell 3.1.8

Will post this inquiry while doing my own investigation. When outputting to the debug console that involves standard input(ex. busctl, systemctl status), the output seems misaligned and dirty.
But I noticed this can be easily fixed by adding to the "tools-sdk" to the EXTRA_IMAGE_FEATURES. 
I'm curious to know what else tools-sdk seems to besides adding development tools(ex. gcc,make)

Below is the snapshot when tools-sdk isn't included in the image built



M+ & H bugs with Milestone Movements WW34

Stephen Jolley
 

All,

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

Priority

Bug ID

Short Description

Changer

Owner

Was

Became

Medium+

13722

Debugging With the GNU Project Debugger enhancements

randy.macleod@...

john.kaldas.enpj@...

3.4 M2

3.4 M4

 

13903

npmsw fetcher fails if multiple recipes have common npm packages

randy.macleod@...

jeanmarie.lemetayer@...

3.4 M2

3.4 M4

 

13954

Invalid layerindex data causing backtrace in `bitbake-layers layerindex-fetch`

randy.macleod@...

unassigned@...

3.4 M2

3.4 M4

 

14060

devtool modify fails when applied on recipes using patches

randy.macleod@...

saul.wold@...

3.4 M2

3.4 M4

 

14146

Post-patch hook fails with submodules and PATCHTOOL=git and PATCH_COMMIT_FUNCTIONS=1

randy.macleod@...

unassigned@...

3.4 M2

3.99

 

14385

mode of sstate files created under pseudo

randy.macleod@...

mark.hatle@...

3.4 M2

3.4 M4

 

14444

[multilib] lib32-core-image-minimal -c populate_sdk failure on dunfell

randy.macleod@...

steve@...

3.4 M2

3.1.11

 

14449

AB-INT PTEST ARM: quilt patch-wrapper ptest intermittent failure

randy.macleod@...

randy.macleod@...

3.4 M3

3.4 M4

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

(    Cell:                (208) 244-4460

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

 


Enhancements/Bugs closed WW34!

Stephen Jolley
 

All,

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

Who

Count

ross@...

2

fransmeulenbroeks@...

1

alexandre.belloni@...

1

randy.macleod@...

1

jay.shen.teoh@...

1

Grand Total

6

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.4

Stephen Jolley
 

All,

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

Who

Count

michael.opdenacker@...

32

ross@...

31

david.reyna@...

22

richard.purdie@...

21

bruce.ashfield@...

16

randy.macleod@...

13

trevor.gamblin@...

13

timothy.t.orling@...

12

JPEWhacker@...

10

sakib.sajal@...

10

bluelightning@...

7

kai.kang@...

7

tony.tascioglu@...

5

hongxu.jia@...

4

Qi.Chen@...

4

mingli.yu@...

3

chee.yang.lee@...

3

alexandre.belloni@...

2

mshah@...

2

jaewon@...

2

yf3yu@...

2

akuster808@...

2

yi.zhao@...

2

alejandro@...

2

vinay.m.engg@...

1

raj.khem@...

1

pokylinux@...

1

mostthingsweb@...

1

weaverjs@...

1

Martin.Jansa@...

1

yoctoproject@...

1

nicolas.dechesne@...

1

kergoth@...

1

dl9pf@...

1

mark.hatle@...

1

open.source@...

1

paul@...

1

jon.mason@...

1

mister_rs@...

1

ydirson@...

1

john.kaldas.enpj@...

1

naveen.kumar.saini@...

1

devendra.tewari@...

1

jeanmarie.lemetayer@...

1

diego.sueiro@...

1

aehs29@...

1

thomas.perrot@...

1

matthewzmd@...

1

douglas.royds@...

1

saul.wold@...

1

tonyb@...

1

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

 

2861 - 2880 of 57387