Re: [OE-core] [PATCH] staging: use relative path in sysroot_stage_dir()

[ahussain]

Hello maintainers,

Can we get a feedback on this.

Thanks,
Ahsan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161600): 
https://lists.openembedded.org/g/openembedded-core/message/161600
Mute This Topic: https://lists.openembedded.org/mt/88803600/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [qa-build-notification] QA notification for completed autobuilder build (yocto-3.1.14.rc1)

[Teoh, Jay Shen]

Hi all,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.1.14.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 next Tuesday, Feb 15.

Thanks,
Jay

> -Original Message-
> From: qa-build-notificat...@lists.yoctoproject.org  notificat...@lists.yoctoproject.org> On Behalf Of Richard Purdie
> Sent: Tuesday, 1 February, 2022 5:47 AM
> To:  
> Cc: qa-build-notification 
> Subject: [qa-build-notification] QA notification for completed autobuilder
> build (yocto-3.1.14.rc1)
> 
> A build flagged for QA (yocto-3.1.14.rc1) was completed on the autobuilder
> and is available at:
> 
> 
> https://autobuilder.yocto.io/pub/releases/yocto-3.1.14.rc1
> 
> 
> Build hash information:
> 
> bitbake: be6ecc160ac4a8d9715257b9b955363cecc081ea
> meta-agl: 7a644d636237459c54128a71d083cb6f9e1b8e60
> meta-arm: ce535dfb96de4d2529f091d7d85a7172c626001c
> meta-aws: 9979cfa676105cb68cfadfdaeabf044d7c919319
> meta-gplv2: 60b251c25ba87e946a0ca4cdc8d17b1cb09292ac
> meta-intel: 87984115eb6ed1a4c17204629dcb100f6b76fe82
> meta-mingw: 524de686205b5d6736661d4532f5f98fee8589b7
> meta-openembedded: ab9fca485e13f6f2f9761e1d2810f87c2e4f060a
> oecore: f3be01483b01c88f8c4ba24ca73ccf1bcc33665c
> poky: bba323389749ec3e306509f8fb12649f031be152
> 
> 
> 
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.pur...@linuxfoundation.org
> 
> 
> 
> 
> 
> 
> 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161599): 
https://lists.openembedded.org/g/openembedded-core/message/161599
Mute This Topic: https://lists.openembedded.org/mt/89039147/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH V2] nghttp2: fix for multilib support

[Changqing Li]

From: Changqing Li 

Update package name to fix following error:
ERROR: Required build target 'lib32-core-image-minimal' has no buildable 
providers.
Missing or unbuildable dependency chain was: ['lib32-core-image-minimal', 
'lib32-libnghttp2']

for lib32 image, lib{PN} will be expanded as lib32-liblib32-nghttp2, so
above error occurs, update lib{PN} to lib{BPN} to fix it.

Signed-off-by: Changqing Li 
---
 meta/recipes-support/nghttp2/nghttp2_1.46.0.bb | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-support/nghttp2/nghttp2_1.46.0.bb 
b/meta/recipes-support/nghttp2/nghttp2_1.46.0.bb
index 972ff2d60a..0ad45ed2c7 100644
--- a/meta/recipes-support/nghttp2/nghttp2_1.46.0.bb
+++ b/meta/recipes-support/nghttp2/nghttp2_1.46.0.bb
@@ -19,7 +19,7 @@ PACKAGECONFIG[manpages] = ""
 # first place
 EXTRA_OECMAKE = "-DENABLE_EXAMPLES=OFF -DENABLE_APP=OFF 
-DENABLE_HPACK_TOOLS=OFF"
 
-PACKAGES =+ "lib${PN} ${PN}-client ${PN}-proxy ${PN}-server"
+PACKAGES =+ "lib${BPN} ${PN}-client ${PN}-proxy ${PN}-server"
 
 RDEPENDS:${PN} = "${PN}-client (>= ${PV}) ${PN}-proxy (>= ${PV}) ${PN}-server 
(>= ${PV})"
 RDEPENDS:${PN}:class-native = ""
@@ -27,7 +27,7 @@ RDEPENDS:${PN}-proxy = "openssl python3-core python3-io 
python3-shell"
 
 ALLOW_EMPTY:${PN} = "1"
 FILES:${PN} = ""
-FILES:lib${PN} = "${libdir}/*${SOLIBS}"
+FILES:lib${BPN} = "${libdir}/*${SOLIBS}"
 FILES:${PN}-client = "${bindir}/h2load ${bindir}/nghttp"
 FILES:${PN}-proxy = "${bindir}/nghttpx ${datadir}/${BPN}/fetch-ocsp-response"
 FILES:${PN}-server = "${bindir}/nghttpd"
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161598): 
https://lists.openembedded.org/g/openembedded-core/message/161598
Mute This Topic: https://lists.openembedded.org/mt/89037201/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] man-db: Fix build with clang

[Khem Raj]

Signed-off-by: Khem Raj 
---
 ...ariable-declaration-to-function-scop.patch | 41 +++
 meta/recipes-extended/man-db/man-db_2.10.0.bb |  1 +
 2 files changed, 42 insertions(+)
 create mode 100644 
meta/recipes-extended/man-db/files/0001-man-Move-local-variable-declaration-to-function-scop.patch

diff --git 
a/meta/recipes-extended/man-db/files/0001-man-Move-local-variable-declaration-to-function-scop.patch
 
b/meta/recipes-extended/man-db/files/0001-man-Move-local-variable-declaration-to-function-scop.patch
new file mode 100644
index 000..820b17b5de6
--- /dev/null
+++ 
b/meta/recipes-extended/man-db/files/0001-man-Move-local-variable-declaration-to-function-scop.patch
@@ -0,0 +1,41 @@
+From 4b5e00ad020ec327cbc934528d02aa8c4fe3910b Mon Sep 17 00:00:00 2001
+From: Khem Raj 
+Date: Wed, 9 Feb 2022 17:30:16 -0800
+Subject: [PATCH] man: Move local variable declaration to function scope
+
+There is a clang bug [1] unearthed here, so help clang by re-arranging
+code without changing the logic, until its fixed in clang
+
+[1] https://github.com/llvm/llvm-project/issues/53692
+
+Upstream-Status: Inappropriate [Inappropriate: Clang bug]
+Signed-off-by: Khem Raj 
+---
+ src/man.c | 4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+diff --git a/src/man.c b/src/man.c
+index c91abf1..3240eea 100644
+--- a/src/man.c
 b/src/man.c
+@@ -352,7 +352,7 @@ static void init_html_pager (void)
+ static error_t parse_opt (int key, char *arg, struct argp_state *state)
+ {
+   static bool apropos, whatis; /* retain values between calls */
+-
++  char *s;
+   /* Please keep these keys in the same order as in options above. */
+   switch (key) {
+   case 'C':
+@@ -383,7 +383,7 @@ static error_t parse_opt (int key, char *arg, struct 
argp_state *state)
+ 
+   case OPT_WARNINGS:
+ #ifdef NROFF_WARNINGS
+-  char *s = xstrdup (arg ? arg : default_roff_warnings);
++  s = xstrdup (arg ? arg : default_roff_warnings);
+   const char *warning;
+ 
+   for (warning = strtok (s, ","); warning;
+-- 
+2.35.1
+
diff --git a/meta/recipes-extended/man-db/man-db_2.10.0.bb 
b/meta/recipes-extended/man-db/man-db_2.10.0.bb
index 6a8ac2e3e34..a604930198e 100644
--- a/meta/recipes-extended/man-db/man-db_2.10.0.bb
+++ b/meta/recipes-extended/man-db/man-db_2.10.0.bb
@@ -7,6 +7,7 @@ LIC_FILES_CHKSUM = 
"file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c \
 
 SRC_URI = "${SAVANNAH_NONGNU_MIRROR}/man-db/man-db-${PV}.tar.xz \
file://99_mandb \
+   
file://0001-man-Move-local-variable-declaration-to-function-scop.patch \
file://man_db.conf-avoid-multilib-install-file-conflict.patch"
 SRC_URI[sha256sum] = 
"0a8629022f7117dc7fc6473c6fdb14913b24b106059bb056abee87dbd6070c79"
 
-- 
2.35.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161597): 
https://lists.openembedded.org/g/openembedded-core/message/161597
Mute This Topic: https://lists.openembedded.org/mt/89036942/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] ed: upgrade 1.17 -> 1.18

[wangmy]

As you can see the ChangeLog shown below, in version 1.5 the maintainer 
mistakenly changed the copyright holder from Andrew Moore to the FSF. In 
versions 1.6 and 1.11 he tried to fix the mistake, but he forgot to restore the 
original COPYING, which he have done now in 1.18.

Therefore, in addition to changing the LICENSE field from GPLv3 + to GPLv2 , 
should I add relevant information in the commit?

2010-08-30  Antonio Diaz Diaz  
* Version 1.5 released.
* Change copyright holder from Andrew, Antonio to the FSF.
  (This change was later discovered to be wrong. See 1.6 and 1.11).

2012-01-01  Antonio Diaz Diaz  

* Version 1.6 released.
* Restore copyright notices of Andrew L. Moore. It seems Andrew
  granted some permissions but never assigned copyright to the FSF.

2015-03-30  Antonio Diaz Diaz  

* Version 1.11 released.
* Restore original copyright and license notices in the code. I
  assigned to the FSF the copyright on changes made to the part of ed
  already copyrighted by the FSF, which seems to be just the manual.

2022-02-04  Antonio Diaz Diaz  
* Version 1.18 released.
* COPYING: Restored. (I forgot to do it in 1.11).

> -Original Message-
> From: Alexander Kanavin 
> Sent: Tuesday, February 8, 2022 6:25 PM
> To: Wang, Mingyu/王 鸣瑜 
> Cc: OE-core 
> Subject: Re: [OE-core] [PATCH] ed: upgrade 1.17 -> 1.18
> 
> On Tue, 8 Feb 2022 at 09:26, wangmy  wrote:
> 
> > License-Update:
> > year updated to 2022.
> > license changed from GNU3 to GNU2.
> >  LICENSE = "GPLv3+"
> > -LIC_FILES_CHKSUM =
> "file://COPYING;md5=0c7051aef9219dc7237f206c5c4179a7 \
> > -
> file://ed.h;endline=20;md5=b72aa5eaafef318c6bfc37f858469113 \
> > -
> file://main.c;endline=17;md5=2c93e24f4db3528a00a24c7df5618e41 \
> > +LIC_FILES_CHKSUM =
> "file://COPYING;md5=76d6e300ffd8fb9d18bd9b136a9bba13 \
> > +
> file://ed.h;endline=20;md5=6e6a818b0593f937fc63ba08d5e314bf \
> > +
> > +file://main.c;endline=17;md5=8419a08bb12936f32384a0d1c0f9e74c \
> 
> 
> If the license changed, you need to update the LICENSE field. Also a bit
> more research would be appreciated: can you find and link the commit
> where the change occurred?
> 
> Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161596): 
https://lists.openembedded.org/g/openembedded-core/message/161596
Mute This Topic: https://lists.openembedded.org/mt/88992428/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[oe-core][PATCH 1/1] virglrenderer: fix CVE-2022-0135 and -0175

[Joe Slater]

CVE-2022-0135 concerns out-of-bounds writes in read_transfer_data().
CVE-2022-0175 concerns using malloc() instead of calloc().

We "cherry-pick" from upstream.  The actual cherry-picks are from
upstream master to branch-0.9.1 and are the patches entered here.

Signed-off-by: Joe Slater 
---
 .../virglrenderer/cve-2022-0135.patch | 117 ++
 .../virglrenderer/cve-2022-0175.patch | 107 
 .../virglrenderer/virglrenderer_0.9.1.bb  |   2 +
 3 files changed, 226 insertions(+)
 create mode 100644 
meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
 create mode 100644 
meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch

diff --git 
a/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch 
b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
new file mode 100644
index 00..ae42dc8f6c
--- /dev/null
+++ b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0135.patch
@@ -0,0 +1,117 @@
+From 63aee871365f9c9e7fa9125672302a0fb250d34d Mon Sep 17 00:00:00 2001
+From: Gert Wollny 
+Date: Tue, 30 Nov 2021 09:16:24 +0100
+Subject: [PATCH 2/2] vrend: propperly check whether the shader image range is
+ correct
+
+Also add a test to check the integer underflow.
+
+Closes: #251
+Signed-off-by: Gert Wollny 
+Reviewed-by: Chia-I Wu 
+
+cherry-pick from anongit.freedesktop.org/virglrenderer
+commit 2aed5d4...
+
+CVE: CVE-2022-0135
+Upstream-Status: Backport
+Signed-off-by: Joe Slater 
+
+---
+ src/vrend_decode.c  |  3 +-
+ tests/test_fuzzer_formats.c | 57 +
+ 2 files changed, 59 insertions(+), 1 deletion(-)
+
+diff --git a/src/vrend_decode.c b/src/vrend_decode.c
+index 91f5f24..6771b10 100644
+--- a/src/vrend_decode.c
 b/src/vrend_decode.c
+@@ -1249,8 +1249,9 @@ static int vrend_decode_set_shader_images(struct 
vrend_context *ctx, const uint3
+if (num_images < 1) {
+   return 0;
+}
++
+if (start_slot > PIPE_MAX_SHADER_IMAGES ||
+-   start_slot > PIPE_MAX_SHADER_IMAGES - num_images)
++   start_slot + num_images > PIPE_MAX_SHADER_IMAGES)
+   return EINVAL;
+ 
+for (uint32_t i = 0; i < num_images; i++) {
+diff --git a/tests/test_fuzzer_formats.c b/tests/test_fuzzer_formats.c
+index 154a2e5..e32caf0 100644
+--- a/tests/test_fuzzer_formats.c
 b/tests/test_fuzzer_formats.c
+@@ -958,6 +958,61 @@ static void test_vrend_set_signle_abo_heap_overflow() {
+ virgl_renderer_submit_cmd((void *) cmd, ctx_id, 0xde);
+ }
+ 
++static void test_vrend_set_shader_images_overflow()
++{
++uint32_t num_shaders = PIPE_MAX_SHADER_IMAGES + 1;
++uint32_t size = num_shaders * VIRGL_SET_SHADER_IMAGE_ELEMENT_SIZE + 3;
++uint32_t cmd[size];
++int i = 0;
++cmd[i++] = ((size - 1)<< 16) | 0 << 8 | VIRGL_CCMD_SET_SHADER_IMAGES;
++cmd[i++] = PIPE_SHADER_FRAGMENT;
++memset([i], 0, size - i);
++
++virgl_renderer_submit_cmd((void *) cmd, ctx_id, size);
++}
++
++/* Test adapted from yaojun8558...@gmail.com:
++ * https://gitlab.freedesktop.org/virgl/virglrenderer/-/issues/250
++*/
++static void test_vrend_3d_resource_overflow() {
++
++struct virgl_renderer_resource_create_args resource;
++resource.handle = 0x4c474572;
++resource.target = PIPE_TEXTURE_2D_ARRAY;
++resource.format = VIRGL_FORMAT_Z24X8_UNORM;
++resource.nr_samples = 2;
++resource.last_level = 0;
++resource.array_size = 3;
++resource.bind = VIRGL_BIND_SAMPLER_VIEW;
++resource.depth = 1;
++resource.width = 8;
++resource.height = 4;
++resource.flags = 0;
++
++virgl_renderer_resource_create(, NULL, 0);
++virgl_renderer_ctx_attach_resource(ctx_id, resource.handle);
++
++uint32_t size = 0x400;
++uint32_t cmd[size];
++int i = 0;
++cmd[i++] = (size - 1) << 16 | 0 << 8 | VIRGL_CCMD_RESOURCE_INLINE_WRITE;
++cmd[i++] = resource.handle;
++cmd[i++] = 0; // level
++cmd[i++] = 0; // usage
++cmd[i++] = 0; // stride
++cmd[i++] = 0; // layer_stride
++cmd[i++] = 0; // x
++cmd[i++] = 0; // y
++cmd[i++] = 0; // z
++cmd[i++] = 8; // w
++cmd[i++] = 4; // h
++cmd[i++] = 3; // d
++memset([i], 0, size - i);
++
++virgl_renderer_submit_cmd((void *) cmd, ctx_id, size);
++}
++
++
+ int main()
+ {
+initialize_environment();
+@@ -980,6 +1035,8 @@ int main()
+test_cs_nullpointer_deference();
+test_vrend_set_signle_abo_heap_overflow();
+ 
++   test_vrend_set_shader_images_overflow();
++   test_vrend_3d_resource_overflow();
+ 
+virgl_renderer_context_destroy(ctx_id);
+virgl_renderer_cleanup();
+-- 
+2.25.1
+
diff --git 
a/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch 
b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch
new file mode 100644
index 00..7fbab75091
--- /dev/null
+++ b/meta/recipes-graphics/virglrenderer/virglrenderer/cve-2022-0175.patch
@@ -0,0 +1,107 @@
+From 

[OE-core] [PATCH 3/3] linux-yocto/5.4: update to v5.4.178

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

76fd334f07cc Linux 5.4.178
ed339069725a cgroup/cpuset: Fix "suspicious RCU usage" lockdep warning
c8d7d7c58e64 ext4: fix error handling in ext4_restore_inline_data()
f4a575eada7c EDAC/xgene: Fix deferred probing
0f1ca7cea596 EDAC/altera: Fix deferred probing
66c5aa5726bc rtc: cmos: Evaluate century appropriate
2ffe36c9c4b6 selftests: futex: Use variable MAKE instead of make
c17a316f3d53 nfsd: nfsd4_setclientid_confirm mistakenly expires confirmed 
client.
53e4f71763c6 scsi: bnx2fc: Make bnx2fc_recv_frame() mp safe
bfba4e8088ca pinctrl: bcm2835: Fix a few error paths
71e60c170105 ASoC: max9759: fix underflow in speaker_gain_control_put()
e7e396324fe2 ASoC: cpcap: Check for NULL pointer after calling 
of_get_child_by_name
7709133f1f7a ASoC: xilinx: xlnx_formatter_pcm: Make buffer bytes multiple 
of period bytes
e51b323f891f ASoC: fsl: Add missing error handling in pcm030_fabric_probe
04698be843dc drm/i915/overlay: Prevent divide by zero bugs in scaling
4a674b8e8a3c net: stmmac: ensure PTP time register reads are consistent
9afc02864031 net: stmmac: dump gmac4 DMA registers correctly
77454c9ada77 net: macsec: Verify that send_sci is on when setting Tx sci 
explicitly
dc8c2f0d010c net: ieee802154: Return meaningful error codes from the 
netlink helpers
6f38d3a6ec11 net: ieee802154: ca8210: Stop leaking skb's
859ded7ac2a6 net: ieee802154: mcr20a: Fix lifs/sifs periods
13be1165efda net: ieee802154: hwsim: Ensure proper channel selection at 
probe time
8cfa026a212e spi: meson-spicc: add IRQ check in meson_spicc_probe
fe58eb96bb41 spi: mediatek: Avoid NULL pointer crash in interrupt
c9fc48511c65 spi: bcm-qspi: check for valid cs before applying chip select
6e0498e24b13 iommu/amd: Fix loop timeout issue in iommu_ga_log_enable()
5c43d46daa0d iommu/vt-d: Fix potential memory leak in 
intel_setup_irq_remapping()
cff7faba8884 RDMA/mlx4: Don't continue event handler after memory 
allocation failure
bc5d3e8b70d5 RDMA/siw: Fix broken RDMA Read Fence/Resume logic.
60af6e686084 IB/rdmavt: Validate remote_addr during loopback atomic tests
4bbb6e6a1caa memcg: charge fs_context and legacy_fs_context
2f837785c2ec Revert "ASoC: mediatek: Check for error clk pointer"
952717785218 block: bio-integrity: Advance seed correctly for larger 
interval sizes
d3533ee20e9a mm/kmemleak: avoid scanning potential huge holes
acc887ba8833 drm/nouveau: fix off by one in BIOS boundary checking
26b3901d20bf btrfs: fix deadlock between quota disable and qgroup rescan 
worker
e680e4d30186 ALSA: hda/realtek: Fix silent output on Gigabyte X570 Aorus 
Xtreme after reboot from Windows
7e59f0554410 ALSA: hda/realtek: Fix silent output on Gigabyte X570S Aorus 
Master (newer chipset)
d8fbf567e703 ALSA: hda/realtek: Add missing fixup-model entry for Gigabyte 
X570 ALC1220 quirks
66b5dd10c2b0 ALSA: hda/realtek: Add quirk for ASUS GU603
f2c5fde84cee ALSA: usb-audio: Simplify quirk entries with a macro
fd9a23319f16 ASoC: ops: Reject out of bounds values in snd_soc_put_xr_sx()
c33402b056de ASoC: ops: Reject out of bounds values in 
snd_soc_put_volsw_sx()
68fd71872428 ASoC: ops: Reject out of bounds values in snd_soc_put_volsw()
01baaf3bede9 audit: improve audit queue handling when "audit=1" on cmdline
b8f53f917128 Linux 5.4.177
4fc41403f0b6 af_packet: fix data-race in packet_setsockopt / 
packet_setsockopt
db6c57d2666d cpuset: Fix the bug that subpart_cpus updated wrongly in 
update_cpumask()
bd43771ee975 rtnetlink: make sure to refresh master_dev/m_ops in 
__rtnl_newlink()
b1d17e920dfc net: sched: fix use-after-free in tc_new_tfilter()
9892742f035f net: amd-xgbe: Fix skb data length underflow
28bdf65a5612 net: amd-xgbe: ensure to reset the tx_timer_active flag
f2a186a44e7e ipheth: fix EOVERFLOW in ipheth_rcvbulk_callback
0e8283cbe499 cgroup-v1: Require capabilities to set release_agent
2fd752ed77ab psi: Fix uaf issue when psi trigger is destroyed while being 
polled
464da38ba827 PCI: pciehp: Fix infinite loop in IRQ handler upon power fault

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.4.bb   |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb |  8 +++
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +--
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 72b11c3c2d..523ace3e14 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 

[OE-core] [PATCH 2/3] linux-yocto/5.4: update to v5.4.176

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

2570bb2729c7 Linux 5.4.176
5e2a4d02252f mtd: rawnand: mpc5121: Remove unused variable in 
ads5121_select_chip()
6cbf4c731d78 block: Fix wrong offset in bio_truncate()
33a9ba52d5ea fsnotify: invalidate dcache before IN_DELETE event
b52103cbb659 dt-bindings: can: tcan4x5x: fix mram-cfg RX FIFO config
e913171594ea ipv4: remove sparse error in ip_neigh_gw4()
c30ecdba9e5a ipv4: tcp: send zero IPID in SYNACK messages
51dde4ae5a37 ipv4: raw: lock the socket in raw_bind()
2d334469c29e net: hns3: handle empty unknown interrupt for VF
7afc09c8915b yam: fix a memory leak in yam_siocdevprivate()
51edc483af6c drm/msm/hdmi: Fix missing put_device() call in msm_hdmi_get_phy
a15ed3e9887f ibmvnic: don't spin in tasklet
c09702f43a6a ibmvnic: init ->running_cap_crqs early
86217a4ebd18 hwmon: (lm90) Mark alert as broken for MAX6654
18684bb996f3 rxrpc: Adjust retransmission backoff
f39027cbada4 phylib: fix potential use-after-free
218cccb52124 net: phy: broadcom: hook up soft_reset for BCM54616S
0d26470b25d2 netfilter: conntrack: don't increment invalid counter on 
NF_REPEAT
abcb9d80a4a5 NFS: Ensure the server has an up to date ctime before renaming
30965c768217 NFS: Ensure the server has an up to date ctime before 
hardlinking
cdfaf8e985f8 ipv6: annotate accesses to fn->fn_sernum
581317b1f001 drm/msm/dsi: invalid parameter check in msm_dsi_phy_enable
b3e3d584f0f1 drm/msm/dsi: Fix missing put_device() call in dsi_get_phy
4abd2a7735e1 drm/msm: Fix wrong size calculation
9f0a6acac4a1 net-procfs: show net devices bound packet types
4fd45ff2b404 NFSv4: nfs_atomic_open() can race when looking up a 
non-regular file
0dfacee40021 NFSv4: Handle case where the lookup of a directory fails
c27abaa040f3 hwmon: (lm90) Reduce maximum conversion rate for G781
1f748455a8f0 ipv4: avoid using shared IP generator for connected sockets
ca5355771ca8 ping: fix the sk_bound_dev_if match in ping_lookup
0b567a24addc hwmon: (lm90) Mark alert as broken for MAX6680
b63031651a05 hwmon: (lm90) Mark alert as broken for MAX6646/6647/6649
e372ecd455b6 net: fix information leakage in /proc/net/ptype
20b7af413153 ipv6_tunnel: Rate limit warning messages
bf2bd892a0cb scsi: bnx2fc: Flush destroy_work queue before calling 
bnx2fc_interface_put()
d380beb5e58d rpmsg: char: Fix race between the release of rpmsg_eptdev and 
cdev
da27b834c1e0 rpmsg: char: Fix race between the release of rpmsg_ctrldev and 
cdev
cb24af19e5a7 i40e: fix unsigned stat widths
be6998f232b8 i40e: Fix queues reservation for XDP
b16f1a078d63 i40e: Fix issue when maximum queues is exceeded
f18aadbdf6ad i40e: Increase delay to 1 s after global EMP reset
7e94539448ed powerpc/32: Fix boot failure with GCC latent entropy plugin
ff19d70b665d net: sfp: ignore disabled SFP node
5ede72d48cab ucsi_ccg: Check DEV_INT bit only when starting CCG4
3922b6e1c9ea usb: typec: tcpm: Do not disconnect while receiving VBUS off
9c61fce322ac USB: core: Fix hang in usb_kill_urb by adding memory barriers
4fc6519bdecb usb: gadget: f_sourcesink: Fix isoc transfer for 
USB_SPEED_SUPER_PLUS
64e671a22163 usb: common: ulpi: Fix crash in ulpi_match()
d66dc656c5f9 usb-storage: Add unusual-devs entry for VL817 USB-SATA bridge
a06cba5ad125 tty: Add support for Brainboxes UC cards.
f5e6c946732a tty: n_gsm: fix SW flow control encoding/handling
05b33011 serial: stm32: fix software flow control transfer
0b92eda2d801 serial: 8250: of: Fix mapped region size when using reg-offset 
property
2bf7dee6f423 netfilter: nft_payload: do not update layer 4 checksum when 
mangling fragments
a6d588572568 arm64: errata: Fix exec handling in erratum 1418040 workaround
5cbcd1f5a20a drm/etnaviv: relax submit size limits
5463cfd83397 fsnotify: fix fsnotify hooks in pseudo filesystems
1614bd844eef tracing: Don't inc err_log entry count if entry allocation 
fails
8a8878ebb596 tracing/histogram: Fix a potential memory leak for kstrdup()
73578a9b2b72 PM: wakeup: simplify the output logic of pm_show_wakelocks()
31136e5467f3 udf: Fix NULL ptr deref when converting from inline format
86bcc670d300 udf: Restore i_lenAlloc when inode expansion fails
c54445af64ca scsi: zfcp: Fix failed recovery on gone remote port with 
non-NPIV FCP devices
4d041e75c4c4 s390/hypfs: include z/VM guests with access control group set
835d37068525 Bluetooth: refactor malicious adv data check
7cdf2951f80d Linux 5.4.175
84b1259fe36a drm/vmwgfx: Fix stale file descriptors on failed usercopy
16895e4eac36 select: Fix indefinitely sleeping task in 
poll_schedule_timeout()
53d5b08d8e98 mmc: sdhci-esdhc-imx: disable CMDQ support
c3fa7ce43cdd ARM: dts: gpio-ranges property is now required
   

[OE-core] [PATCH 1/3] linux-yocto/5.4: update to v5.4.173

[Bruce Ashfield]

From: Bruce Ashfield 

Updating linux-yocto/5.4 to the latest korg -stable release that comprises
the following commits:

4aa2e7393e14 Linux 5.4.173
e245aaefef39 ARM: 9025/1: Kconfig: CPU_BIG_ENDIAN depends on !LD_IS_LLD
d40f6eeaf513 mtd: fixup CFI on ixp4xx
1451deb164e1 ALSA: hda/realtek - Fix silent output on Gigabyte X570 Aorus 
Master after reboot from Windows
7b98f61b8388 KVM: x86: remove PMU FIXED_CTR3 from msrs_to_save_all
5c69ba9e80f0 firmware: qemu_fw_cfg: fix kobject leak in probe error path
1cc36ed56138 firmware: qemu_fw_cfg: fix NULL-pointer deref on duplicate 
entries
b543e4141570 firmware: qemu_fw_cfg: fix sysfs information leak
b25e9ef29d8f rtlwifi: rtl8192cu: Fix WARNING when calling 
local_irq_restore() with interrupts enabled
8716657b1b4b media: uvcvideo: fix division by zero at stream start
70ae85ca124e KVM: s390: Clarify SIGP orders versus STOP/RESTART
9b45f2007ea3 perf: Protect perf_guest_cbs with RCU
bd2aed0464ae vfs: fs_context: fix up param length parsing in 
legacy_parse_param
c2f067d4ad4a orangefs: Fix the size of a memory allocation in 
orangefs_bufmap_alloc()
5d6af67307e8 devtmpfs regression fix: reconfigure on each mount
c117b116e6b3 kbuild: Add $(KBUILD_HOSTLDFLAGS) to 'has_libelf' test

Signed-off-by: Bruce Ashfield 
---
 .../linux/linux-yocto-rt_5.4.bb   |  6 ++---
 .../linux/linux-yocto-tiny_5.4.bb |  8 +++
 meta/recipes-kernel/linux/linux-yocto_5.4.bb  | 22 +--
 3 files changed, 18 insertions(+), 18 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
index 9e8281c7a1..8e5a0ae5e0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.4.bb
@@ -11,13 +11,13 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "e92d76afe6d8592917c0e7b948912c085e661df2"
-SRCREV_meta ?= "98cce1c95fcc9a26965cbc5f038fd71d53c387c8"
+SRCREV_machine ?= "04f6e2728373decb06b2c159cdf599c8813a7ea2"
+SRCREV_meta ?= "9e6e627445612ea0b6cc514bcdb879de3999f175"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.4;destsuffix=${KMETA}"
 
-LINUX_VERSION ?= "5.4.172"
+LINUX_VERSION ?= "5.4.173"
 
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
index a75570df93..53f85c8cd4 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.4.bb
@@ -6,7 +6,7 @@ KCONFIG_MODE = "--allnoconfig"
 
 require recipes-kernel/linux/linux-yocto.inc
 
-LINUX_VERSION ?= "5.4.172"
+LINUX_VERSION ?= "5.4.173"
 LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine_qemuarm ?= "10b4756eee78aa43ff9ed64da700ec6e8d97ff22"
-SRCREV_machine ?= "6ab93fdc53b64e146e4f16363375c1beb37b82e4"
-SRCREV_meta ?= "98cce1c95fcc9a26965cbc5f038fd71d53c387c8"
+SRCREV_machine_qemuarm ?= "dd1d37cf1243bb0194f63992294c386b91b883ee"
+SRCREV_machine ?= "149a477216fedee100a2a7c749d7876a5af18c3d"
+SRCREV_meta ?= "9e6e627445612ea0b6cc514bcdb879de3999f175"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.4.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
index 2d7f7559e5..ad22072ddf 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.4.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.4.bb
@@ -12,16 +12,16 @@ KBRANCH_qemux86  ?= "v5.4/standard/base"
 KBRANCH_qemux86-64 ?= "v5.4/standard/base"
 KBRANCH_qemumips64 ?= "v5.4/standard/mti-malta64"
 
-SRCREV_machine_qemuarm ?= "8de1da3dc354dedef2e435e694eec6d6e72c9822"
-SRCREV_machine_qemuarm64 ?= "eed7c0a64f3a7a91a130bc2e507304dc8b446a31"
-SRCREV_machine_qemumips ?= "996a9660e4fab70db5cecec9c831141cd03c3d36"
-SRCREV_machine_qemuppc ?= "0197cf5754b1bd4eb035c342af9cc27e8c3339ca"
-SRCREV_machine_qemuriscv64 ?= "c6b015510134942076c0e111e56357656acf3dd5"
-SRCREV_machine_qemux86 ?= "c6b015510134942076c0e111e56357656acf3dd5"
-SRCREV_machine_qemux86-64 ?= "c6b015510134942076c0e111e56357656acf3dd5"
-SRCREV_machine_qemumips64 ?= "fe2769a7c268ed224ec70fd2aaab850e4eef70dc"
-SRCREV_machine ?= "c6b015510134942076c0e111e56357656acf3dd5"
-SRCREV_meta ?= "98cce1c95fcc9a26965cbc5f038fd71d53c387c8"
+SRCREV_machine_qemuarm ?= "7d8ca1d1b0891c023c74d79ea39e045d1a794077"
+SRCREV_machine_qemuarm64 ?= "79e8b8d059d36f1c2e7e20e38f883ea8c7381ffa"
+SRCREV_machine_qemumips ?= "bed90b69d8120029e8b362166c11437a257b9fdc"

Re: [OE-core] [PATCH] wget.py: use a longer timeout in checkstatus()

[Alexander Kanavin]

Wrong list, resending.

Alex

On Wed, 9 Feb 2022 at 22:21, Alexander Kanavin via
lists.openembedded.org 
wrote:
>
> The addition of 30 second timeout is recent [1], and has
> proved not long enough with the AB server when mass-checking
> for sstate item availability, resulting in timeout errors with
> extensible SDKs[2].
>
> [1]
> https://git.yoctoproject.org/poky/commit/?id=2c46245f449d2716566ef668da0bf48f2109643a
> [2]
> https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4710/steps/16/logs/stdio
>
> Signed-off-by: Alexander Kanavin 
> ---
>  bitbake/lib/bb/fetch2/wget.py | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bitbake/lib/bb/fetch2/wget.py b/bitbake/lib/bb/fetch2/wget.py
> index 253cabce75..2a7592ae5f 100644
> --- a/bitbake/lib/bb/fetch2/wget.py
> +++ b/bitbake/lib/bb/fetch2/wget.py
> @@ -366,7 +366,7 @@ class Wget(FetchMethod):
>  except (TypeError, ImportError, IOError, 
> netrc.NetrcParseError):
>  pass
>
> -with opener.open(r, timeout=30) as response:
> +with opener.open(r, timeout=300) as response:
>  pass
>  except urllib.error.URLError as e:
>  if try_again:
> --
> 2.20.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161591): 
https://lists.openembedded.org/g/openembedded-core/message/161591
Mute This Topic: https://lists.openembedded.org/mt/89032073/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] wget.py: use a longer timeout in checkstatus()

[Alexander Kanavin]

The addition of 30 second timeout is recent [1], and has
proved not long enough with the AB server when mass-checking
for sstate item availability, resulting in timeout errors with
extensible SDKs[2].

[1]
https://git.yoctoproject.org/poky/commit/?id=2c46245f449d2716566ef668da0bf48f2109643a
[2]
https://autobuilder.yoctoproject.org/typhoon/#/builders/53/builds/4710/steps/16/logs/stdio

Signed-off-by: Alexander Kanavin 
---
 bitbake/lib/bb/fetch2/wget.py | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/bitbake/lib/bb/fetch2/wget.py b/bitbake/lib/bb/fetch2/wget.py
index 253cabce75..2a7592ae5f 100644
--- a/bitbake/lib/bb/fetch2/wget.py
+++ b/bitbake/lib/bb/fetch2/wget.py
@@ -366,7 +366,7 @@ class Wget(FetchMethod):
 except (TypeError, ImportError, IOError, 
netrc.NetrcParseError):
 pass
 
-with opener.open(r, timeout=30) as response:
+with opener.open(r, timeout=300) as response:
 pass
 except urllib.error.URLError as e:
 if try_again:
-- 
2.20.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161590): 
https://lists.openembedded.org/g/openembedded-core/message/161590
Mute This Topic: https://lists.openembedded.org/mt/89032073/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] man-db: upgrade 2.9.4 -> 2.10.0

[Khem Raj]

This is failing on musl see
https://errors.yoctoproject.org/Errors/Details/624476/

On Tue, Feb 8, 2022 at 12:29 AM wangmy  wrote:
>
> License-Update:
> ==
>  COPYING : "GNU Library" changed to "GNU Lesser"
>  format changed
>  COPYING.LIB : "51 Franklin St" changed to "51 Franklin Street"
>format changed
>
> Signed-off-by: Wang Mingyu 
> ---
>  .../man-db/{man-db_2.9.4.bb => man-db_2.10.0.bb}| 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>  rename meta/recipes-extended/man-db/{man-db_2.9.4.bb => man-db_2.10.0.bb} 
> (90%)
>
> diff --git a/meta/recipes-extended/man-db/man-db_2.9.4.bb 
> b/meta/recipes-extended/man-db/man-db_2.10.0.bb
> similarity index 90%
> rename from meta/recipes-extended/man-db/man-db_2.9.4.bb
> rename to meta/recipes-extended/man-db/man-db_2.10.0.bb
> index f97974abb8..6a8ac2e3e3 100644
> --- a/meta/recipes-extended/man-db/man-db_2.9.4.bb
> +++ b/meta/recipes-extended/man-db/man-db_2.10.0.bb
> @@ -2,13 +2,13 @@ SUMMARY = "An implementation of the standard Unix 
> documentation system accessed
>  HOMEPAGE = "http://man-db.nongnu.org/;
>  DESCRIPTION = "man-db is an implementation of the standard Unix 
> documentation system accessed using the man command. It uses a Berkeley DB 
> database in place of the traditional flat-text whatis databases."
>  LICENSE = "LGPLv2.1 & GPLv2"
> -LIC_FILES_CHKSUM = 
> "file://docs/COPYING.LIB;md5=a6f89e2100d9b6cdffcea4f398e37343 \
> -file://docs/COPYING;md5=eb723b61539feef013de476e68b5c50a"
> +LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c \
> +file://COPYING;md5=b234ee4d69f5fce4486a80fdaf4a4263"
>
>  SRC_URI = "${SAVANNAH_NONGNU_MIRROR}/man-db/man-db-${PV}.tar.xz \
> file://99_mandb \
> file://man_db.conf-avoid-multilib-install-file-conflict.patch"
> -SRC_URI[sha256sum] = 
> "b66c99edfad16ad928c889f87cf76380263c1609323c280b3a9e6963fdb16756"
> +SRC_URI[sha256sum] = 
> "0a8629022f7117dc7fc6473c6fdb14913b24b106059bb056abee87dbd6070c79"
>
>  # remove at next version upgrade or when output changes
>  PR = "r1"
> --
> 2.25.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161589): 
https://lists.openembedded.org/g/openembedded-core/message/161589
Mute This Topic: https://lists.openembedded.org/mt/88992456/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Bruce Ashfield]

On Wed, Feb 9, 2022 at 2:13 PM Richard Purdie
 wrote:
>
> On Wed, 2022-02-09 at 12:36 -0500, Bruce Ashfield wrote:
> > On Wed, Feb 9, 2022 at 12:30 PM Ross Burton  wrote:
> > >
> > > Currently each split-out kernel module RDEPENDS on the top-level kernel
> > > package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
> > > correct, as modules obviously need their matching kernel, there are many
> > > situations where the kernel is provided out-of-band and forcing the
> > > kernel in via RDEPENDS in the wrong thing to do, for example an
> > > initramfs really shouldn't contain a kernel image, but can contain
> > > kernel modules.
> > >
> > > Change the module splitting logic to use RRECOMMENDS instead of
> > > RDEPENDS, and tighten the dependency to kernel-image instead of kernel
> > > to pull in just the image, which also means PACKAGE_EXCLUDE =
> > > "kernel-image-*" is sufficient to ensure the image doesn't get pulled
> > > into an image.
> > >
> >
> > As much as I hate to suggest it, I think the strength of the image
> > dependency needs to be configurable. I know of situations were
> > rrecommends are disabled AND they use quite a few out of tree
> > modules. While I can't say that they are counting on RDEPENDS
> > heavily in this situation, I also can't rule it out .. so this is a breaking
> > change in behaviour for those configurations.
> >
> > That being said, if RP doesn't want/like a conditional at this particular
> > spot, I can understand that as well .. and am happy to be ignored
> > in that case :)
>
> Isn't there a case where the main kernel "image" package is empty so you just
> have to break the dependency at the main image level rather than messing with
> the modules? or am I half remembering something badly?

I've always just used this (from kernel.bbclass):

# Allow machines to override this dependency if kernel image files are
# not wanted in images as standard
RDEPENDS:${KERNEL_PACKAGE_NAME}-base ?= "${KERNEL_PACKAGE_NAME}-image
(= ${EXTENDPKGV})"

Maybe that's the one you are remembering ?

Bruce

>
> Cheers,
>
> Richard
>


-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161588): 
https://lists.openembedded.org/g/openembedded-core/message/161588
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Richard Purdie]

On Wed, 2022-02-09 at 12:36 -0500, Bruce Ashfield wrote:
> On Wed, Feb 9, 2022 at 12:30 PM Ross Burton  wrote:
> > 
> > Currently each split-out kernel module RDEPENDS on the top-level kernel
> > package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
> > correct, as modules obviously need their matching kernel, there are many
> > situations where the kernel is provided out-of-band and forcing the
> > kernel in via RDEPENDS in the wrong thing to do, for example an
> > initramfs really shouldn't contain a kernel image, but can contain
> > kernel modules.
> > 
> > Change the module splitting logic to use RRECOMMENDS instead of
> > RDEPENDS, and tighten the dependency to kernel-image instead of kernel
> > to pull in just the image, which also means PACKAGE_EXCLUDE =
> > "kernel-image-*" is sufficient to ensure the image doesn't get pulled
> > into an image.
> > 
> 
> As much as I hate to suggest it, I think the strength of the image
> dependency needs to be configurable. I know of situations were
> rrecommends are disabled AND they use quite a few out of tree
> modules. While I can't say that they are counting on RDEPENDS
> heavily in this situation, I also can't rule it out .. so this is a breaking
> change in behaviour for those configurations.
> 
> That being said, if RP doesn't want/like a conditional at this particular
> spot, I can understand that as well .. and am happy to be ignored
> in that case :)

Isn't there a case where the main kernel "image" package is empty so you just
have to break the dependency at the main image level rather than messing with
the modules? or am I half remembering something badly?

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161587): 
https://lists.openembedded.org/g/openembedded-core/message/161587
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0

[Peter Kjellerstedt]

> -Original Message-
> From: openembedded-core@lists.openembedded.org  c...@lists.openembedded.org> On Behalf Of Jose Quaresma
> Sent: den 7 februari 2022 02:08
> To: openembedded-core@lists.openembedded.org
> Cc: Jose Quaresma 
> Subject: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0
> 
> - License update:
>   The code actually is LGPLv2.1 but the COPYING file is wrong.
>   
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/d157b23fb0ce175b167611a4cb019599d9017042

Since the COPYING file for the GStreamer sub-projects now states 
that the used license is LGPL-2.1, shouldn't the LICENSE for these 
recipes be updated to say "LGPL-2.1-or-later"?

As for -bad and -ugly, they should really have individual LICENSE:foo 
for each generated package, so that only the packages that are affected 
by the GPL license includes it, and the others only specify LGPL.

//Peter


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161586): 
https://lists.openembedded.org/g/openembedded-core/message/161586
Mute This Topic: https://lists.openembedded.org/mt/88962313/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Bruce Ashfield]

On Wed, Feb 9, 2022 at 12:57 PM Khem Raj  wrote:
>
> On Wed, Feb 9, 2022 at 9:36 AM Bruce Ashfield  
> wrote:
> >
> > On Wed, Feb 9, 2022 at 12:30 PM Ross Burton  wrote:
> > >
> > > Currently each split-out kernel module RDEPENDS on the top-level kernel
> > > package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
> > > correct, as modules obviously need their matching kernel, there are many
> > > situations where the kernel is provided out-of-band and forcing the
> > > kernel in via RDEPENDS in the wrong thing to do, for example an
> > > initramfs really shouldn't contain a kernel image, but can contain
> > > kernel modules.
> > >
> > > Change the module splitting logic to use RRECOMMENDS instead of
> > > RDEPENDS, and tighten the dependency to kernel-image instead of kernel
> > > to pull in just the image, which also means PACKAGE_EXCLUDE =
> > > "kernel-image-*" is sufficient to ensure the image doesn't get pulled
> > > into an image.
> > >
> >
> > As much as I hate to suggest it, I think the strength of the image
> > dependency needs to be configurable. I know of situations were
> > rrecommends are disabled AND they use quite a few out of tree
> > modules. While I can't say that they are counting on RDEPENDS
> > heavily in this situation, I also can't rule it out .. so this is a breaking
> > change in behaviour for those configurations.
> >
> > That being said, if RP doesn't want/like a conditional at this particular
> > spot, I can understand that as well .. and am happy to be ignored
> > in that case :)
>
> I see that this change eases container image generation. I would be inclined
> to support this change.

To be clear, i think the change is fine as well .. I'm simply saying,
it should be configurable, as we are potential breaking the existing
use case for another.

Cheers,

Bruce

>
> >
> > Bruce
> >
> > > Signed-off-by: Ross Burton 
> > > ---
> > >  meta/classes/kernel-module-split.bbclass | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/meta/classes/kernel-module-split.bbclass 
> > > b/meta/classes/kernel-module-split.bbclass
> > > index a29c294810e..4429fee4b51 100644
> > > --- a/meta/classes/kernel-module-split.bbclass
> > > +++ b/meta/classes/kernel-module-split.bbclass
> > > @@ -175,7 +175,7 @@ python split_kernel_module_packages () {
> > >  module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
> > >  module_pattern = module_pattern_prefix + kernel_package_name + 
> > > '-module-%s' + module_pattern_suffix
> > >
> > > -modules = do_split_packages(d, 
> > > root='${nonarch_base_libdir}/modules', file_regex=module_regex, 
> > > output_pattern=module_pattern, description='%s kernel module', 
> > > postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
> > > extra_depends='%s-%s' % (kernel_package_name, kernel_version))
> > > +modules = do_split_packages(d, 
> > > root='${nonarch_base_libdir}/modules', file_regex=module_regex, 
> > > output_pattern=module_pattern, description='%s kernel module', 
> > > postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
> > > extra_recommends='%s-image-%s' % (kernel_package_name, kernel_version))
> > >  if modules:
> > >  d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
> > >
> > > --
> > > 2.25.1
> > >
> >
> >
> > --
> > - Thou shalt not follow the NULL pointer, for chaos and madness await
> > thee at its end
> > - "Use the force Harry" - Gandalf, Star Trek II
> >
> > 
> >



-- 
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161585): 
https://lists.openembedded.org/g/openembedded-core/message/161585
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 4/5] qemuarmv5: use arm-versatile-926ejs KMACHINE and add more virtio devices

[Khem Raj]

On Wed, Feb 9, 2022 at 9:30 AM Jon Mason  wrote:
>
> Use the Arm Versatile 926 kernel configs and round out all of the virtio
> interfaces to match other QEMU machines.
>
> Signed-off-by: Jon Mason 
> ---
>  meta/conf/machine/qemuarm64.conf |  8 
>  meta/conf/machine/qemuarmv5.conf | 11 +--
>  2 files changed, 13 insertions(+), 6 deletions(-)
>
> diff --git a/meta/conf/machine/qemuarm64.conf 
> b/meta/conf/machine/qemuarm64.conf
> index f24515216838..ffc51c803fa7 100644
> --- a/meta/conf/machine/qemuarm64.conf
> +++ b/meta/conf/machine/qemuarm64.conf
> @@ -23,9 +23,9 @@ QB_GRAPHICS = "-device virtio-gpu-pci"
>  QB_OPT_APPEND = "-device qemu-xhci -device usb-tablet -device usb-kbd"
>  # Virtio Networking support
>  QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
> -QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
> +QB_NETWORK_DEVICE = "-device virtio-net-pci,netdev=net0,mac=@MAC@"
>  # Virtio block device
> -QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device 
> virtio-blk-device,drive=disk0"
> +QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device 
> virtio-blk-pci,drive=disk0"
>  # Virtio serial console
> -QB_SERIAL_OPT = "-device virtio-serial-device -chardev null,id=virtcon 
> -device virtconsole,chardev=virtcon"
> -QB_TCPSERIAL_OPT = "-device virtio-serial-device -chardev 
> socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
> virtconsole,chardev=virtcon"
> +QB_SERIAL_OPT = "-device virtio-serial-pci -chardev null,id=virtcon -device 
> virtconsole,chardev=virtcon"
> +QB_TCPSERIAL_OPT = "-device virtio-serial-pci -chardev 
> socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
> virtconsole,chardev=virtcon"
> diff --git a/meta/conf/machine/qemuarmv5.conf 
> b/meta/conf/machine/qemuarmv5.conf
> index 2dad504c9932..863379ff4961 100644
> --- a/meta/conf/machine/qemuarmv5.conf
> +++ b/meta/conf/machine/qemuarmv5.conf
> @@ -13,9 +13,16 @@ SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;ttyAMA1"
>  QB_SYSTEM_NAME = "qemu-system-arm"
>  QB_MACHINE = "-machine versatilepb"
>  QB_KERNEL_CMDLINE_APPEND = "vmalloc=256"
> +# For graphics to work we need to define the VGA device as well as the 
> necessary USB devices
>  QB_GRAPHICS = "-device virtio-gpu-pci"
>  QB_OPT_APPEND = "-device qemu-xhci -device usb-tablet -device usb-kbd"
> -PREFERRED_VERSION_linux-yocto ??= "5.15%"

is this intentional change ?

> +# Virtio Networking support
> +QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
> +QB_NETWORK_DEVICE = "-device virtio-net-pci,netdev=net0,mac=@MAC@"
> +# Virtio serial console
> +QB_SERIAL_OPT = "-device virtio-serial-pci -chardev null,id=virtcon -device 
> virtconsole,chardev=virtcon"
> +QB_TCPSERIAL_OPT = "-device virtio-serial-pci -chardev 
> socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
> virtconsole,chardev=virtcon"
> +
>  QB_DTB = "${@oe.utils.version_less_or_equal('PREFERRED_VERSION_linux-yocto', 
> '4.7', '', 'zImage-versatile-pb.dtb', d)}"
>
> -KMACHINE:qemuarmv5 = "qemuarm"
> +KMACHINE:qemuarmv5 = "arm-versatile-926ejs"
> --
> 2.30.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161584): 
https://lists.openembedded.org/g/openembedded-core/message/161584
Mute This Topic: https://lists.openembedded.org/mt/89026731/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 5/5] poky-tiny: enable qemuarmv5/qemuarm64 and cleanups

[Khem Raj]

On Wed, Feb 9, 2022 at 9:30 AM Jon Mason  wrote:
>
> Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
> entries, as it should be generic now.
>
> Signed-off-by: Jon Mason 
> ---
>  meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 5 ++---
>  1 file changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb 
> b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
> index 2c81e3c00506..e146ecddceb9 100644
> --- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
> @@ -1,5 +1,4 @@
>  KBRANCH ?= "v5.15/standard/tiny/base"
> -KBRANCH:qemuarm  ?= "v5.15/standard/tiny/arm-versatile-926ejs"
>
>  LINUX_KERNEL_TYPE = "tiny"
>  KCONFIG_MODE = "--allnoconfig"
> @@ -15,16 +14,16 @@ DEPENDS += "openssl-native util-linux-native"
>  KMETA = "kernel-meta"
>  KCONF_BSP_AUDIT_LEVEL = "2"
>
> -SRCREV_machine:qemuarm ?= "67b4c868eafbd63c437d0e79523c3bdc5f3aa834"
>  SRCREV_machine ?= "f46816a75d738acbe4b1211153badf2f8e412780"
>  SRCREV_meta ?= "26e884f8c2d22607e97900d22ad52a290f555fd7"
>
> +

spurious line :)

>  PV = "${LINUX_VERSION}+git${SRCPV}"
>
>  SRC_URI = 
> "git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \
> 
> git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
>
> -COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
> +COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm64|qemuarm|qemuarmv5"
>
>  # Functionality flags
>  KERNEL_FEATURES = ""
> --
> 2.30.2
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161583): 
https://lists.openembedded.org/g/openembedded-core/message/161583
Mute This Topic: https://lists.openembedded.org/mt/89026732/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Khem Raj]

On Wed, Feb 9, 2022 at 9:36 AM Bruce Ashfield  wrote:
>
> On Wed, Feb 9, 2022 at 12:30 PM Ross Burton  wrote:
> >
> > Currently each split-out kernel module RDEPENDS on the top-level kernel
> > package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
> > correct, as modules obviously need their matching kernel, there are many
> > situations where the kernel is provided out-of-band and forcing the
> > kernel in via RDEPENDS in the wrong thing to do, for example an
> > initramfs really shouldn't contain a kernel image, but can contain
> > kernel modules.
> >
> > Change the module splitting logic to use RRECOMMENDS instead of
> > RDEPENDS, and tighten the dependency to kernel-image instead of kernel
> > to pull in just the image, which also means PACKAGE_EXCLUDE =
> > "kernel-image-*" is sufficient to ensure the image doesn't get pulled
> > into an image.
> >
>
> As much as I hate to suggest it, I think the strength of the image
> dependency needs to be configurable. I know of situations were
> rrecommends are disabled AND they use quite a few out of tree
> modules. While I can't say that they are counting on RDEPENDS
> heavily in this situation, I also can't rule it out .. so this is a breaking
> change in behaviour for those configurations.
>
> That being said, if RP doesn't want/like a conditional at this particular
> spot, I can understand that as well .. and am happy to be ignored
> in that case :)

I see that this change eases container image generation. I would be inclined
to support this change.

>
> Bruce
>
> > Signed-off-by: Ross Burton 
> > ---
> >  meta/classes/kernel-module-split.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/meta/classes/kernel-module-split.bbclass 
> > b/meta/classes/kernel-module-split.bbclass
> > index a29c294810e..4429fee4b51 100644
> > --- a/meta/classes/kernel-module-split.bbclass
> > +++ b/meta/classes/kernel-module-split.bbclass
> > @@ -175,7 +175,7 @@ python split_kernel_module_packages () {
> >  module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
> >  module_pattern = module_pattern_prefix + kernel_package_name + 
> > '-module-%s' + module_pattern_suffix
> >
> > -modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
> > file_regex=module_regex, output_pattern=module_pattern, description='%s 
> > kernel module', postinst=postinst, postrm=postrm, recursive=True, 
> > hook=frob_metadata, extra_depends='%s-%s' % (kernel_package_name, 
> > kernel_version))
> > +modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
> > file_regex=module_regex, output_pattern=module_pattern, description='%s 
> > kernel module', postinst=postinst, postrm=postrm, recursive=True, 
> > hook=frob_metadata, extra_recommends='%s-image-%s' % (kernel_package_name, 
> > kernel_version))
> >  if modules:
> >  d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
> >
> > --
> > 2.25.1
> >
>
>
> --
> - Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end
> - "Use the force Harry" - Gandalf, Star Trek II
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161582): 
https://lists.openembedded.org/g/openembedded-core/message/161582
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] Missing python.h when building ntpsec

[Khem Raj]

On Wed, Feb 9, 2022 at 5:50 AM Mans Zigher  wrote:
>
> Hi,
>
> I am trying to backport ntpsec from master to Thud but I have
> encountered an issue where python.h is missing in the sysroot for the
> ntpsec so the configuration task is failing. The ntpsec recipe has
>
> DEPENDS += "bison-native \
> openssl \
> python3"
>
> So should that not result in python.h being included to the sysroot
> for the ntpsec? Any hints on what to look for?
>

what happens if you change python3 to python in depends

> Thanks,
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161581): 
https://lists.openembedded.org/g/openembedded-core/message/161581
Mute This Topic: https://lists.openembedded.org/mt/89021393/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] cmake: stop FetchContent from fetching content

[Khem Raj]

On 2/9/22 4:53 AM, Ross Burton wrote:

CMake includes a FetchContent module, which will download further
source code at configure time.  With the network isolation this will now
fail, but as not all environments support network isolation we can tell
cmake to not download either for extra safety.



what is cmake's default ? I think it could become a constant source of 
pain if it is not default. Since many cmake based packages might start 
to depend on it indirectly in future.



Signed-off-by: Ross Burton 
---
  meta/classes/cmake.bbclass | 1 +
  1 file changed, 1 insertion(+)

diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index 92b9197c487..fac7bbca7a3 100644
--- a/meta/classes/cmake.bbclass
+++ b/meta/classes/cmake.bbclass
@@ -189,6 +189,7 @@ cmake_do_configure() {
  -DCMAKE_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake \
  -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 \
  -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON \
+ -DFETCHCONTENT_FULLY_DISCONNECTED=ON \
  ${EXTRA_OECMAKE} \
  -Wno-dev
  }






-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161580): 
https://lists.openembedded.org/g/openembedded-core/message/161580
Mute This Topic: https://lists.openembedded.org/mt/89020454/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v4] perl: Help resolving WNOHANG and _exit in Posix module

[Khem Raj]

On Wed, Feb 9, 2022 at 5:44 AM Richard Purdie
 wrote:
>
> On Tue, 2022-02-08 at 21:15 -0800, Khem Raj wrote:
> > Signed-off-by: Khem Raj 
> > ---
> > v4: Fix filepaths in release tarballs which are different than git repo
> >
> >  ...01-ipc-force-POSIX-WNOHANG-resolving.patch | 52 +++
> >  meta/recipes-devtools/perl/perl_5.34.0.bb |  1 +
> >  2 files changed, 53 insertions(+)
> >  create mode 100644 
> > meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch
>
> As I hinted at originally, this papers over a crack and doesn't solve the real
> error:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/5042/steps/12/logs/stdio
>
> What the real error is remains unclear too :(

right, I was attempting to test if module importing/resolving was the
issue but it seems it
is not really the issue as I see below in your new logs, it means its
being resolved ok.

| Attempt to reload POSIX.pm aborted.

so I guess we still are at loss here.

>
> Cheers,
>
> Richard
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161579): 
https://lists.openembedded.org/g/openembedded-core/message/161579
Mute This Topic: https://lists.openembedded.org/mt/89016040/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Bruce Ashfield]

On Wed, Feb 9, 2022 at 12:30 PM Ross Burton  wrote:
>
> Currently each split-out kernel module RDEPENDS on the top-level kernel
> package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
> correct, as modules obviously need their matching kernel, there are many
> situations where the kernel is provided out-of-band and forcing the
> kernel in via RDEPENDS in the wrong thing to do, for example an
> initramfs really shouldn't contain a kernel image, but can contain
> kernel modules.
>
> Change the module splitting logic to use RRECOMMENDS instead of
> RDEPENDS, and tighten the dependency to kernel-image instead of kernel
> to pull in just the image, which also means PACKAGE_EXCLUDE =
> "kernel-image-*" is sufficient to ensure the image doesn't get pulled
> into an image.
>

As much as I hate to suggest it, I think the strength of the image
dependency needs to be configurable. I know of situations were
rrecommends are disabled AND they use quite a few out of tree
modules. While I can't say that they are counting on RDEPENDS
heavily in this situation, I also can't rule it out .. so this is a breaking
change in behaviour for those configurations.

That being said, if RP doesn't want/like a conditional at this particular
spot, I can understand that as well .. and am happy to be ignored
in that case :)

Bruce

> Signed-off-by: Ross Burton 
> ---
>  meta/classes/kernel-module-split.bbclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/kernel-module-split.bbclass 
> b/meta/classes/kernel-module-split.bbclass
> index a29c294810e..4429fee4b51 100644
> --- a/meta/classes/kernel-module-split.bbclass
> +++ b/meta/classes/kernel-module-split.bbclass
> @@ -175,7 +175,7 @@ python split_kernel_module_packages () {
>  module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
>  module_pattern = module_pattern_prefix + kernel_package_name + 
> '-module-%s' + module_pattern_suffix
>
> -modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
> file_regex=module_regex, output_pattern=module_pattern, description='%s 
> kernel module', postinst=postinst, postrm=postrm, recursive=True, 
> hook=frob_metadata, extra_depends='%s-%s' % (kernel_package_name, 
> kernel_version))
> +modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
> file_regex=module_regex, output_pattern=module_pattern, description='%s 
> kernel module', postinst=postinst, postrm=postrm, recursive=True, 
> hook=frob_metadata, extra_recommends='%s-image-%s' % (kernel_package_name, 
> kernel_version))
>  if modules:
>  d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
>
> --
> 2.25.1
>


--
- Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end
- "Use the force Harry" - Gandalf, Star Trek II

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161577): 
https://lists.openembedded.org/g/openembedded-core/message/161577
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v3 1/3] glibc: Upgrade to 2.35 (RFC)

[Khem Raj]

On Wed, Feb 9, 2022 at 5:48 AM Richard Purdie
 wrote:
>
> On Tue, 2022-02-08 at 14:53 -0800, Khem Raj wrote:
> > From: Richard Purdie 
> >
> > Package /usr/bin/ld.so in a separate package
> >
> > ld.so is a new tool which is added as a symlink to original dynamic
> > linker so make it available with same name across architectures which is
> > useful to leveral features like  --preload, --audit, and --list-diagnostics
> > more accessible to end users
> >
>
> There is still a QA error with this for multilib:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/4735/steps/11/logs/stdio
>

yeah, I think I needed to add multilib prefix and also rename the
symlink so they can coexist.
I have made this change and pushed the update to kraj/poky-next

> Cheers,
>
> Richard
>
>
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161578): 
https://lists.openembedded.org/g/openembedded-core/message/161578
Mute This Topic: https://lists.openembedded.org/mt/89009276/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/2] package: add extra_recommends to do_split_package()

[Ross Burton]

It may be preferrable to add RRECOMMENDS instead of RDEPENDS to each of
the split packages, so add extra_recommends to do this.

Signed-off-by: Ross Burton 
---
 meta/classes/package.bbclass | 6 +-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index f4a661ba25a..2143abca0d1 100644
--- a/meta/classes/package.bbclass
+++ b/meta/classes/package.bbclass
@@ -79,7 +79,7 @@ def legitimize_package_name(s):
 # Remaining package name validity fixes
 return s.lower().replace('_', '-').replace('@', '+').replace(',', 
'+').replace('/', '-')
 
-def do_split_packages(d, root, file_regex, output_pattern, description, 
postinst=None, recursive=False, hook=None, extra_depends=None, 
aux_files_pattern=None, postrm=None, allow_dirs=False, prepend=False, 
match_path=False, aux_files_pattern_verbatim=None, allow_links=False, 
summary=None):
+def do_split_packages(d, root, file_regex, output_pattern, description, 
postinst=None, recursive=False, hook=None, extra_depends=None, 
extra_recommends=None, aux_files_pattern=None, postrm=None, allow_dirs=False, 
prepend=False, match_path=False, aux_files_pattern_verbatim=None, 
allow_links=False, summary=None):
 """
 Used in .bb files to split up dynamically generated subpackages of a
 given package, usually plugins or modules.
@@ -108,6 +108,8 @@ def do_split_packages(d, root, file_regex, output_pattern, 
description, postinst
   all packages. The default value of None causes a
   dependency on the main package (${PN}) - if you do
   not want this, pass '' for this parameter.
+extra_recommends -- extra runtime recommends (RRECOMMENDS) to be set for
+  all packages. By default no recommends are added.
 aux_files_pattern -- extra item(s) to be added to FILES for each
   package. Can be a single string item or a list of
   strings for multiple items.  Must include %s.
@@ -222,6 +224,8 @@ def do_split_packages(d, root, file_regex, output_pattern, 
description, postinst
 d.setVar('FILES:' + pkg, oldfiles + " " + newfile)
 if extra_depends != '':
 d.appendVar('RDEPENDS:' + pkg, ' ' + extra_depends)
+if extra_recommends:
+d.appendVar('RRECOMMENDS:' + pkg, ' ' + extra_recommends)
 if not d.getVar('DESCRIPTION:' + pkg):
 d.setVar('DESCRIPTION:' + pkg, description % on)
 if not d.getVar('SUMMARY:' + pkg):
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161575): 
https://lists.openembedded.org/g/openembedded-core/message/161575
Mute This Topic: https://lists.openembedded.org/mt/89026747/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/2] kernel-module-split: modules should recommend the kernel image

[Ross Burton]

Currently each split-out kernel module RDEPENDS on the top-level kernel
package (e.g. kernel-5.15-yocto-standard). Whilst at first this seems
correct, as modules obviously need their matching kernel, there are many
situations where the kernel is provided out-of-band and forcing the
kernel in via RDEPENDS in the wrong thing to do, for example an
initramfs really shouldn't contain a kernel image, but can contain
kernel modules.

Change the module splitting logic to use RRECOMMENDS instead of
RDEPENDS, and tighten the dependency to kernel-image instead of kernel
to pull in just the image, which also means PACKAGE_EXCLUDE =
"kernel-image-*" is sufficient to ensure the image doesn't get pulled
into an image.

Signed-off-by: Ross Burton 
---
 meta/classes/kernel-module-split.bbclass | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index a29c294810e..4429fee4b51 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -175,7 +175,7 @@ python split_kernel_module_packages () {
 module_pattern_suffix = d.getVar('KERNEL_MODULE_PACKAGE_SUFFIX')
 module_pattern = module_pattern_prefix + kernel_package_name + 
'-module-%s' + module_pattern_suffix
 
-modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_depends='%s-%s' % (kernel_package_name, kernel_version))
+modules = do_split_packages(d, root='${nonarch_base_libdir}/modules', 
file_regex=module_regex, output_pattern=module_pattern, description='%s kernel 
module', postinst=postinst, postrm=postrm, recursive=True, hook=frob_metadata, 
extra_recommends='%s-image-%s' % (kernel_package_name, kernel_version))
 if modules:
 d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161576): 
https://lists.openembedded.org/g/openembedded-core/message/161576
Mute This Topic: https://lists.openembedded.org/mt/89026749/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 0/5] poky-tiny clean-ups and qemuarm fixes

[Jon Mason]

Fixes to get qemuarmv5, qemuarm64, and qemuarm working with poky-tiny
(again).  While I'm there, do some clean-ups.

This needs https://lists.yoctoproject.org/g/linux-yocto/message/10908
for qemuarm's to work.

Jon Mason (5):
  linux-yocto-dev: add qemuriscv32
  linux-yocto: Remove unnecessary commented out qemuarm entry
  qemuarm: use virtio pci interface for graphics
  qemuarmv5: use arm-versatile-926ejs KMACHINE and add more virtio
devices
  poky-tiny: enable qemuarmv5/qemuarm64 and cleanups

 meta/conf/machine/qemuarm.conf |  3 +--
 meta/conf/machine/qemuarm64.conf   |  8 
 meta/conf/machine/qemuarmv5.conf   | 11 +--
 meta/recipes-kernel/linux/linux-yocto-dev.bb   |  2 +-
 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb |  5 ++---
 meta/recipes-kernel/linux/linux-yocto_5.10.bb  |  3 ---
 meta/recipes-kernel/linux/linux-yocto_5.15.bb  |  3 ---
 7 files changed, 17 insertions(+), 18 deletions(-)

-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161569): 
https://lists.openembedded.org/g/openembedded-core/message/161569
Mute This Topic: https://lists.openembedded.org/mt/89026727/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 1/5] linux-yocto-dev: add qemuriscv32

[Jon Mason]

Signed-off-by: Jon Mason 
---
 meta/recipes-kernel/linux/linux-yocto-dev.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-dev.bb 
b/meta/recipes-kernel/linux/linux-yocto-dev.bb
index 0d946373523c..98a42235af54 100644
--- a/meta/recipes-kernel/linux/linux-yocto-dev.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-dev.bb
@@ -50,7 +50,7 @@ PACKAGECONFIG[dt-validation] = ",,python3-dtschema-native"
 # we need the wrappers if validation isn't in the packageconfig
 DEPENDS += "${@bb.utils.contains('PACKAGECONFIG', 'dt-validation', '', 
'python3-dtschema-wrapper-native', d)}"
 
-COMPATIBLE_MACHINE = 
"(qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv64)"
+COMPATIBLE_MACHINE = 
"(qemuarm|qemux86|qemuppc|qemumips|qemumips64|qemux86-64|qemuriscv32|qemuriscv64)"
 
 KERNEL_DEVICETREE:qemuarmv5 = "versatile-pb.dtb"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161570): 
https://lists.openembedded.org/g/openembedded-core/message/161570
Mute This Topic: https://lists.openembedded.org/mt/89026728/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 5/5] poky-tiny: enable qemuarmv5/qemuarm64 and cleanups

[Jon Mason]

Add support for qemuarmv5 and qemuarm64, and remove qemuarm specific
entries, as it should be generic now.

Signed-off-by: Jon Mason 
---
 meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
index 2c81e3c00506..e146ecddceb9 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.15.bb
@@ -1,5 +1,4 @@
 KBRANCH ?= "v5.15/standard/tiny/base"
-KBRANCH:qemuarm  ?= "v5.15/standard/tiny/arm-versatile-926ejs"
 
 LINUX_KERNEL_TYPE = "tiny"
 KCONFIG_MODE = "--allnoconfig"
@@ -15,16 +14,16 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine:qemuarm ?= "67b4c868eafbd63c437d0e79523c3bdc5f3aa834"
 SRCREV_machine ?= "f46816a75d738acbe4b1211153badf2f8e412780"
 SRCREV_meta ?= "26e884f8c2d22607e97900d22ad52a290f555fd7"
 
+
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;branch=${KBRANCH};name=machine \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
 
-COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm|qemuarmv5"
+COMPATIBLE_MACHINE = "qemux86|qemux86-64|qemuarm64|qemuarm|qemuarmv5"
 
 # Functionality flags
 KERNEL_FEATURES = ""
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161574): 
https://lists.openembedded.org/g/openembedded-core/message/161574
Mute This Topic: https://lists.openembedded.org/mt/89026732/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 4/5] qemuarmv5: use arm-versatile-926ejs KMACHINE and add more virtio devices

[Jon Mason]

Use the Arm Versatile 926 kernel configs and round out all of the virtio
interfaces to match other QEMU machines.

Signed-off-by: Jon Mason 
---
 meta/conf/machine/qemuarm64.conf |  8 
 meta/conf/machine/qemuarmv5.conf | 11 +--
 2 files changed, 13 insertions(+), 6 deletions(-)

diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index f24515216838..ffc51c803fa7 100644
--- a/meta/conf/machine/qemuarm64.conf
+++ b/meta/conf/machine/qemuarm64.conf
@@ -23,9 +23,9 @@ QB_GRAPHICS = "-device virtio-gpu-pci"
 QB_OPT_APPEND = "-device qemu-xhci -device usb-tablet -device usb-kbd"
 # Virtio Networking support
 QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
-QB_NETWORK_DEVICE = "-device virtio-net-device,netdev=net0,mac=@MAC@"
+QB_NETWORK_DEVICE = "-device virtio-net-pci,netdev=net0,mac=@MAC@"
 # Virtio block device
-QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device 
virtio-blk-device,drive=disk0"
+QB_ROOTFS_OPT = "-drive id=disk0,file=@ROOTFS@,if=none,format=raw -device 
virtio-blk-pci,drive=disk0"
 # Virtio serial console
-QB_SERIAL_OPT = "-device virtio-serial-device -chardev null,id=virtcon -device 
virtconsole,chardev=virtcon"
-QB_TCPSERIAL_OPT = "-device virtio-serial-device -chardev 
socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
virtconsole,chardev=virtcon"
+QB_SERIAL_OPT = "-device virtio-serial-pci -chardev null,id=virtcon -device 
virtconsole,chardev=virtcon"
+QB_TCPSERIAL_OPT = "-device virtio-serial-pci -chardev 
socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
virtconsole,chardev=virtcon"
diff --git a/meta/conf/machine/qemuarmv5.conf b/meta/conf/machine/qemuarmv5.conf
index 2dad504c9932..863379ff4961 100644
--- a/meta/conf/machine/qemuarmv5.conf
+++ b/meta/conf/machine/qemuarmv5.conf
@@ -13,9 +13,16 @@ SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;ttyAMA1"
 QB_SYSTEM_NAME = "qemu-system-arm"
 QB_MACHINE = "-machine versatilepb"
 QB_KERNEL_CMDLINE_APPEND = "vmalloc=256"
+# For graphics to work we need to define the VGA device as well as the 
necessary USB devices
 QB_GRAPHICS = "-device virtio-gpu-pci"
 QB_OPT_APPEND = "-device qemu-xhci -device usb-tablet -device usb-kbd"
-PREFERRED_VERSION_linux-yocto ??= "5.15%"
+# Virtio Networking support
+QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
+QB_NETWORK_DEVICE = "-device virtio-net-pci,netdev=net0,mac=@MAC@"
+# Virtio serial console
+QB_SERIAL_OPT = "-device virtio-serial-pci -chardev null,id=virtcon -device 
virtconsole,chardev=virtcon"
+QB_TCPSERIAL_OPT = "-device virtio-serial-pci -chardev 
socket,id=virtcon,port=@PORT@,host=127.0.0.1 -device 
virtconsole,chardev=virtcon"
+
 QB_DTB = "${@oe.utils.version_less_or_equal('PREFERRED_VERSION_linux-yocto', 
'4.7', '', 'zImage-versatile-pb.dtb', d)}"
 
-KMACHINE:qemuarmv5 = "qemuarm"
+KMACHINE:qemuarmv5 = "arm-versatile-926ejs"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161573): 
https://lists.openembedded.org/g/openembedded-core/message/161573
Mute This Topic: https://lists.openembedded.org/mt/89026731/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 2/5] linux-yocto: Remove unnecessary commented out qemuarm entry

[Jon Mason]

The line in question is already in place in qemuarm.conf.  Remove it
from here, as it is not necessary and references an older kernel.

Signed-off-by: Jon Mason 
---
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 3 ---
 meta/recipes-kernel/linux/linux-yocto_5.15.bb | 3 ---
 2 files changed, 6 deletions(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto_5.10.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
index 3a0a43bc0b90..1f0f2977c06d 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.10.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.10.bb
@@ -25,9 +25,6 @@ SRCREV_machine:qemumips64 ?= 
"b668a352c94a8c29e585608e8302cacb1350f5ed"
 SRCREV_machine ?= "a1bbb29fe30c94c21309aa8b8c0d06fa12f3368d"
 SRCREV_meta ?= "7df27e6d296dfa16f289883c0661eed45059360c"
 
-# remap qemuarm to qemuarma15 for the 5.8 kernel
-# KMACHINE:qemuarm ?= "qemuarma15"
-
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH}; \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.10;destsuffix=${KMETA}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.15.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
index ea10de30cd2f..ce66ddc75cd5 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.15.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.15.bb
@@ -35,9 +35,6 @@ SRCREV_machine:class-devupstream ?= 
"63dcc388662c3562de94d69bfa771ae4cd29b79f"
 PN:class-devupstream = "linux-yocto-upstream"
 KBRANCH:class-devupstream = "v5.15/base"
 
-# remap qemuarm to qemuarma15 for the 5.8 kernel
-# KMACHINE:qemuarm ?= "qemuarma15"
-
 SRC_URI = 
"git://git.yoctoproject.org/linux-yocto.git;name=machine;branch=${KBRANCH}; \

git://git.yoctoproject.org/yocto-kernel-cache;type=kmeta;name=meta;branch=yocto-5.15;destsuffix=${KMETA}"
 
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161571): 
https://lists.openembedded.org/g/openembedded-core/message/161571
Mute This Topic: https://lists.openembedded.org/mt/89026729/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH 3/5] qemuarm: use virtio pci interface for graphics

[Jon Mason]

For uniformity, use the virtio pci interface (which all the other
virtio devices are using for this machine).

Signed-off-by: Jon Mason 
---
 meta/conf/machine/qemuarm.conf | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index 1bd4e3e154fc..12da1557efff 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -17,10 +17,9 @@ QB_SYSTEM_NAME = "qemu-system-arm"
 QB_MACHINE = "-machine virt,highmem=off"
 QB_CPU = "-cpu cortex-a15"
 QB_SMP = "-smp 4"
-# Standard Serial console
 QB_KERNEL_CMDLINE_APPEND = "vmalloc=256"
 # For graphics to work we need to define the VGA device as well as the 
necessary USB devices
-QB_GRAPHICS = "-device virtio-gpu-pci"
+QB_GRAPHICS = "-device virtio-gpu-device"
 QB_OPT_APPEND = "-device qemu-xhci -device usb-tablet -device usb-kbd"
 # Virtio Networking support
 QB_TAP_OPT = "-netdev tap,id=net0,ifname=@TAP@,script=no,downscript=no"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161572): 
https://lists.openembedded.org/g/openembedded-core/message/161572
Mute This Topic: https://lists.openembedded.org/mt/89026730/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [PATCH] qemuboot: Fix build error if UNINATIVE_LOADER is unset

[Zoltan Boszormenyi via lists.openembedded.org]

From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_write_qemuboot_conf(d)
 0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
141, function: do_write_qemuboot_conf
 0137:else:
 0138:val = d.getVar(k)
 0139:# we only want to write out relative paths so that we can 
relocate images
 0140:# and still run them
 *** 0141:if val.startswith(topdir):
 0142:val = os.path.relpath(val, finalpath)
 0143:cf.set('config_bsp', k, '%s' % val)
 0144:
 0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a 
symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None, which may happen for k = "UNINATIVE_LOADER".

Signed-off-by: Zoltán Böszörményi 
---
 meta/classes/qemuboot.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 229bd88527..755d49acd6 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {

'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
 else:
 val = d.getVar(k)
+if val is None:
+continue
 # we only want to write out relative paths so that we can relocate 
images
 # and still run them
 if val.startswith(topdir):
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161568): 
https://lists.openembedded.org/g/openembedded-core/message/161568
Mute This Topic: https://lists.openembedded.org/mt/89024474/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Alexander Kanavin]

Right, I think the patch is ok then, but please change the commit
message so that it specifically mentions UNINATIVE_LOADER.

Alex

On Wed, 9 Feb 2022 at 16:27, Böszörményi Zoltán  wrote:
>
> I guess this commit below is what broke the image build for me,
> as it added UNINATIVE_LOADER handling to qemuboot.bbclass.
>
> commit 39c10816d5ec9d9c7952d786d7a3f942d25d0c27
> Author: Alexander Kanavin 
> Date:   Fri Feb 4 20:59:43 2022 +0100
>
>  runqemu: preload uninative libraries when host gl drivers are in use
>
>  Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
>  that tricks uninative loader into loading pieces of the host libc, if
>  the same pieces haven't been previously loaded by native binaries. Mixing
>  the two libc versions leads to failures.
>
>  This change ensures that the correct (uninative) versions are always in 
> use.
>
>  Signed-off-by: Alexander Kanavin 
>  Signed-off-by: Richard Purdie 
>
>
> Zoltán
>
> 2022. 02. 09. 15:55 keltezéssel, Zoltan Boszormenyi via 
> lists.openembedded.org írta:
> > I have added a bb.error line to print the value of "k".
> > It's "UNINATIVE_LOADER".
> >
> > I am not touching this variable in my custom distro layer. Should I?
> >
> > Zoltán
> >
> > 2022. 02. 09. 11:56 keltezéssel, Alexander Kanavin írta:
> >> Right, but this might be fixing the symptom, and not the problem.
> >>
> >> Alex
> >>
> >> On Wed, 9 Feb 2022 at 11:53, Böszörményi Zoltán  wrote:
> >>>
> >>> (Resending from the address I am subscribed with.)
> >>>
> >>> I have no idea.
> >>>
> >>> It was working a week ago for me but today after "repo sync"
> >>> the image build failed on me with the quoted error.
> >>>
> >>> With this fix, the image is built with the expected contents.
> >>>
> >>> The change with "if val.startswith()" was from 2017,
> >>> something around it must have changed very recently.
> >>>
> >>> Zoltán
> >>>
> >>> 2022. 02. 09. 11:35 keltezéssel, Alexander Kanavin írta:
>  Wait, why val is none in the first place? Why aren't others seeing it?
> 
>  Alex
> 
>  On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
>  lists.openembedded.org  wrote:
> >
> > From: Zoltán Böszörményi 
> >
> > I got this error on current master:
> >
> > File: 'exec_func_python() autogenerated', lineno: 2, function: 
> >0001:
> >*** 0002:do_write_qemuboot_conf(d)
> >0003:
> > File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', 
> > lineno: 141,
> > function: do_write_qemuboot_conf
> >0137:else:
> >0138:val = d.getVar(k)
> >0139:# we only want to write out relative paths so that 
> > we can
> > relocate images
> >0140:# and still run them
> >*** 0141:if val.startswith(topdir):
> >0142:val = os.path.relpath(val, finalpath)
> >0143:cf.set('config_bsp', k, '%s' % val)
> >0144:
> >0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the 
> > name of a symlink
> > Exception: AttributeError: 'NoneType' object has no attribute 
> > 'startswith'
> >
> > Do nothing if "val" is None.
> >
> > Signed-off-by: Zoltán Böszörményi 
> > ---
> >meta/classes/qemuboot.bbclass | 2 ++
> >1 file changed, 2 insertions(+)
> >
> > diff --git a/meta/classes/qemuboot.bbclass 
> > b/meta/classes/qemuboot.bbclass
> > index 229bd88527..755d49acd6 100644
> > --- a/meta/classes/qemuboot.bbclass
> > +++ b/meta/classes/qemuboot.bbclass
> > @@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
> >
> > 'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
> >else:
> >val = d.getVar(k)
> > +if val is None:
> > +continue
> ># we only want to write out relative paths so that we can 
> > relocate images
> ># and still run them
> >if val.startswith(topdir):
> > --
> > 2.34.1
> >
> >
> >
> >
> >>>
> >
> >
> >
> > 
> >
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161567): 
https://lists.openembedded.org/g/openembedded-core/message/161567
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[Richard Purdie]

On Wed, 2022-02-09 at 14:27 +, mikko.rap...@bmw.de wrote:
> On Wed, Feb 09, 2022 at 01:40:22PM +, Richard Purdie wrote:
> > On Wed, 2022-02-09 at 13:27 +, mikko.rap...@bmw.de wrote:
> > > Hi,
> > > 
> > > On Wed, Feb 09, 2022 at 12:23:39PM +, Richard Purdie wrote:
> > > > People have requested changes like this before and I rejected it as I'm 
> > > > worried
> > > > that allowing people to customise this code will just fork the project 
> > > > into many
> > > > different directions. 
> > > 
> > > It's the other way round. There are a lot of needs to extract metadata 
> > > from
> > > build system into something where reports can be generated.
> > 
> > I don't doubt that however buildhistory was written for a specific purpose 
> > and
> > if we start adding the ability to customise it heavily we lose the ability 
> > for
> > comparisions to be made, or sstate reuse and so on.
> > 
> > I'm partly channelling the original author's views on this since they had 
> > some
> > very specific thoughts on this change. I do sometimes wonder if I should
> > continue doing that though :/.
> 
> Then how should yocto users export CVE_NAME, LICENSE, PN, PV, SRC_URI etc from
> the build system to generate SW bill of materials (BOM) for their product
> and track progress?
> 
> Yes, SPDX can be the other answer but I don't find that human readable or 
> working
> out of the box atm.

buildhistory was not intended for SBOM generation, that is what create-spdx is
being developed for. They have two quite different intentions and trying to turn
one into the other is why I have concerns about this patch.

For example, of we did go this way, next, we may need to either write a
converter of buildhistory to SPDX format, or change buildhistory to use SPDX
format so that it has a standard SBOM output form. This is not the direction we
want/need to go.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161566): 
https://lists.openembedded.org/g/openembedded-core/message/161566
Mute This Topic: https://lists.openembedded.org/mt/89018266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Zoltan Boszormenyi via lists.openembedded.org]

I guess this commit below is what broke the image build for me,
as it added UNINATIVE_LOADER handling to qemuboot.bbclass.

commit 39c10816d5ec9d9c7952d786d7a3f942d25d0c27
Author: Alexander Kanavin 
Date:   Fri Feb 4 20:59:43 2022 +0100

runqemu: preload uninative libraries when host gl drivers are in use

Some of the host distributions build the drivers in a way (RPATH/RUNPATH)
that tricks uninative loader into loading pieces of the host libc, if
the same pieces haven't been previously loaded by native binaries. Mixing
the two libc versions leads to failures.

This change ensures that the correct (uninative) versions are always in use.

Signed-off-by: Alexander Kanavin 
Signed-off-by: Richard Purdie 


Zoltán

2022. 02. 09. 15:55 keltezéssel, Zoltan Boszormenyi via lists.openembedded.org 
írta:

I have added a bb.error line to print the value of "k".
It's "UNINATIVE_LOADER".

I am not touching this variable in my custom distro layer. Should I?

Zoltán

2022. 02. 09. 11:56 keltezéssel, Alexander Kanavin írta:

Right, but this might be fixing the symptom, and not the problem.

Alex

On Wed, 9 Feb 2022 at 11:53, Böszörményi Zoltán  wrote:


(Resending from the address I am subscribed with.)

I have no idea.

It was working a week ago for me but today after "repo sync"
the image build failed on me with the quoted error.

With this fix, the image is built with the expected contents.

The change with "if val.startswith()" was from 2017,
something around it must have changed very recently.

Zoltán

2022. 02. 09. 11:35 keltezéssel, Alexander Kanavin írta:

Wait, why val is none in the first place? Why aren't others seeing it?

Alex

On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
lists.openembedded.org  wrote:


From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
   0001:
   *** 0002:do_write_qemuboot_conf(d)
   0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 141, 
function: do_write_qemuboot_conf

   0137:    else:
   0138:    val = d.getVar(k)
   0139:    # we only want to write out relative paths so that we can 
relocate images

   0140:    # and still run them
   *** 0141:    if val.startswith(topdir):
   0142:    val = os.path.relpath(val, finalpath)
   0143:    cf.set('config_bsp', k, '%s' % val)
   0144:
   0145:    # QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of 
a symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None.

Signed-off-by: Zoltán Böszörményi 
---
   meta/classes/qemuboot.bbclass | 2 ++
   1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 229bd88527..755d49acd6 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
  
'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')

   else:
   val = d.getVar(k)
+    if val is None:
+    continue
   # we only want to write out relative paths so that we can relocate 
images
   # and still run them
   if val.startswith(topdir):
--
2.34.1















-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161565): 
https://lists.openembedded.org/g/openembedded-core/message/161565
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Zoltan Boszormenyi via lists.openembedded.org]

I have added a bb.error line to print the value of "k".
It's "UNINATIVE_LOADER".

I am not touching this variable in my custom distro layer. Should I?

Zoltán

2022. 02. 09. 11:56 keltezéssel, Alexander Kanavin írta:

Right, but this might be fixing the symptom, and not the problem.

Alex

On Wed, 9 Feb 2022 at 11:53, Böszörményi Zoltán  wrote:


(Resending from the address I am subscribed with.)

I have no idea.

It was working a week ago for me but today after "repo sync"
the image build failed on me with the quoted error.

With this fix, the image is built with the expected contents.

The change with "if val.startswith()" was from 2017,
something around it must have changed very recently.

Zoltán

2022. 02. 09. 11:35 keltezéssel, Alexander Kanavin írta:

Wait, why val is none in the first place? Why aren't others seeing it?

Alex

On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
lists.openembedded.org  wrote:


From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
   0001:
   *** 0002:do_write_qemuboot_conf(d)
   0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
141, function: do_write_qemuboot_conf
   0137:else:
   0138:val = d.getVar(k)
   0139:# we only want to write out relative paths so that we can 
relocate images
   0140:# and still run them
   *** 0141:if val.startswith(topdir):
   0142:val = os.path.relpath(val, finalpath)
   0143:cf.set('config_bsp', k, '%s' % val)
   0144:
   0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of 
a symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None.

Signed-off-by: Zoltán Böszörményi 
---
   meta/classes/qemuboot.bbclass | 2 ++
   1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 229bd88527..755d49acd6 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
  
'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
   else:
   val = d.getVar(k)
+if val is None:
+continue
   # we only want to write out relative paths so that we can relocate 
images
   # and still run them
   if val.startswith(topdir):
--
2.34.1









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161564): 
https://lists.openembedded.org/g/openembedded-core/message/161564
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[Mikko Rapeli]

On Wed, Feb 09, 2022 at 01:40:22PM +, Richard Purdie wrote:
> On Wed, 2022-02-09 at 13:27 +, mikko.rap...@bmw.de wrote:
> > Hi,
> > 
> > On Wed, Feb 09, 2022 at 12:23:39PM +, Richard Purdie wrote:
> > > People have requested changes like this before and I rejected it as I'm 
> > > worried
> > > that allowing people to customise this code will just fork the project 
> > > into many
> > > different directions. 
> > 
> > It's the other way round. There are a lot of needs to extract metadata from
> > build system into something where reports can be generated.
> 
> I don't doubt that however buildhistory was written for a specific purpose and
> if we start adding the ability to customise it heavily we lose the ability for
> comparisions to be made, or sstate reuse and so on.
> 
> I'm partly channelling the original author's views on this since they had some
> very specific thoughts on this change. I do sometimes wonder if I should
> continue doing that though :/.

Then how should yocto users export CVE_NAME, LICENSE, PN, PV, SRC_URI etc from
the build system to generate SW bill of materials (BOM) for their product
and track progress?

Yes, SPDX can be the other answer but I don't find that human readable or 
working
out of the box atm.

> >  I'd prefer this to be buildhistory as it also tracks progress across 
> > releases and 
> > versions and custom builds if the setup has been done correctly. If this 
> > change isn't 
> > going to be accepted, projects need to continue with their custom patches 
> > on top of 
> > current buildhistory bbclass in poky.
> > 
> > > The elif block above illustrates part of my concern since it still isn't 
> > > scaling
> > > well and just potentially makes every buildhistory output difference 
> > > (even with
> > > different ordering). There are reasons the data is taken from pkginfo 
> > > rather
> > > than getVar too and I think this could introduce subtle bugs in the 
> > > future.
> > 
> > The elif block is just for backwards compatibility. Changing the order of 
> > fields would
> > be annoying in buildhistory. The new ones will be in alphabetical order so 
> > I don't
> > think this is so bad. It is possibly to completely rewrite and simplify 
> > buildhistory
> > but this would be annoying for users who actually track the changes.
> >
> > > Which variables are you actually interested in when changing this?
> > 
> > LICENSE, CVE_PRODUCT, SRC_URI, MAINTAINER and some project specific 
> > variables too.
> > It is very useful to have these tracked in buildhistory git repo where 
> > differences
> > between releases can easily be seen.
> 
> The trouble is this turns it into a "metadata difference" tool rather than a
> build output difference tool which is different to the design. It also makes 
> it
> much harder to write the buildhistory analysis tool since all of a sudden 
> we're
> dealing with any variable rather than package specific ones and we can no 
> longer
> assume any particular output would be present (and it is no longer just based
> upon packagedata).

What tool or feature from yocto should we use then?

> I guess we can see what others think, but I am concerned about letting people
> remove existing output from it too.

Well buildhistory can have defaults. It can be extended. I don't see your 
reasons
for limiting the output to a few variables which you care about.

I frequently debug issues by looking at buildhistory data about images, binary
packages and recipes. It is a very useful tool.

-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161563): 
https://lists.openembedded.org/g/openembedded-core/message/161563
Mute This Topic: https://lists.openembedded.org/mt/89018266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] Missing python.h when building ntpsec

[Mans Zigher]

Hi,

I am trying to backport ntpsec from master to Thud but I have
encountered an issue where python.h is missing in the sysroot for the
ntpsec so the configuration task is failing. The ntpsec recipe has

DEPENDS += "bison-native \
openssl \
python3"

So should that not result in python.h being included to the sysroot
for the ntpsec? Any hints on what to look for?

Thanks,

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161562): 
https://lists.openembedded.org/g/openembedded-core/message/161562
Mute This Topic: https://lists.openembedded.org/mt/89021393/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v3 1/3] glibc: Upgrade to 2.35 (RFC)

[Richard Purdie]

On Tue, 2022-02-08 at 14:53 -0800, Khem Raj wrote:
> From: Richard Purdie 
> 
> Package /usr/bin/ld.so in a separate package
> 
> ld.so is a new tool which is added as a symlink to original dynamic
> linker so make it available with same name across architectures which is
> useful to leveral features like  --preload, --audit, and --list-diagnostics
> more accessible to end users
> 

There is still a QA error with this for multilib:

https://autobuilder.yoctoproject.org/typhoon/#/builders/44/builds/4735/steps/11/logs/stdio

Cheers,

Richard





-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161561): 
https://lists.openembedded.org/g/openembedded-core/message/161561
Mute This Topic: https://lists.openembedded.org/mt/89009276/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH v4] perl: Help resolving WNOHANG and _exit in Posix module

[Richard Purdie]

On Tue, 2022-02-08 at 21:15 -0800, Khem Raj wrote:
> Signed-off-by: Khem Raj 
> ---
> v4: Fix filepaths in release tarballs which are different than git repo
> 
>  ...01-ipc-force-POSIX-WNOHANG-resolving.patch | 52 +++
>  meta/recipes-devtools/perl/perl_5.34.0.bb |  1 +
>  2 files changed, 53 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch

As I hinted at originally, this papers over a crack and doesn't solve the real
error:

https://autobuilder.yoctoproject.org/typhoon/#/builders/20/builds/5042/steps/12/logs/stdio

What the real error is remains unclear too :(

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161560): 
https://lists.openembedded.org/g/openembedded-core/message/161560
Mute This Topic: https://lists.openembedded.org/mt/89016040/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[Richard Purdie]

On Wed, 2022-02-09 at 13:27 +, mikko.rap...@bmw.de wrote:
> Hi,
> 
> On Wed, Feb 09, 2022 at 12:23:39PM +, Richard Purdie wrote:
> > People have requested changes like this before and I rejected it as I'm 
> > worried
> > that allowing people to customise this code will just fork the project into 
> > many
> > different directions. 
> 
> It's the other way round. There are a lot of needs to extract metadata from
> build system into something where reports can be generated.

I don't doubt that however buildhistory was written for a specific purpose and
if we start adding the ability to customise it heavily we lose the ability for
comparisions to be made, or sstate reuse and so on.

I'm partly channelling the original author's views on this since they had some
very specific thoughts on this change. I do sometimes wonder if I should
continue doing that though :/.

>  I'd prefer this to be buildhistory as it also tracks progress across 
> releases and 
> versions and custom builds if the setup has been done correctly. If this 
> change isn't 
> going to be accepted, projects need to continue with their custom patches on 
> top of 
> current buildhistory bbclass in poky.
> 
> > The elif block above illustrates part of my concern since it still isn't 
> > scaling
> > well and just potentially makes every buildhistory output difference (even 
> > with
> > different ordering). There are reasons the data is taken from pkginfo rather
> > than getVar too and I think this could introduce subtle bugs in the future.
> 
> The elif block is just for backwards compatibility. Changing the order of 
> fields would
> be annoying in buildhistory. The new ones will be in alphabetical order so I 
> don't
> think this is so bad. It is possibly to completely rewrite and simplify 
> buildhistory
> but this would be annoying for users who actually track the changes.
>
> > Which variables are you actually interested in when changing this?
> 
> LICENSE, CVE_PRODUCT, SRC_URI, MAINTAINER and some project specific variables 
> too.
> It is very useful to have these tracked in buildhistory git repo where 
> differences
> between releases can easily be seen.

The trouble is this turns it into a "metadata difference" tool rather than a
build output difference tool which is different to the design. It also makes it
much harder to write the buildhistory analysis tool since all of a sudden we're
dealing with any variable rather than package specific ones and we can no longer
assume any particular output would be present (and it is no longer just based
upon packagedata).

I guess we can see what others think, but I am concerned about letting people
remove existing output from it too.

Cheers,

Richard








-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161559): 
https://lists.openembedded.org/g/openembedded-core/message/161559
Mute This Topic: https://lists.openembedded.org/mt/89018266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core][dunfell][PATCH] binutils: Fix CVE-2021-45078

[Purushottam Choudhary]

From: Sundeep KOKKONDA 

Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=161e87d12167b1e36193385485c1f6ce92f74f02]
(From OE-Core rev: be665a2279795c522cb3e3e700ea747efd885f95)

Signed-off-by: Sundeep KOKKONDA 
Signed-off-by: Anuj Mittal 
Signed-off-by: Richard Purdie 
(cherry picked from commit 823d25f5218836fb4298482366fbc5d05d822907)
Signed-off-by: Purushottam Choudhary 
Signed-off-by: Purushottam Choudhary 
---
 .../binutils/binutils-2.34.inc|   1 +
 .../binutils/0001-CVE-2021-45078.patch| 257 ++
 2 files changed, 258 insertions(+)
 create mode 100644 
meta/recipes-devtools/binutils/binutils/0001-CVE-2021-45078.patch

diff --git a/meta/recipes-devtools/binutils/binutils-2.34.inc 
b/meta/recipes-devtools/binutils/binutils-2.34.inc
index 6104bec591..d3936a5da2 100644
--- a/meta/recipes-devtools/binutils/binutils-2.34.inc
+++ b/meta/recipes-devtools/binutils/binutils-2.34.inc
@@ -50,5 +50,6 @@ SRC_URI = "\
  file://CVE-2021-3487.patch \
  file://CVE-2021-3549.patch \
  file://CVE-2020-16593.patch \
+ file://0001-CVE-2021-45078.patch \
 "
 S  = "${WORKDIR}/git"
diff --git a/meta/recipes-devtools/binutils/binutils/0001-CVE-2021-45078.patch 
b/meta/recipes-devtools/binutils/binutils/0001-CVE-2021-45078.patch
new file mode 100644
index 00..2af82477ac
--- /dev/null
+++ b/meta/recipes-devtools/binutils/binutils/0001-CVE-2021-45078.patch
@@ -0,0 +1,257 @@
+From 161e87d12167b1e36193385485c1f6ce92f74f02 Mon Sep 17 00:00:00 2001
+From: Alan Modra 
+Date: Wed, 15 Dec 2021 11:48:42 +1030
+Subject: [PATCH] PR28694, Out-of-bounds write in stab_xcoff_builtin_type
+
+   PR 28694
+   * stabs.c (stab_xcoff_builtin_type): Make typenum unsigned.
+   Negate typenum earlier, simplifying bounds checking.  Correct
+   off-by-one indexing.  Adjust switch cases.
+
+
+CVE: CVE-2021-45078
+Upstream-Status: Backport 
[https://sourceware.org/git/?p=binutils-gdb.git;a=patch;h=161e87d12167b1e36193385485c1f6ce92f74f02]
+
+Signed-off-by: Sundeep KOKKONDA 
+Signed-off-by: Purushottam Choudhary 
+Signed-off-by: Purushottam Choudhary 
+---
+ binutils/stabs.c | 87 
+ 1 file changed, 43 insertions(+), 44 deletions(-)
+
+
+diff --git a/binutils/stabs.c b/binutils/stabs.c
+index 274bfb0e7fa..83ee3ea5fa4 100644
+--- a/binutils/stabs.c
 b/binutils/stabs.c
+@@ -202,7 +202,7 @@ static debug_type stab_find_type (void *, struct 
stab_handle *, const int *);
+ static bfd_boolean stab_record_type
+   (void *, struct stab_handle *, const int *, debug_type);
+ static debug_type stab_xcoff_builtin_type
+-  (void *, struct stab_handle *, int);
++  (void *, struct stab_handle *, unsigned int);
+ static debug_type stab_find_tagged_type
+   (void *, struct stab_handle *, const char *, int, enum debug_type_kind);
+ static debug_type *stab_demangle_argtypes
+@@ -3496,166 +3496,167 @@ stab_record_type (void *dhandle ATTRIBUTE_UNUSED, 
struct stab_handle *info,
+ 
+ static debug_type
+ stab_xcoff_builtin_type (void *dhandle, struct stab_handle *info,
+-   int typenum)
++   unsigned int typenum)
+ {
+   debug_type rettype;
+   const char *name;
+ 
+-  if (typenum >= 0 || typenum < -XCOFF_TYPE_COUNT)
++  typenum = -typenum - 1;
++  if (typenum >= XCOFF_TYPE_COUNT)
+ {
+-  fprintf (stderr, _("Unrecognized XCOFF type %d\n"), typenum);
++  fprintf (stderr, _("Unrecognized XCOFF type %d\n"), -typenum - 1);
+   return DEBUG_TYPE_NULL;
+ }
+-  if (info->xcoff_types[-typenum] != NULL)
+-return info->xcoff_types[-typenum];
++  if (info->xcoff_types[typenum] != NULL)
++return info->xcoff_types[typenum];
+ 
+-  switch (-typenum)
++  switch (typenum)
+ {
+-case 1:
++case 0:
+   /* The size of this and all the other types are fixed, defined
+by the debugging format.  */
+   name = "int";
+   rettype = debug_make_int_type (dhandle, 4, FALSE);
+   break;
+-case 2:
++case 1:
+   name = "char";
+   rettype = debug_make_int_type (dhandle, 1, FALSE);
+   break;
+-case 3:
++case 2:
+   name = "short";
+   rettype = debug_make_int_type (dhandle, 2, FALSE);
+   break;
+-case 4:
++case 3:
+   name = "long";
+   rettype = debug_make_int_type (dhandle, 4, FALSE);
+   break;
+-case 5:
++case 4:
+   name = "unsigned char";
+   rettype = debug_make_int_type (dhandle, 1, TRUE);
+   break;
+-case 6:
++case 5:
+   name = "signed char";
+   rettype = debug_make_int_type (dhandle, 1, FALSE);
+   break;
+-case 7:
++case 6:
+   name = "unsigned short";
+   rettype = debug_make_int_type (dhandle, 2, TRUE);
+   break;
+-case 8:
++case 7:
+   name = "unsigned int";
+   rettype = debug_make_int_type (dhandle, 4, TRUE);
+   break;
+-case 9:
++case 8:
+   name = "unsigned";
+   

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[Mikko Rapeli]

Hi,

On Wed, Feb 09, 2022 at 12:23:39PM +, Richard Purdie wrote:
> People have requested changes like this before and I rejected it as I'm 
> worried
> that allowing people to customise this code will just fork the project into 
> many
> different directions. 

It's the other way round. There are a lot of needs to extract metadata from
build system into something where reports can be generated. I'd prefer this to
be buildhistory as it also tracks progress across releases and versions and 
custom
builds if the setup has been done correctly. If this change isn't going to be 
accepted,
projects need to continue with their custom patches on top of current 
buildhistory
bbclass in poky.

> The elif block above illustrates part of my concern since it still isn't 
> scaling
> well and just potentially makes every buildhistory output difference (even 
> with
> different ordering). There are reasons the data is taken from pkginfo rather
> than getVar too and I think this could introduce subtle bugs in the future.

The elif block is just for backwards compatibility. Changing the order of 
fields would
be annoying in buildhistory. The new ones will be in alphabetical order so I 
don't
think this is so bad. It is possibly to completely rewrite and simplify 
buildhistory
but this would be annoying for users who actually track the changes.

> Which variables are you actually interested in when changing this?

LICENSE, CVE_PRODUCT, SRC_URI, MAINTAINER and some project specific variables 
too.
It is very useful to have these tracked in buildhistory git repo where 
differences
between releases can easily be seen.

Cheers,

-Mikko
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161557): 
https://lists.openembedded.org/g/openembedded-core/message/161557
Mute This Topic: https://lists.openembedded.org/mt/89018266/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[sana kazi]

Hi Richard,

I need all the variables but am also interested in additional information
like CVE_PRODUCT or MAINTAINER. Prepared these changes so that any project
specific additional information like that can be added by appending them in
a recipe or distro specific conf.

Regards,
Sana Kazi

On Wed, 9 Feb 2022 at 17:53, Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:

> On Wed, 2022-02-09 at 14:59 +0530, sana kazi wrote:
> > Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> > BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
> > data to the latest file of buildhistory and sorted it alphabetically.
> >
> > This makes extending data in buildhistory git tree simple and avoids
> > patches to it for users who care about things like SRC_URI and like
> > to track it in buildhistory git tree.
> >
> > Now we can add additional information as per our requirement to the
> > buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
> > by appending them in a recipe or distro specific conf file as follows:
> >
> > BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
> > BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"
> >
> > Signed-off-by: Sana Kazi 
> > Signed-off-by: Sana Kazi 
> > ---
> >  meta/classes/buildhistory.bbclass | 111 --
> >  1 file changed, 73 insertions(+), 38 deletions(-)
> >
> > diff --git a/meta/classes/buildhistory.bbclass
> b/meta/classes/buildhistory.bbclass
> > index daa96f3b63..377b325518 100644
> > --- a/meta/classes/buildhistory.bbclass
> > +++ b/meta/classes/buildhistory.bbclass
> > @@ -69,6 +69,11 @@ BUILDHISTORY_PRESERVE = "latest latest_srcrev sysroot"
> >  PATCH_GIT_USER_EMAIL ?= "buildhistory@oe"
> >  PATCH_GIT_USER_NAME ?= "OpenEmbedded"
> >
> > +# Set BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES
> > +# to export recipe and package data to the latest file of buildhistory
> > +BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS
> PACKAGES SRC_URI LICENSE CONFIG"
> > +BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR
> RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES
> FILELIST"
> > +
> >  #
> >  # Write out the contents of the sysroot
> >  #
> > @@ -264,12 +269,11 @@ python buildhistory_emit_pkghistory() {
> >  rcpinfo.pe = pe
> >  rcpinfo.pv = pv
> >  rcpinfo.pr = pr
> > -rcpinfo.depends =
> sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or ""))
> >  rcpinfo.packages = packages
> >  rcpinfo.layer = layer
> > -rcpinfo.license = license
> >  rcpinfo.config =
> sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> > -rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> > +export_recipe_variables =
> d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') or ''
> > +rcpinfo.export_recipe_variables = export_recipe_variables
> >  write_recipehistory(rcpinfo, d)
> >
> >  bb.build.exec_func("read_subpackage_metadata", d)
> > @@ -323,6 +327,9 @@ python buildhistory_emit_pkghistory() {
> >
> >  pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
> >
> > +export_package_variables =
> d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
> > +pkginfo.export_package_variables = export_package_variables
> > +
> >  write_pkghistory(pkginfo, d)
> >
> >  oe.qa.exit_if_errors(d)
> > @@ -370,17 +377,22 @@ def write_recipehistory(rcpinfo, d):
> >  pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
> >
> >  infofile = os.path.join(pkghistdir, "latest")
> > +export_recipe_variables =
> set(rcpinfo.export_recipe_variables.split())
> > +ret = []
> >  with open(infofile, "w") as f:
> > -if rcpinfo.pe != "0":
> > -f.write(u"PE = %s\n" %  rcpinfo.pe)
> > -f.write(u"PV = %s\n" %  rcpinfo.pv)
> > -f.write(u"PR = %s\n" %  rcpinfo.pr)
> > -f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
> > -f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
> > -f.write(u"LAYER = %s\n" %  rcpinfo.layer)
> > -f.write(u"LICENSE = %s\n" %  rcpinfo.license)
> > -f.write(u"CONFIG = %s\n" %  rcpinfo.config)
> > -f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
> > +for var in export_recipe_variables:
> > +if var == "PE":
> > +if rcpinfo.pe != "0":
> > +ret.append("%s = %s" % (var, rcpinfo.pe))
> > +elif var == "LAYER":
> > +ret.append("%s = %s" % (var, rcpinfo.layer))
> > +elif var == "CONFIG":
> > +ret.append("%s = %s" % (var, rcpinfo.config))
> > +else:
> > +ret.append("%s = %s" % (var,"
> ".join((str(d.getVar(var)).split()
> > +ret.sort()
> > +for element in ret:
> > +f.write(element + "\n")
> >
> >  write_latest_srcrev(d, pkghistdir)
> >
> > @@ -394,32 +406,55 @@ def 

[OE-core] [PATCH] gcc : Fix CVE-2021-46195

[Pgowda]

Upstream-Status: Backport 
[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab]

Signed-off-by: pgowda 
---
 meta/recipes-devtools/gcc/gcc-11.2.inc|   1 +
 .../gcc/gcc/0001-CVE-2021-46195.patch | 128 ++
 2 files changed, 129 insertions(+)
 create mode 100644 meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch

diff --git a/meta/recipes-devtools/gcc/gcc-11.2.inc 
b/meta/recipes-devtools/gcc/gcc-11.2.inc
index a62f272d3c..7a45ff76c1 100644
--- a/meta/recipes-devtools/gcc/gcc-11.2.inc
+++ b/meta/recipes-devtools/gcc/gcc-11.2.inc
@@ -67,6 +67,7 @@ SRC_URI = "\
file://0002-CVE-2021-42574.patch \
file://0003-CVE-2021-42574.patch \
file://0004-CVE-2021-42574.patch \
+   file://0001-CVE-2021-46195.patch \
 "
 SRC_URI[sha256sum] = 
"d08edc536b54c372a1010ff6619dd274c0f1603aa49212ba20f7aa2cda36fa8b"
 
diff --git a/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch 
b/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch
new file mode 100644
index 00..7b3651c73e
--- /dev/null
+++ b/meta/recipes-devtools/gcc/gcc/0001-CVE-2021-46195.patch
@@ -0,0 +1,128 @@
+From f10bec5ffa487ad3033ed5f38cfd0fc7d696deab Mon Sep 17 00:00:00 2001
+From: Nick Clifton 
+Date: Mon, 31 Jan 2022 14:28:42 +
+Subject: [PATCH] libiberty: Fix infinite recursion in rust demangler.
+
+libiberty/
+   PR demangler/98886
+   PR demangler/99935
+   * rust-demangle.c (struct rust_demangler): Add a recursion
+   counter.
+   (demangle_path): Increment/decrement the recursion counter upon
+   entry and exit.  Fail if the counter exceeds a fixed limit.
+   (demangle_type): Likewise.
+   (rust_demangle_callback): Initialise the recursion counter,
+   disabling if requested by the option flags.
+
+CVE: CVE-2021-46195
+Upstream-Status: Backport
+[https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=f10bec5ffa487ad3033ed5f38cfd0fc7d696deab]
+Signed-off-by: Pgowda 
+---
+ libiberty/rust-demangle.c | 47 ++-
+ 1 file changed, 41 insertions(+), 6 deletions(-)
+
+diff --git a/libiberty/rust-demangle.c b/libiberty/rust-demangle.c
+index 18c760491bd..3b24d63892a 100644
+--- a/libiberty/rust-demangle.c
 b/libiberty/rust-demangle.c
+@@ -74,6 +74,12 @@ struct rust_demangler
+   /* Rust mangling version, with legacy mangling being -1. */
+   int version;
+ 
++  /* Recursion depth.  */
++  unsigned int recursion;
++  /* Maximum number of times demangle_path may be called recursively.  */
++#define RUST_MAX_RECURSION_COUNT  1024
++#define RUST_NO_RECURSION_LIMIT   ((unsigned int) -1)
++
+   uint64_t bound_lifetime_depth;
+ };
+ 
+@@ -671,6 +677,15 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+   if (rdm->errored)
+ return;
+ 
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++{
++  ++ rdm->recursion;
++  if (rdm->recursion > RUST_MAX_RECURSION_COUNT)
++  /* FIXME: There ought to be a way to report
++ that the recursion limit has been reached.  */
++  goto fail_return;
++}
++
+   switch (tag = next (rdm))
+ {
+ case 'C':
+@@ -688,10 +703,7 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+ case 'N':
+   ns = next (rdm);
+   if (!ISLOWER (ns) && !ISUPPER (ns))
+-{
+-  rdm->errored = 1;
+-  return;
+-}
++  goto fail_return;
+ 
+   demangle_path (rdm, in_value);
+ 
+@@ -776,9 +788,15 @@ demangle_path (struct rust_demangler *rdm, int in_value)
+ }
+   break;
+ default:
+-  rdm->errored = 1;
+-  return;
++  goto fail_return;
+ }
++  goto pass_return;
++
++ fail_return:
++  rdm->errored = 1;
++ pass_return:
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++-- rdm->recursion;
+ }
+ 
+ static void
+@@ -870,6 +888,19 @@ demangle_type (struct rust_demangler *rdm)
+   return;
+ }
+ 
++   if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++{
++  ++ rdm->recursion;
++  if (rdm->recursion > RUST_MAX_RECURSION_COUNT)
++  /* FIXME: There ought to be a way to report
++ that the recursion limit has been reached.  */
++  {
++rdm->errored = 1;
++-- rdm->recursion;
++return;
++  }
++}
++
+   switch (tag)
+ {
+ case 'R':
+@@ -1030,6 +1061,9 @@ demangle_type (struct rust_demangler *rdm)
+   rdm->next--;
+   demangle_path (rdm, 0);
+ }
++
++  if (rdm->recursion != RUST_NO_RECURSION_LIMIT)
++-- rdm->recursion;
+ }
+ 
+ /* A trait in a trait object may have some "existential projections"
+@@ -1320,6 +1354,7 @@ rust_demangle_callback (const char *mangled, int options,
+   rdm.skipping_printing = 0;
+   rdm.verbose = (options & DMGL_VERBOSE) != 0;
+   rdm.version = 0;
++  rdm.recursion = (options & DMGL_NO_RECURSE_LIMIT) ? RUST_NO_RECURSION_LIMIT 
: 0;
+   rdm.bound_lifetime_depth = 0;
+ 
+   /* Rust symbols always start with _R (v0) or _ZN (legacy). */

[OE-core] [PATCH] cmake: stop FetchContent from fetching content

[Ross Burton]

CMake includes a FetchContent module, which will download further
source code at configure time.  With the network isolation this will now
fail, but as not all environments support network isolation we can tell
cmake to not download either for extra safety.

Signed-off-by: Ross Burton 
---
 meta/classes/cmake.bbclass | 1 +
 1 file changed, 1 insertion(+)

diff --git a/meta/classes/cmake.bbclass b/meta/classes/cmake.bbclass
index 92b9197c487..fac7bbca7a3 100644
--- a/meta/classes/cmake.bbclass
+++ b/meta/classes/cmake.bbclass
@@ -189,6 +189,7 @@ cmake_do_configure() {
  -DCMAKE_TOOLCHAIN_FILE=${WORKDIR}/toolchain.cmake \
  -DCMAKE_NO_SYSTEM_FROM_IMPORTED=1 \
  -DCMAKE_EXPORT_NO_PACKAGE_REGISTRY=ON \
+ -DFETCHCONTENT_FULLY_DISCONNECTED=ON \
  ${EXTRA_OECMAKE} \
  -Wno-dev
 }
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161554): 
https://lists.openembedded.org/g/openembedded-core/message/161554
Mute This Topic: https://lists.openembedded.org/mt/89020454/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[Richard Purdie]

On Wed, 2022-02-09 at 14:59 +0530, sana kazi wrote:
> Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
> data to the latest file of buildhistory and sorted it alphabetically.
> 
> This makes extending data in buildhistory git tree simple and avoids
> patches to it for users who care about things like SRC_URI and like
> to track it in buildhistory git tree.
> 
> Now we can add additional information as per our requirement to the
> buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
> by appending them in a recipe or distro specific conf file as follows:
> 
> BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"
> 
> Signed-off-by: Sana Kazi 
> Signed-off-by: Sana Kazi 
> ---
>  meta/classes/buildhistory.bbclass | 111 --
>  1 file changed, 73 insertions(+), 38 deletions(-)
> 
> diff --git a/meta/classes/buildhistory.bbclass 
> b/meta/classes/buildhistory.bbclass
> index daa96f3b63..377b325518 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -69,6 +69,11 @@ BUILDHISTORY_PRESERVE = "latest latest_srcrev sysroot"
>  PATCH_GIT_USER_EMAIL ?= "buildhistory@oe"
>  PATCH_GIT_USER_NAME ?= "OpenEmbedded"
>  
> +# Set BUILDHISTORY_EXPORT_RECIPE_VARIABLES and 
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES
> +# to export recipe and package data to the latest file of buildhistory
> +BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
> SRC_URI LICENSE CONFIG"
> +BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
> RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
> FILELIST"
> +
>  #
>  # Write out the contents of the sysroot
>  #
> @@ -264,12 +269,11 @@ python buildhistory_emit_pkghistory() {
>  rcpinfo.pe = pe
>  rcpinfo.pv = pv
>  rcpinfo.pr = pr
> -rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or 
> ""))
>  rcpinfo.packages = packages
>  rcpinfo.layer = layer
> -rcpinfo.license = license
>  rcpinfo.config = 
> sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> -rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> +export_recipe_variables = 
> d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') or ''
> +rcpinfo.export_recipe_variables = export_recipe_variables
>  write_recipehistory(rcpinfo, d)
>  
>  bb.build.exec_func("read_subpackage_metadata", d)
> @@ -323,6 +327,9 @@ python buildhistory_emit_pkghistory() {
>  
>  pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
>  
> +export_package_variables = 
> d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
> +pkginfo.export_package_variables = export_package_variables
> +
>  write_pkghistory(pkginfo, d)
>  
>  oe.qa.exit_if_errors(d)
> @@ -370,17 +377,22 @@ def write_recipehistory(rcpinfo, d):
>  pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
>  
>  infofile = os.path.join(pkghistdir, "latest")
> +export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if rcpinfo.pe != "0":
> -f.write(u"PE = %s\n" %  rcpinfo.pe)
> -f.write(u"PV = %s\n" %  rcpinfo.pv)
> -f.write(u"PR = %s\n" %  rcpinfo.pr)
> -f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
> -f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
> -f.write(u"LAYER = %s\n" %  rcpinfo.layer)
> -f.write(u"LICENSE = %s\n" %  rcpinfo.license)
> -f.write(u"CONFIG = %s\n" %  rcpinfo.config)
> -f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
> +for var in export_recipe_variables:
> +if var == "PE":
> +if rcpinfo.pe != "0":
> +ret.append("%s = %s" % (var, rcpinfo.pe))
> +elif var == "LAYER":
> +ret.append("%s = %s" % (var, rcpinfo.layer))
> +elif var == "CONFIG":
> +ret.append("%s = %s" % (var, rcpinfo.config))
> +else:
> +ret.append("%s = %s" % (var," 
> ".join((str(d.getVar(var)).split()
> +ret.sort()
> +for element in ret:
> +f.write(element + "\n")
>  
>  write_latest_srcrev(d, pkghistdir)
>  
> @@ -394,32 +406,55 @@ def write_pkghistory(pkginfo, d):
>  bb.utils.mkdirhier(pkgpath)
>  
>  infofile = os.path.join(pkgpath, "latest")
> +export_package_variables = set(pkginfo.export_package_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if pkginfo.pe != "0":
> -f.write(u"PE = %s\n" %  pkginfo.pe)
> -f.write(u"PV = %s\n" %  pkginfo.pv)
> -f.write(u"PR = %s\n" %  pkginfo.pr)
> -
> -if pkginfo.pkg != pkginfo.name:
> -f.write(u"PKG = %s\n" % pkginfo.pkg)
> -if pkginfo.pkge != 

Re: [OE-core] [RFC] support for multi project toolchain-cmake

[Tobias Neumann]

Hello Vyacheslav and Richard,

thank you both for your feedback,

On Mon, 2022-02-08 at 10:44, Vyacheslav Yurkov wrote:
> Any reason you set SDK to be read-only? Perhaps your use case can be covered
> by extensible SDK? I mean if you have some shared libraries between project,
> isn't that enough to extend your SDK to solve the original problem?

While we indeed do have shared libraries between projects, they are not
necessary of the same version. In general we don't want to enforce restrictions
on shared code between the projects (e.g. hinder different patch sets or
enforce specific versions), appart from the base distribution that is generated
with OpenEmbedded. If libraries mature enough that they can be considered to be
(mostly) stable, we have different processes to share it between projects.

On Mon, 2022-02-08 at 14:22, Richard Purdie wrote:
> We definitely don't support that usage scenario since it would be highly build
> system specific and would work in some cases but not others. I do have a
> suggestion of a different approach though.

After your first reply, I've expected this. The Bug report #14703 can then also
be closed, however I can only set it to RESOLVED and not something like
REJECTED, hence I would asked somebody else to reject the report.

> Have you considered creating a sysroot per project with a copy of the sysroot
> files?
> 
> This sounds like a crazy idea at first but with hardlinks for the files it is
> fast and efficient to create these sysroot file trees. This is exactly what
> OpenEmbedded does internally and how we handle this in our builds.

That sounds like an interesting alternative solution. We haven't thought about
it yet, but it will be something we're going to look into.

best regards
Tobias

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161552): 
https://lists.openembedded.org/g/openembedded-core/message/161552
Mute This Topic: https://lists.openembedded.org/mt/88743247/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Alexander Kanavin]

Right, but this might be fixing the symptom, and not the problem.

Alex

On Wed, 9 Feb 2022 at 11:53, Böszörményi Zoltán  wrote:
>
> (Resending from the address I am subscribed with.)
>
> I have no idea.
>
> It was working a week ago for me but today after "repo sync"
> the image build failed on me with the quoted error.
>
> With this fix, the image is built with the expected contents.
>
> The change with "if val.startswith()" was from 2017,
> something around it must have changed very recently.
>
> Zoltán
>
> 2022. 02. 09. 11:35 keltezéssel, Alexander Kanavin írta:
> > Wait, why val is none in the first place? Why aren't others seeing it?
> >
> > Alex
> >
> > On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
> > lists.openembedded.org  wrote:
> >>
> >> From: Zoltán Böszörményi 
> >>
> >> I got this error on current master:
> >>
> >> File: 'exec_func_python() autogenerated', lineno: 2, function: 
> >>   0001:
> >>   *** 0002:do_write_qemuboot_conf(d)
> >>   0003:
> >> File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', 
> >> lineno: 141, function: do_write_qemuboot_conf
> >>   0137:else:
> >>   0138:val = d.getVar(k)
> >>   0139:# we only want to write out relative paths so that we 
> >> can relocate images
> >>   0140:# and still run them
> >>   *** 0141:if val.startswith(topdir):
> >>   0142:val = os.path.relpath(val, finalpath)
> >>   0143:cf.set('config_bsp', k, '%s' % val)
> >>   0144:
> >>   0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name 
> >> of a symlink
> >> Exception: AttributeError: 'NoneType' object has no attribute 'startswith'
> >>
> >> Do nothing if "val" is None.
> >>
> >> Signed-off-by: Zoltán Böszörményi 
> >> ---
> >>   meta/classes/qemuboot.bbclass | 2 ++
> >>   1 file changed, 2 insertions(+)
> >>
> >> diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
> >> index 229bd88527..755d49acd6 100644
> >> --- a/meta/classes/qemuboot.bbclass
> >> +++ b/meta/classes/qemuboot.bbclass
> >> @@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
> >>  
> >> 'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
> >>   else:
> >>   val = d.getVar(k)
> >> +if val is None:
> >> +continue
> >>   # we only want to write out relative paths so that we can 
> >> relocate images
> >>   # and still run them
> >>   if val.startswith(topdir):
> >> --
> >> 2.34.1
> >>
> >>
> >> 
> >>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161551): 
https://lists.openembedded.org/g/openembedded-core/message/161551
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Zoltan Boszormenyi via lists.openembedded.org]

(Resending from the address I am subscribed with.)

I have no idea.

It was working a week ago for me but today after "repo sync"
the image build failed on me with the quoted error.

With this fix, the image is built with the expected contents.

The change with "if val.startswith()" was from 2017,
something around it must have changed very recently.

Zoltán

2022. 02. 09. 11:35 keltezéssel, Alexander Kanavin írta:

Wait, why val is none in the first place? Why aren't others seeing it?

Alex

On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
lists.openembedded.org  wrote:


From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
  0001:
  *** 0002:do_write_qemuboot_conf(d)
  0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
141, function: do_write_qemuboot_conf
  0137:else:
  0138:val = d.getVar(k)
  0139:# we only want to write out relative paths so that we can 
relocate images
  0140:# and still run them
  *** 0141:if val.startswith(topdir):
  0142:val = os.path.relpath(val, finalpath)
  0143:cf.set('config_bsp', k, '%s' % val)
  0144:
  0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a 
symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None.

Signed-off-by: Zoltán Böszörményi 
---
  meta/classes/qemuboot.bbclass | 2 ++
  1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 229bd88527..755d49acd6 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
 
'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
  else:
  val = d.getVar(k)
+if val is None:
+continue
  # we only want to write out relative paths so that we can relocate 
images
  # and still run them
  if val.startswith(topdir):
--
2.34.1







-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161550): 
https://lists.openembedded.org/g/openembedded-core/message/161550
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Alexander Kanavin]

Wait, why val is none in the first place? Why aren't others seeing it?

Alex

On Wed, 9 Feb 2022 at 10:53, Zoltan Boszormenyi via
lists.openembedded.org  wrote:
>
> From: Zoltán Böszörményi 
>
> I got this error on current master:
>
> File: 'exec_func_python() autogenerated', lineno: 2, function: 
>  0001:
>  *** 0002:do_write_qemuboot_conf(d)
>  0003:
> File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
> 141, function: do_write_qemuboot_conf
>  0137:else:
>  0138:val = d.getVar(k)
>  0139:# we only want to write out relative paths so that we can 
> relocate images
>  0140:# and still run them
>  *** 0141:if val.startswith(topdir):
>  0142:val = os.path.relpath(val, finalpath)
>  0143:cf.set('config_bsp', k, '%s' % val)
>  0144:
>  0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of 
> a symlink
> Exception: AttributeError: 'NoneType' object has no attribute 'startswith'
>
> Do nothing if "val" is None.
>
> Signed-off-by: Zoltán Böszörményi 
> ---
>  meta/classes/qemuboot.bbclass | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
> index 229bd88527..755d49acd6 100644
> --- a/meta/classes/qemuboot.bbclass
> +++ b/meta/classes/qemuboot.bbclass
> @@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {
> 
> 'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
>  else:
>  val = d.getVar(k)
> +if val is None:
> +continue
>  # we only want to write out relative paths so that we can relocate 
> images
>  # and still run them
>  if val.startswith(topdir):
> --
> 2.34.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161549): 
https://lists.openembedded.org/g/openembedded-core/message/161549
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0

[Alexander Kanavin]

Yes, it seems to be sporadic. Here's a sample fail:

https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/3083
https://autobuilder.yocto.io/pub/non-release/20220208-14/testresults/qemux86-64-ptest/gstreamer1.0.log

Alex

On Wed, 9 Feb 2022 at 10:30, Claudius Heine  wrote:
>
> Hi Jose
>
> On 2022-02-09 10:15, Jose Quaresma wrote:
> > Hi Alexander,
> >
> > Can you please clarify in what target arch is this happening and I can
> > try to replicate it with qemu?
>
> I think we are hitting:
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/778
>
> This testcase seems to be flaky and IIUC upstream marked it as such in
> their test infrastructure.
>
> In my patchset, I added a patch to disable that testcase.
>
> regards,
> Claudius
>
> >
> > It works on my side on qemux86-64.
> >
> > root@qemux86-64:~# /usr/libexec/installed-tests/gstreamer/gst_gstbin.sh
> > + CK_DEFAULT_TIMEOUT=20
> > + GST_PLUGIN_LOADING_WHITELIST=gstreamer
> > + GST_REGISTRY=/home/root/.cache/gstreamer-1.0/gst_gstbin.registry
> > + GST_STATE_IGNORE_ELEMENTS=
> > + exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
> > Running suite(s): GstBin
> > 100%: Checks: 26, Failures: 0, Errors: 0
> > Check suite gst_bin ran in 6.239s (tests failed: 0)
> >
> >
> > Alexander Kanavin  > > escreveu no dia terça, 8/02/2022 à(s)
> > 22:01:
> >
> > Unfortunately this patchset (which is now in master) does not address
> > the ptest fail. Please resolve this as soon as possible.
> >
> > + exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
> > Running suite(s): GstBin
> > Executing: gstreamer/gst_gstbin.test
> > Executing: gstreamer/gst_gstbin.test
> > 
> > Executing: gstreamer/gst_gstbin.test
> > Executing: gstreamer/gst_gstbin.test
> > Test timed out after 300 seconds
> > FAIL: gstreamer/gst_gstbin.test (Child process killed by signal 9)
> >
> > Alex
> >
> > On Mon, 7 Feb 2022 at 02:08, Jose Quaresma  > > wrote:
> >  >
> >  > - License update:
> >  >   The code actually is LGPLv2.1 but the COPYING file is wrong.
> >  >
> > 
> > https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/d157b23fb0ce175b167611a4cb019599d9017042
> > 
> > 
> >  >
> >  > - Drop backported patches
> >  >   0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> >  >   0002-Remove-unused-valgrind-detection.patch
> >  >   0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
> >  >
> >  > - Update submitted patches
> >  >   0001-tests-respect-the-idententaion-used-in-meson.patch
> >  >   0002-tests-add-support-for-install-the-tests.patch
> >  >   0003-tests-use-a-dictionaries-for-environment.patch
> >  >   0004-tests-add-helper-script-to-run-the-installed_tests.patch
> >  >
> >  > Signed-off-by: Jose Quaresma  > >
> >  > ---
> >  >  ...der.c-when-env-var-is-set-do-not-fal.patch |  69 ---
> >  >  ...pect-the-idententaion-used-in-meson.patch} |  14 +--
> >  >  ...002-Remove-unused-valgrind-detection.patch | 112
> > --
> >  >  ...s-add-support-for-install-the-tests.patch} |  67 ++-
> >  >  ...-use-too-strict-timeout-for-validati.patch |  32 -
> >  >  ...-use-a-dictionaries-for-environment.patch} |  28 +++--
> >  >  ...er-script-to-run-the-installed_tests.patch |  74 
> >  >  ...-the-environment-for-installed_tests.patch |  58 -
> >  >  ...er1.0_1.18.5.bb  =>
> > gstreamer1.0_1.20.0.bb } |  17 ++-
> >  >  9 files changed, 136 insertions(+), 335 deletions(-)
> >  >  delete mode 100644
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> >  >  rename
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/{0004-tests-respect-the-idententaion-used-in-meson.patch
> > => 0001-tests-respect-the-idententaion-used-in-meson.patch} (71%)
> >  >  delete mode 100644
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-Remove-unused-valgrind-detection.patch
> >  >  rename
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/{0005-tests-add-support-for-install-the-tests.patch
> > => 0002-tests-add-support-for-install-the-tests.patch} (65%)
> >  >  delete mode 100644
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
> >  >  rename
> > 
> > meta/recipes-multimedia/gstreamer/gstreamer1.0/{0006-tests-use-a-dictionaries-for-environment.patch
> > => 0003-tests-use-a-dictionaries-for-environment.patch} (61%)
> >  >  create mode 100644
> > 
> > 

[OE-core] [PATCH] qemuboot: Fix NoneType error in do_write_qemuboot_conf

[Zoltan Boszormenyi via lists.openembedded.org]

From: Zoltán Böszörményi 

I got this error on current master:

File: 'exec_func_python() autogenerated', lineno: 2, function: 
 0001:
 *** 0002:do_write_qemuboot_conf(d)
 0003:
File: '.../layers/openembedded-core/meta/classes/qemuboot.bbclass', lineno: 
141, function: do_write_qemuboot_conf
 0137:else:
 0138:val = d.getVar(k)
 0139:# we only want to write out relative paths so that we can 
relocate images
 0140:# and still run them
 *** 0141:if val.startswith(topdir):
 0142:val = os.path.relpath(val, finalpath)
 0143:cf.set('config_bsp', k, '%s' % val)
 0144:
 0145:# QB_DEFAULT_KERNEL's value of KERNEL_IMAGETYPE is the name of a 
symlink
Exception: AttributeError: 'NoneType' object has no attribute 'startswith'

Do nothing if "val" is None.

Signed-off-by: Zoltán Böszörményi 
---
 meta/classes/qemuboot.bbclass | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/meta/classes/qemuboot.bbclass b/meta/classes/qemuboot.bbclass
index 229bd88527..755d49acd6 100644
--- a/meta/classes/qemuboot.bbclass
+++ b/meta/classes/qemuboot.bbclass
@@ -136,6 +136,8 @@ python do_write_qemuboot_conf() {

'qemu-helper-native/1.0-r1/recipe-sysroot-native/usr/bin/')
 else:
 val = d.getVar(k)
+if val is None:
+continue
 # we only want to write out relative paths so that we can relocate 
images
 # and still run them
 if val.startswith(topdir):
-- 
2.34.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161547): 
https://lists.openembedded.org/g/openembedded-core/message/161547
Mute This Topic: https://lists.openembedded.org/mt/89018458/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0

[Claudius Heine]

Hi Jose

On 2022-02-09 10:15, Jose Quaresma wrote:

Hi Alexander,

Can you please clarify in what target arch is this happening and I can 
try to replicate it with qemu?


I think we are hitting:
https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/778

This testcase seems to be flaky and IIUC upstream marked it as such in 
their test infrastructure.


In my patchset, I added a patch to disable that testcase.

regards,
Claudius



It works on my side on qemux86-64.

root@qemux86-64:~# /usr/libexec/installed-tests/gstreamer/gst_gstbin.sh
+ CK_DEFAULT_TIMEOUT=20
+ GST_PLUGIN_LOADING_WHITELIST=gstreamer
+ GST_REGISTRY=/home/root/.cache/gstreamer-1.0/gst_gstbin.registry
+ GST_STATE_IGNORE_ELEMENTS=
+ exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
Running suite(s): GstBin
100%: Checks: 26, Failures: 0, Errors: 0
Check suite gst_bin ran in 6.239s (tests failed: 0)


Alexander Kanavin > escreveu no dia terça, 8/02/2022 à(s) 
22:01:


Unfortunately this patchset (which is now in master) does not address
the ptest fail. Please resolve this as soon as possible.

+ exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
Running suite(s): GstBin
Executing: gstreamer/gst_gstbin.test
Executing: gstreamer/gst_gstbin.test

Executing: gstreamer/gst_gstbin.test
Executing: gstreamer/gst_gstbin.test
Test timed out after 300 seconds
FAIL: gstreamer/gst_gstbin.test (Child process killed by signal 9)

Alex

On Mon, 7 Feb 2022 at 02:08, Jose Quaresma mailto:quaresma.j...@gmail.com>> wrote:
 >
 > - License update:
 >   The code actually is LGPLv2.1 but the COPYING file is wrong.
 >

https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/d157b23fb0ce175b167611a4cb019599d9017042


 >
 > - Drop backported patches
 >   0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
 >   0002-Remove-unused-valgrind-detection.patch
 >   0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
 >
 > - Update submitted patches
 >   0001-tests-respect-the-idententaion-used-in-meson.patch
 >   0002-tests-add-support-for-install-the-tests.patch
 >   0003-tests-use-a-dictionaries-for-environment.patch
 >   0004-tests-add-helper-script-to-run-the-installed_tests.patch
 >
 > Signed-off-by: Jose Quaresma mailto:quaresma.j...@gmail.com>>
 > ---
 >  ...der.c-when-env-var-is-set-do-not-fal.patch |  69 ---
 >  ...pect-the-idententaion-used-in-meson.patch} |  14 +--
 >  ...002-Remove-unused-valgrind-detection.patch | 112
--
 >  ...s-add-support-for-install-the-tests.patch} |  67 ++-
 >  ...-use-too-strict-timeout-for-validati.patch |  32 -
 >  ...-use-a-dictionaries-for-environment.patch} |  28 +++--
 >  ...er-script-to-run-the-installed_tests.patch |  74 
 >  ...-the-environment-for-installed_tests.patch |  58 -
 >  ...er1.0_1.18.5.bb  =>
gstreamer1.0_1.20.0.bb } |  17 ++-
 >  9 files changed, 136 insertions(+), 335 deletions(-)
 >  delete mode 100644

meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
 >  rename

meta/recipes-multimedia/gstreamer/gstreamer1.0/{0004-tests-respect-the-idententaion-used-in-meson.patch
=> 0001-tests-respect-the-idententaion-used-in-meson.patch} (71%)
 >  delete mode 100644

meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-Remove-unused-valgrind-detection.patch
 >  rename

meta/recipes-multimedia/gstreamer/gstreamer1.0/{0005-tests-add-support-for-install-the-tests.patch
=> 0002-tests-add-support-for-install-the-tests.patch} (65%)
 >  delete mode 100644

meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
 >  rename

meta/recipes-multimedia/gstreamer/gstreamer1.0/{0006-tests-use-a-dictionaries-for-environment.patch
=> 0003-tests-use-a-dictionaries-for-environment.patch} (61%)
 >  create mode 100644

meta/recipes-multimedia/gstreamer/gstreamer1.0/0004-tests-add-helper-script-to-run-the-installed_tests.patch
 >  delete mode 100644

meta/recipes-multimedia/gstreamer/gstreamer1.0/0007-tests-install-the-environment-for-installed_tests.patch
 >  rename meta/recipes-multimedia/gstreamer/{gstreamer1.0_1.18.5.bb
 => gstreamer1.0_1.20.0.bb
} (76%)
 >
 > diff --git

a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch

b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
 > 

[OE-core] [poky][master][PATCHv2] buildhistory.bbclass: Enable exporting more recipe and package data

[sana kazi]

Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
data to the latest file of buildhistory and sorted it alphabetically.

This makes extending data in buildhistory git tree simple and avoids
patches to it for users who care about things like SRC_URI and like
to track it in buildhistory git tree.

Now we can add additional information as per our requirement to the
buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
by appending them in a recipe or distro specific conf file as follows:

BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"

Signed-off-by: Sana Kazi 
Signed-off-by: Sana Kazi 
---
 meta/classes/buildhistory.bbclass | 111 --
 1 file changed, 73 insertions(+), 38 deletions(-)

diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index daa96f3b63..377b325518 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -69,6 +69,11 @@ BUILDHISTORY_PRESERVE = "latest latest_srcrev sysroot"
 PATCH_GIT_USER_EMAIL ?= "buildhistory@oe"
 PATCH_GIT_USER_NAME ?= "OpenEmbedded"
 
+# Set BUILDHISTORY_EXPORT_RECIPE_VARIABLES and 
BUILDHISTORY_EXPORT_PACKAGE_VARIABLES
+# to export recipe and package data to the latest file of buildhistory
+BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
SRC_URI LICENSE CONFIG"
+BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
FILELIST"
+
 #
 # Write out the contents of the sysroot
 #
@@ -264,12 +269,11 @@ python buildhistory_emit_pkghistory() {
 rcpinfo.pe = pe
 rcpinfo.pv = pv
 rcpinfo.pr = pr
-rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or 
""))
 rcpinfo.packages = packages
 rcpinfo.layer = layer
-rcpinfo.license = license
 rcpinfo.config = sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') 
or ""))
-rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
+export_recipe_variables = d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') 
or ''
+rcpinfo.export_recipe_variables = export_recipe_variables
 write_recipehistory(rcpinfo, d)
 
 bb.build.exec_func("read_subpackage_metadata", d)
@@ -323,6 +327,9 @@ python buildhistory_emit_pkghistory() {
 
 pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
 
+export_package_variables = 
d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
+pkginfo.export_package_variables = export_package_variables
+
 write_pkghistory(pkginfo, d)
 
 oe.qa.exit_if_errors(d)
@@ -370,17 +377,22 @@ def write_recipehistory(rcpinfo, d):
 pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
 
 infofile = os.path.join(pkghistdir, "latest")
+export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
+ret = []
 with open(infofile, "w") as f:
-if rcpinfo.pe != "0":
-f.write(u"PE = %s\n" %  rcpinfo.pe)
-f.write(u"PV = %s\n" %  rcpinfo.pv)
-f.write(u"PR = %s\n" %  rcpinfo.pr)
-f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
-f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
-f.write(u"LAYER = %s\n" %  rcpinfo.layer)
-f.write(u"LICENSE = %s\n" %  rcpinfo.license)
-f.write(u"CONFIG = %s\n" %  rcpinfo.config)
-f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
+for var in export_recipe_variables:
+if var == "PE":
+if rcpinfo.pe != "0":
+ret.append("%s = %s" % (var, rcpinfo.pe))
+elif var == "LAYER":
+ret.append("%s = %s" % (var, rcpinfo.layer))
+elif var == "CONFIG":
+ret.append("%s = %s" % (var, rcpinfo.config))
+else:
+ret.append("%s = %s" % (var," 
".join((str(d.getVar(var)).split()
+ret.sort()
+for element in ret:
+f.write(element + "\n")
 
 write_latest_srcrev(d, pkghistdir)
 
@@ -394,32 +406,55 @@ def write_pkghistory(pkginfo, d):
 bb.utils.mkdirhier(pkgpath)
 
 infofile = os.path.join(pkgpath, "latest")
+export_package_variables = set(pkginfo.export_package_variables.split())
+ret = []
 with open(infofile, "w") as f:
-if pkginfo.pe != "0":
-f.write(u"PE = %s\n" %  pkginfo.pe)
-f.write(u"PV = %s\n" %  pkginfo.pv)
-f.write(u"PR = %s\n" %  pkginfo.pr)
-
-if pkginfo.pkg != pkginfo.name:
-f.write(u"PKG = %s\n" % pkginfo.pkg)
-if pkginfo.pkge != pkginfo.pe:
-f.write(u"PKGE = %s\n" % pkginfo.pkge)
-if pkginfo.pkgv != pkginfo.pv:
-f.write(u"PKGV = %s\n" % pkginfo.pkgv)
-if pkginfo.pkgr != pkginfo.pr:
-f.write(u"PKGR = %s\n" % pkginfo.pkgr)
-f.write(u"RPROVIDES = %s\n" %  

Re: [OE-core] [PATCH 07/17] gstreamer1.0: upgrade 1.18.5 -> 1.20.0

[Jose Quaresma]

Hi Alexander,

Can you please clarify in what target arch is this happening and I can try
to replicate it with qemu?

It works on my side on qemux86-64.

root@qemux86-64:~# /usr/libexec/installed-tests/gstreamer/gst_gstbin.sh
+ CK_DEFAULT_TIMEOUT=20
+ GST_PLUGIN_LOADING_WHITELIST=gstreamer
+ GST_REGISTRY=/home/root/.cache/gstreamer-1.0/gst_gstbin.registry
+ GST_STATE_IGNORE_ELEMENTS=
+ exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
Running suite(s): GstBin
100%: Checks: 26, Failures: 0, Errors: 0
Check suite gst_bin ran in 6.239s (tests failed: 0)


Alexander Kanavin  escreveu no dia terça, 8/02/2022
à(s) 22:01:

> Unfortunately this patchset (which is now in master) does not address
> the ptest fail. Please resolve this as soon as possible.
>
> + exec /usr/libexec/installed-tests/gstreamer/gst_gstbin
> Running suite(s): GstBin
> Executing: gstreamer/gst_gstbin.test
> Executing: gstreamer/gst_gstbin.test
> 
> Executing: gstreamer/gst_gstbin.test
> Executing: gstreamer/gst_gstbin.test
> Test timed out after 300 seconds
> FAIL: gstreamer/gst_gstbin.test (Child process killed by signal 9)
>
> Alex
>
> On Mon, 7 Feb 2022 at 02:08, Jose Quaresma 
> wrote:
> >
> > - License update:
> >   The code actually is LGPLv2.1 but the COPYING file is wrong.
> >
> https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/d157b23fb0ce175b167611a4cb019599d9017042
> >
> > - Drop backported patches
> >   0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> >   0002-Remove-unused-valgrind-detection.patch
> >   0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
> >
> > - Update submitted patches
> >   0001-tests-respect-the-idententaion-used-in-meson.patch
> >   0002-tests-add-support-for-install-the-tests.patch
> >   0003-tests-use-a-dictionaries-for-environment.patch
> >   0004-tests-add-helper-script-to-run-the-installed_tests.patch
> >
> > Signed-off-by: Jose Quaresma 
> > ---
> >  ...der.c-when-env-var-is-set-do-not-fal.patch |  69 ---
> >  ...pect-the-idententaion-used-in-meson.patch} |  14 +--
> >  ...002-Remove-unused-valgrind-detection.patch | 112 --
> >  ...s-add-support-for-install-the-tests.patch} |  67 ++-
> >  ...-use-too-strict-timeout-for-validati.patch |  32 -
> >  ...-use-a-dictionaries-for-environment.patch} |  28 +++--
> >  ...er-script-to-run-the-installed_tests.patch |  74 
> >  ...-the-environment-for-installed_tests.patch |  58 -
> >  ...er1.0_1.18.5.bb => gstreamer1.0_1.20.0.bb} |  17 ++-
> >  9 files changed, 136 insertions(+), 335 deletions(-)
> >  delete mode 100644
> meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> >  rename
> meta/recipes-multimedia/gstreamer/gstreamer1.0/{0004-tests-respect-the-idententaion-used-in-meson.patch
> => 0001-tests-respect-the-idententaion-used-in-meson.patch} (71%)
> >  delete mode 100644
> meta/recipes-multimedia/gstreamer/gstreamer1.0/0002-Remove-unused-valgrind-detection.patch
> >  rename
> meta/recipes-multimedia/gstreamer/gstreamer1.0/{0005-tests-add-support-for-install-the-tests.patch
> => 0002-tests-add-support-for-install-the-tests.patch} (65%)
> >  delete mode 100644
> meta/recipes-multimedia/gstreamer/gstreamer1.0/0003-tests-seek-Don-t-use-too-strict-timeout-for-validati.patch
> >  rename
> meta/recipes-multimedia/gstreamer/gstreamer1.0/{0006-tests-use-a-dictionaries-for-environment.patch
> => 0003-tests-use-a-dictionaries-for-environment.patch} (61%)
> >  create mode 100644
> meta/recipes-multimedia/gstreamer/gstreamer1.0/0004-tests-add-helper-script-to-run-the-installed_tests.patch
> >  delete mode 100644
> meta/recipes-multimedia/gstreamer/gstreamer1.0/0007-tests-install-the-environment-for-installed_tests.patch
> >  rename meta/recipes-multimedia/gstreamer/{gstreamer1.0_1.18.5.bb =>
> gstreamer1.0_1.20.0.bb} (76%)
> >
> > diff --git
> a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> b/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> > deleted file mode 100644
> > index 23ebd5c600..00
> > ---
> a/meta/recipes-multimedia/gstreamer/gstreamer1.0/0001-gst-gstpluginloader.c-when-env-var-is-set-do-not-fal.patch
> > +++ /dev/null
> > @@ -1,69 +0,0 @@
> > -From fd8f49dba8c09d47425da80f5faab3bfa4a7c962 Mon Sep 17 00:00:00 2001
> > -From: Jose Quaresma 
> > -Date: Sat, 10 Oct 2020 19:09:03 +
> > -Subject: [PATCH 1/3] gstpluginloader: when env var is set do not fall
> through
> > - to system plugin scanner
> > -
> > -If we set a custom GST_PLUGIN_SCANNER env var, then we probably want to
> use that and only that.
> > -
> > -Falling through to the one installed on the system is problamatic in
> cross-compilation
> > -environemnts, regardless of whether one pointed to by the env var
> succeeded or failed.
> > -
> > -taken from:
> > -
> 

Re: [OE-core] [PATCH v4] perl: Help resolving WNOHANG and _exit in Posix module

[Alexander Kanavin]

Please submit upstream:
https://github.com/jib/ipc-cmd

Alex

On Wed, 9 Feb 2022 at 06:15, Khem Raj  wrote:
>
> Signed-off-by: Khem Raj 
> ---
> v4: Fix filepaths in release tarballs which are different than git repo
>
>  ...01-ipc-force-POSIX-WNOHANG-resolving.patch | 52 +++
>  meta/recipes-devtools/perl/perl_5.34.0.bb |  1 +
>  2 files changed, 53 insertions(+)
>  create mode 100644 
> meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch
>
> diff --git 
> a/meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch
>  
> b/meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch
> new file mode 100644
> index 000..3df15d4f08c
> --- /dev/null
> +++ 
> b/meta/recipes-devtools/perl/files/0001-ipc-force-POSIX-WNOHANG-resolving.patch
> @@ -0,0 +1,52 @@
> +From 0d8c411ef7e8b4452007c77eee3d83d227b86bb4 Mon Sep 17 00:00:00 2001
> +From: Khem Raj 
> +Date: Tue, 8 Feb 2022 14:05:22 -0800
> +Subject: [PATCH] ipc: force POSIX::WNOHANG resolving
> +
> +It seems POSIX module is special and may not have autovivified (resolved) 
> WNOHANG.
> +see [1]
> +
> +Fixes
> + Bareword "POSIX::WNOHANG" not allowed while "strict subs"
> +
> +[1] 
> https://redmine.lighttpd.net/projects/lighttpd/repository/14/revisions/78eb0e39454ab3ca8e7ef77f1d014b50b3632fb9
> +
> +Upstream-Status: Pending
> +Signed-off-by: Khem Raj 
> +---
> + cpan/IPC-Cmd/lib/IPC/Cmd.pm | 8 
> + 1 file changed, 4 insertions(+), 4 deletions(-)
> +
> +--- a/cpan/IPC-Cmd/lib/IPC/Cmd.pm
>  b/cpan/IPC-Cmd/lib/IPC/Cmd.pm
> +@@ -499,7 +499,7 @@ sub kill_gently {
> + next;
> + }
> +
> +-my $waitpid = waitpid($pid, POSIX::WNOHANG);
> ++my $waitpid = waitpid($pid, POSIX::WNOHANG());
> +
> + if ($waitpid eq -1) {
> + $child_finished = 1;
> +@@ -619,10 +619,10 @@ sub open3_run {
> +   #
> +   kill(-9, $$);
> +
> +-  POSIX::_exit 1;
> ++  POSIX::_exit(1);
> + }
> +
> +-my $waitpid = waitpid($pid, POSIX::WNOHANG);
> ++my $waitpid = waitpid($pid, POSIX::WNOHANG());
> +
> + # child finished, catch it's exit status
> + if ($waitpid ne 0 && $waitpid ne -1) {
> +@@ -1005,7 +1005,7 @@ sub run_forked {
> +   $child_finished = 1;
> + }
> +
> +-my $waitpid = waitpid($pid, POSIX::WNOHANG);
> ++my $waitpid = waitpid($pid, POSIX::WNOHANG());
> +
> + # child finished, catch it's exit status
> + if ($waitpid ne 0 && $waitpid ne -1) {
> diff --git a/meta/recipes-devtools/perl/perl_5.34.0.bb 
> b/meta/recipes-devtools/perl/perl_5.34.0.bb
> index e4bcfe3ce69..48d755744fe 100644
> --- a/meta/recipes-devtools/perl/perl_5.34.0.bb
> +++ b/meta/recipes-devtools/perl/perl_5.34.0.bb
> @@ -20,6 +20,7 @@ SRC_URI = 
> "https://www.cpan.org/src/5.0/perl-${PV}.tar.gz;name=perl \
> file://aacd2398e766500cb5d83c4d76b642fcf31d997a.patch \
> file://ea57297a58b8f10ab885c19eec48ea076116cc1f.patch \
> file://5bc1e5fdd87aa205011512cd1e6cc655bcf677fd.patch \
> +   file://0001-ipc-force-POSIX-WNOHANG-resolving.patch \
> "
>  SRC_URI:append:class-native = " \
> file://perl-configpm-switch.patch \
> --
> 2.35.1
>
>
> 
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161543): 
https://lists.openembedded.org/g/openembedded-core/message/161543
Mute This Topic: https://lists.openembedded.org/mt/89016040/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Re: [OE-core] [poky][master][PATCH 1/2] buildhistory.bbclass: Enable exporting more recipe and package data

[Alexander Kanavin]

I think what is set in poky.conf should be set directly in the class.
Not everyone uses poky as a distro, and buildhistory should work for
all.

Alex

On Wed, 9 Feb 2022 at 09:11, sana kazi  wrote:
>
> Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
> data to the latest file of buildhistory and sorted it alphabetically.
>
> This makes extending data in buildhistory git tree simple and avoids
> patches to it for users who care about things like SRC_URI and like
> to track it in buildhistory git tree.
>
> Now we can add additional information as per our requirement to the
> buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
> by appending them in a recipe or distro specific conf file as follows:
>
> BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"
>
> Signed-off-by: Sana Kazi 
> Signed-off-by: Sana Kazi 
> ---
>  meta-poky/conf/distro/poky.conf   |   2 +
>  meta/classes/buildhistory.bbclass | 106 +++---
>  2 files changed, 70 insertions(+), 38 deletions(-)
>
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index 2dc3606ae5..c382493dbc 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -72,3 +72,5 @@ INHERIT += "uninative"
>
>  BB_SIGNATURE_HANDLER ?= "OEEquivHash"
>  BB_HASHSERVE ??= "auto"
> +BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
> SRC_URI LICENSE CONFIG"
> +BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
> RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
> FILELIST"
> diff --git a/meta/classes/buildhistory.bbclass 
> b/meta/classes/buildhistory.bbclass
> index daa96f3b63..04837cafc4 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -264,12 +264,11 @@ python buildhistory_emit_pkghistory() {
>  rcpinfo.pe = pe
>  rcpinfo.pv = pv
>  rcpinfo.pr = pr
> -rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or 
> ""))
>  rcpinfo.packages = packages
>  rcpinfo.layer = layer
> -rcpinfo.license = license
>  rcpinfo.config = 
> sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> -rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> +export_recipe_variables = 
> d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') or ''
> +rcpinfo.export_recipe_variables = export_recipe_variables
>  write_recipehistory(rcpinfo, d)
>
>  bb.build.exec_func("read_subpackage_metadata", d)
> @@ -323,6 +322,9 @@ python buildhistory_emit_pkghistory() {
>
>  pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
>
> +export_package_variables = 
> d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
> +pkginfo.export_package_variables = export_package_variables
> +
>  write_pkghistory(pkginfo, d)
>
>  oe.qa.exit_if_errors(d)
> @@ -370,17 +372,22 @@ def write_recipehistory(rcpinfo, d):
>  pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
>
>  infofile = os.path.join(pkghistdir, "latest")
> +export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if rcpinfo.pe != "0":
> -f.write(u"PE = %s\n" %  rcpinfo.pe)
> -f.write(u"PV = %s\n" %  rcpinfo.pv)
> -f.write(u"PR = %s\n" %  rcpinfo.pr)
> -f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
> -f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
> -f.write(u"LAYER = %s\n" %  rcpinfo.layer)
> -f.write(u"LICENSE = %s\n" %  rcpinfo.license)
> -f.write(u"CONFIG = %s\n" %  rcpinfo.config)
> -f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
> +for var in export_recipe_variables:
> +if var == "PE":
> +if rcpinfo.pe != "0":
> +ret.append("%s = %s" % (var, rcpinfo.pe))
> +elif var == "LAYER":
> +ret.append("%s = %s" % (var, rcpinfo.layer))
> +elif var == "CONFIG":
> +ret.append("%s = %s" % (var, rcpinfo.config))
> +else:
> +ret.append("%s = %s" % (var," 
> ".join((str(d.getVar(var)).split()
> +ret.sort()
> +for element in ret:
> +f.write(element + "\n")
>
>  write_latest_srcrev(d, pkghistdir)
>
> @@ -394,32 +401,55 @@ def write_pkghistory(pkginfo, d):
>  bb.utils.mkdirhier(pkgpath)
>
>  infofile = os.path.join(pkgpath, "latest")
> +export_package_variables = set(pkginfo.export_package_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if pkginfo.pe != "0":
> -f.write(u"PE = %s\n" %  pkginfo.pe)
> -f.write(u"PV = %s\n" %  pkginfo.pv)
> -f.write(u"PR = %s\n" %  pkginfo.pr)
> -
> -if pkginfo.pkg != 

Re: [OE-core] [poky][master][PATCH 1/2] buildhistory.bbclass: Enable exporting more recipe and package data

[Alexander Kanavin]

Ah, ignore me. Not reading the whole patchset can cause useless noise :)

Alex

On Wed, 9 Feb 2022 at 09:34, Alexander Kanavin via
lists.openembedded.org 
wrote:
>
> Please adjust the test in meta/lib/oeqa/selftest/cases/buildhistory.py
> to cover this expanded use case as well.
>
> Alex
>
> On Wed, 9 Feb 2022 at 09:11, sana kazi  wrote:
> >
> > Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> > BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
> > data to the latest file of buildhistory and sorted it alphabetically.
> >
> > This makes extending data in buildhistory git tree simple and avoids
> > patches to it for users who care about things like SRC_URI and like
> > to track it in buildhistory git tree.
> >
> > Now we can add additional information as per our requirement to the
> > buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
> > by appending them in a recipe or distro specific conf file as follows:
> >
> > BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
> > BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"
> >
> > Signed-off-by: Sana Kazi 
> > Signed-off-by: Sana Kazi 
> > ---
> >  meta-poky/conf/distro/poky.conf   |   2 +
> >  meta/classes/buildhistory.bbclass | 106 +++---
> >  2 files changed, 70 insertions(+), 38 deletions(-)
> >
> > diff --git a/meta-poky/conf/distro/poky.conf 
> > b/meta-poky/conf/distro/poky.conf
> > index 2dc3606ae5..c382493dbc 100644
> > --- a/meta-poky/conf/distro/poky.conf
> > +++ b/meta-poky/conf/distro/poky.conf
> > @@ -72,3 +72,5 @@ INHERIT += "uninative"
> >
> >  BB_SIGNATURE_HANDLER ?= "OEEquivHash"
> >  BB_HASHSERVE ??= "auto"
> > +BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
> > SRC_URI LICENSE CONFIG"
> > +BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
> > RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
> > FILELIST"
> > diff --git a/meta/classes/buildhistory.bbclass 
> > b/meta/classes/buildhistory.bbclass
> > index daa96f3b63..04837cafc4 100644
> > --- a/meta/classes/buildhistory.bbclass
> > +++ b/meta/classes/buildhistory.bbclass
> > @@ -264,12 +264,11 @@ python buildhistory_emit_pkghistory() {
> >  rcpinfo.pe = pe
> >  rcpinfo.pv = pv
> >  rcpinfo.pr = pr
> > -rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') 
> > or ""))
> >  rcpinfo.packages = packages
> >  rcpinfo.layer = layer
> > -rcpinfo.license = license
> >  rcpinfo.config = 
> > sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> > -rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> > +export_recipe_variables = 
> > d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') or ''
> > +rcpinfo.export_recipe_variables = export_recipe_variables
> >  write_recipehistory(rcpinfo, d)
> >
> >  bb.build.exec_func("read_subpackage_metadata", d)
> > @@ -323,6 +322,9 @@ python buildhistory_emit_pkghistory() {
> >
> >  pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
> >
> > +export_package_variables = 
> > d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
> > +pkginfo.export_package_variables = export_package_variables
> > +
> >  write_pkghistory(pkginfo, d)
> >
> >  oe.qa.exit_if_errors(d)
> > @@ -370,17 +372,22 @@ def write_recipehistory(rcpinfo, d):
> >  pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
> >
> >  infofile = os.path.join(pkghistdir, "latest")
> > +export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
> > +ret = []
> >  with open(infofile, "w") as f:
> > -if rcpinfo.pe != "0":
> > -f.write(u"PE = %s\n" %  rcpinfo.pe)
> > -f.write(u"PV = %s\n" %  rcpinfo.pv)
> > -f.write(u"PR = %s\n" %  rcpinfo.pr)
> > -f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
> > -f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
> > -f.write(u"LAYER = %s\n" %  rcpinfo.layer)
> > -f.write(u"LICENSE = %s\n" %  rcpinfo.license)
> > -f.write(u"CONFIG = %s\n" %  rcpinfo.config)
> > -f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
> > +for var in export_recipe_variables:
> > +if var == "PE":
> > +if rcpinfo.pe != "0":
> > +ret.append("%s = %s" % (var, rcpinfo.pe))
> > +elif var == "LAYER":
> > +ret.append("%s = %s" % (var, rcpinfo.layer))
> > +elif var == "CONFIG":
> > +ret.append("%s = %s" % (var, rcpinfo.config))
> > +else:
> > +ret.append("%s = %s" % (var," 
> > ".join((str(d.getVar(var)).split()
> > +ret.sort()
> > +for element in ret:
> > +f.write(element + "\n")
> >
> >  write_latest_srcrev(d, pkghistdir)
> >
> > @@ -394,32 +401,55 @@ def write_pkghistory(pkginfo, d):
> >  bb.utils.mkdirhier(pkgpath)
> >
> >  infofile = 

Re: [OE-core] [poky][master][PATCH 1/2] buildhistory.bbclass: Enable exporting more recipe and package data

[Alexander Kanavin]

Please adjust the test in meta/lib/oeqa/selftest/cases/buildhistory.py
to cover this expanded use case as well.

Alex

On Wed, 9 Feb 2022 at 09:11, sana kazi  wrote:
>
> Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
> data to the latest file of buildhistory and sorted it alphabetically.
>
> This makes extending data in buildhistory git tree simple and avoids
> patches to it for users who care about things like SRC_URI and like
> to track it in buildhistory git tree.
>
> Now we can add additional information as per our requirement to the
> buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
> by appending them in a recipe or distro specific conf file as follows:
>
> BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
> BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"
>
> Signed-off-by: Sana Kazi 
> Signed-off-by: Sana Kazi 
> ---
>  meta-poky/conf/distro/poky.conf   |   2 +
>  meta/classes/buildhistory.bbclass | 106 +++---
>  2 files changed, 70 insertions(+), 38 deletions(-)
>
> diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
> index 2dc3606ae5..c382493dbc 100644
> --- a/meta-poky/conf/distro/poky.conf
> +++ b/meta-poky/conf/distro/poky.conf
> @@ -72,3 +72,5 @@ INHERIT += "uninative"
>
>  BB_SIGNATURE_HANDLER ?= "OEEquivHash"
>  BB_HASHSERVE ??= "auto"
> +BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
> SRC_URI LICENSE CONFIG"
> +BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
> RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
> FILELIST"
> diff --git a/meta/classes/buildhistory.bbclass 
> b/meta/classes/buildhistory.bbclass
> index daa96f3b63..04837cafc4 100644
> --- a/meta/classes/buildhistory.bbclass
> +++ b/meta/classes/buildhistory.bbclass
> @@ -264,12 +264,11 @@ python buildhistory_emit_pkghistory() {
>  rcpinfo.pe = pe
>  rcpinfo.pv = pv
>  rcpinfo.pr = pr
> -rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or 
> ""))
>  rcpinfo.packages = packages
>  rcpinfo.layer = layer
> -rcpinfo.license = license
>  rcpinfo.config = 
> sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') or ""))
> -rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
> +export_recipe_variables = 
> d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') or ''
> +rcpinfo.export_recipe_variables = export_recipe_variables
>  write_recipehistory(rcpinfo, d)
>
>  bb.build.exec_func("read_subpackage_metadata", d)
> @@ -323,6 +322,9 @@ python buildhistory_emit_pkghistory() {
>
>  pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
>
> +export_package_variables = 
> d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
> +pkginfo.export_package_variables = export_package_variables
> +
>  write_pkghistory(pkginfo, d)
>
>  oe.qa.exit_if_errors(d)
> @@ -370,17 +372,22 @@ def write_recipehistory(rcpinfo, d):
>  pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
>
>  infofile = os.path.join(pkghistdir, "latest")
> +export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if rcpinfo.pe != "0":
> -f.write(u"PE = %s\n" %  rcpinfo.pe)
> -f.write(u"PV = %s\n" %  rcpinfo.pv)
> -f.write(u"PR = %s\n" %  rcpinfo.pr)
> -f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
> -f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
> -f.write(u"LAYER = %s\n" %  rcpinfo.layer)
> -f.write(u"LICENSE = %s\n" %  rcpinfo.license)
> -f.write(u"CONFIG = %s\n" %  rcpinfo.config)
> -f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
> +for var in export_recipe_variables:
> +if var == "PE":
> +if rcpinfo.pe != "0":
> +ret.append("%s = %s" % (var, rcpinfo.pe))
> +elif var == "LAYER":
> +ret.append("%s = %s" % (var, rcpinfo.layer))
> +elif var == "CONFIG":
> +ret.append("%s = %s" % (var, rcpinfo.config))
> +else:
> +ret.append("%s = %s" % (var," 
> ".join((str(d.getVar(var)).split()
> +ret.sort()
> +for element in ret:
> +f.write(element + "\n")
>
>  write_latest_srcrev(d, pkghistdir)
>
> @@ -394,32 +401,55 @@ def write_pkghistory(pkginfo, d):
>  bb.utils.mkdirhier(pkgpath)
>
>  infofile = os.path.join(pkgpath, "latest")
> +export_package_variables = set(pkginfo.export_package_variables.split())
> +ret = []
>  with open(infofile, "w") as f:
> -if pkginfo.pe != "0":
> -f.write(u"PE = %s\n" %  pkginfo.pe)
> -f.write(u"PV = %s\n" %  pkginfo.pv)
> -f.write(u"PR = %s\n" %  pkginfo.pr)
> -
> -if pkginfo.pkg != pkginfo.name:
> -

[OE-core] [poky][master][PATCH 2/2] test_buildhistory: Add test to verify that LICENSE is added

[sana kazi]

Added test case which uses BUILDHISTORY_EXPORT_RECIPE_VARIABLES
and BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to add LICENSE for glibc as a
sample recipe to buildhistory and the test verifies that expected
license value is written in latest file.

Signed-off-by: Sana Kazi 
Signed-off-by: Sana Kazi 
---
 .../recipes-test/glibc/glibc_%.bbappend   |  2 +
 .../oeqa/selftest/cases/test_buildhistory.py  | 50 +++
 2 files changed, 52 insertions(+)
 create mode 100644 meta-selftest/recipes-test/glibc/glibc_%.bbappend
 create mode 100644 meta/lib/oeqa/selftest/cases/test_buildhistory.py

diff --git a/meta-selftest/recipes-test/glibc/glibc_%.bbappend 
b/meta-selftest/recipes-test/glibc/glibc_%.bbappend
new file mode 100644
index 00..205720982c
--- /dev/null
+++ b/meta-selftest/recipes-test/glibc/glibc_%.bbappend
@@ -0,0 +1,2 @@
+# This bbappend is used to alter the recipe using the test_recipe.inc file 
created by tests.
+include test_recipe.inc
diff --git a/meta/lib/oeqa/selftest/cases/test_buildhistory.py 
b/meta/lib/oeqa/selftest/cases/test_buildhistory.py
new file mode 100644
index 00..5b0ce4be24
--- /dev/null
+++ b/meta/lib/oeqa/selftest/cases/test_buildhistory.py
@@ -0,0 +1,50 @@
+import unittest
+from oeqa.selftest.case import OESelftestTestCase
+from oeqa.selftest.cases.buildhistory import BuildhistoryBase
+from oeqa.utils.commands import bitbake, get_bb_var
+
+class BuildhistoryTests(BuildhistoryBase):
+
+def test_write_license_to_latest_recipe(self):
+target = 'glibc'
+recipe_variables = []
+self.write_recipeinc(target, 'BUILDHISTORY_EXPORT_RECIPE_VARIABLES += 
\"LICENSE\"')
+self.run_buildhistory_operation(target)
+add_buildhistory_config = 'PACKAGE_CLASSES = \"package_ipk\"'
+self.append_config(add_buildhistory_config)
+self.assertTrue(os.path.isdir(get_bb_var('BUILDHISTORY_DIR')), 
"buildhistory dir was not created.")
+pkghistdir = get_bb_var('BUILDHISTORY_DIR')
+PACKAGE_ARCH = get_bb_var('MULTIMACH_TARGET_SYS')
+bitbake('-c package_write_ipk -f %s' % target)
+infofile = "{}/packages/{}/{}/latest".format(pkghistdir, PACKAGE_ARCH, 
target)
+expected = "LICENSE = GPLv2 & LGPLv2.1"
+result = False
+with open(infofile, "r") as f:
+for line in f:
+if line.strip() == expected:
+result = True
+break
+if not result:
+raise AssertionError("Expected License not found")
+
+def test_write_license_to_latest_package(self):
+target = 'glibc'
+recipe_variables = []
+self.write_recipeinc(target, 'BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += 
\"LICENSE\"')
+self.run_buildhistory_operation(target)
+add_buildhistory_config = 'PACKAGE_CLASSES = \"package_ipk\"'
+self.append_config(add_buildhistory_config)
+self.assertTrue(os.path.isdir(get_bb_var('BUILDHISTORY_DIR')), 
"buildhistory dir was not created.")
+bitbake('-c package_write_ipk -f %s' % target)
+pkghistdir = get_bb_var('BUILDHISTORY_DIR')
+PACKAGE_ARCH = get_bb_var('MULTIMACH_TARGET_SYS')
+infofile = "{}/packages/{}/{}/{}-dbg/latest".format(pkghistdir, 
PACKAGE_ARCH, target, target)
+expected = "LICENSE = GPLv2 & LGPLv2.1"
+result = False
+with open(infofile, "r") as f:
+for line in f:
+if line.strip() == expected:
+result = True
+break
+if not result:
+raise AssertionError("Expected License not found")
-- 
2.17.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#161539): 
https://lists.openembedded.org/g/openembedded-core/message/161539
Mute This Topic: https://lists.openembedded.org/mt/89017597/21656
Group Owner: openembedded-core+ow...@lists.openembedded.org
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub 
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[OE-core] [poky][master][PATCH 1/2] buildhistory.bbclass: Enable exporting more recipe and package data

[sana kazi]

Used BUILDHISTORY_EXPORT_RECIPE_VARIABLES and
BUILDHISTORY_EXPORT_PACKAGE_VARIABLES to export recipe and package
data to the latest file of buildhistory and sorted it alphabetically.

This makes extending data in buildhistory git tree simple and avoids
patches to it for users who care about things like SRC_URI and like
to track it in buildhistory git tree.

Now we can add additional information as per our requirement to the
buildhistory like LICENSE, SRC_URI AND MAINTAINER to the buildhistory
by appending them in a recipe or distro specific conf file as follows:

BUILDHISTORY_EXPORT_RECIPE_VARIABLES += "MAINTAINER"
BUILDHISTORY_EXPORT_PACKAGE_VARIABLES += "MAINTAINER"

Signed-off-by: Sana Kazi 
Signed-off-by: Sana Kazi 
---
 meta-poky/conf/distro/poky.conf   |   2 +
 meta/classes/buildhistory.bbclass | 106 +++---
 2 files changed, 70 insertions(+), 38 deletions(-)

diff --git a/meta-poky/conf/distro/poky.conf b/meta-poky/conf/distro/poky.conf
index 2dc3606ae5..c382493dbc 100644
--- a/meta-poky/conf/distro/poky.conf
+++ b/meta-poky/conf/distro/poky.conf
@@ -72,3 +72,5 @@ INHERIT += "uninative"
 
 BB_SIGNATURE_HANDLER ?= "OEEquivHash"
 BB_HASHSERVE ??= "auto"
+BUILDHISTORY_EXPORT_RECIPE_VARIABLES ?= "PR PV PE LAYER DEPENDS PACKAGES 
SRC_URI LICENSE CONFIG"
+BUILDHISTORY_EXPORT_PACKAGE_VARIABLES ?= "PE PV PR PKG PKGE PKGV PKGR 
RPROVIDES RDEPENDS RRECOMMENDS RSUGGESTS RREPLACES RCONFLICTS PKGSIZE FILES 
FILELIST"
diff --git a/meta/classes/buildhistory.bbclass 
b/meta/classes/buildhistory.bbclass
index daa96f3b63..04837cafc4 100644
--- a/meta/classes/buildhistory.bbclass
+++ b/meta/classes/buildhistory.bbclass
@@ -264,12 +264,11 @@ python buildhistory_emit_pkghistory() {
 rcpinfo.pe = pe
 rcpinfo.pv = pv
 rcpinfo.pr = pr
-rcpinfo.depends = sortlist(oe.utils.squashspaces(d.getVar('DEPENDS') or 
""))
 rcpinfo.packages = packages
 rcpinfo.layer = layer
-rcpinfo.license = license
 rcpinfo.config = sortlist(oe.utils.squashspaces(d.getVar('PACKAGECONFIG') 
or ""))
-rcpinfo.src_uri = oe.utils.squashspaces(d.getVar('SRC_URI') or "")
+export_recipe_variables = d.getVar('BUILDHISTORY_EXPORT_RECIPE_VARIABLES') 
or ''
+rcpinfo.export_recipe_variables = export_recipe_variables
 write_recipehistory(rcpinfo, d)
 
 bb.build.exec_func("read_subpackage_metadata", d)
@@ -323,6 +322,9 @@ python buildhistory_emit_pkghistory() {
 
 pkginfo.size = int(localdata.getVar('PKGSIZE') or '0')
 
+export_package_variables = 
d.getVar('BUILDHISTORY_EXPORT_PACKAGE_VARIABLES') or ''
+pkginfo.export_package_variables = export_package_variables
+
 write_pkghistory(pkginfo, d)
 
 oe.qa.exit_if_errors(d)
@@ -370,17 +372,22 @@ def write_recipehistory(rcpinfo, d):
 pkghistdir = d.getVar('BUILDHISTORY_DIR_PACKAGE')
 
 infofile = os.path.join(pkghistdir, "latest")
+export_recipe_variables = set(rcpinfo.export_recipe_variables.split())
+ret = []
 with open(infofile, "w") as f:
-if rcpinfo.pe != "0":
-f.write(u"PE = %s\n" %  rcpinfo.pe)
-f.write(u"PV = %s\n" %  rcpinfo.pv)
-f.write(u"PR = %s\n" %  rcpinfo.pr)
-f.write(u"DEPENDS = %s\n" %  rcpinfo.depends)
-f.write(u"PACKAGES = %s\n" %  rcpinfo.packages)
-f.write(u"LAYER = %s\n" %  rcpinfo.layer)
-f.write(u"LICENSE = %s\n" %  rcpinfo.license)
-f.write(u"CONFIG = %s\n" %  rcpinfo.config)
-f.write(u"SRC_URI = %s\n" %  rcpinfo.src_uri)
+for var in export_recipe_variables:
+if var == "PE":
+if rcpinfo.pe != "0":
+ret.append("%s = %s" % (var, rcpinfo.pe))
+elif var == "LAYER":
+ret.append("%s = %s" % (var, rcpinfo.layer))
+elif var == "CONFIG":
+ret.append("%s = %s" % (var, rcpinfo.config))
+else:
+ret.append("%s = %s" % (var," 
".join((str(d.getVar(var)).split()
+ret.sort()
+for element in ret:
+f.write(element + "\n")
 
 write_latest_srcrev(d, pkghistdir)
 
@@ -394,32 +401,55 @@ def write_pkghistory(pkginfo, d):
 bb.utils.mkdirhier(pkgpath)
 
 infofile = os.path.join(pkgpath, "latest")
+export_package_variables = set(pkginfo.export_package_variables.split())
+ret = []
 with open(infofile, "w") as f:
-if pkginfo.pe != "0":
-f.write(u"PE = %s\n" %  pkginfo.pe)
-f.write(u"PV = %s\n" %  pkginfo.pv)
-f.write(u"PR = %s\n" %  pkginfo.pr)
-
-if pkginfo.pkg != pkginfo.name:
-f.write(u"PKG = %s\n" % pkginfo.pkg)
-if pkginfo.pkge != pkginfo.pe:
-f.write(u"PKGE = %s\n" % pkginfo.pkge)
-if pkginfo.pkgv != pkginfo.pv:
-f.write(u"PKGV = %s\n" % pkginfo.pkgv)
-if pkginfo.pkgr != pkginfo.pr:
-f.write(u"PKGR = %s\n" % pkginfo.pkgr)
-f.write(u"RPROVIDES = %s\n" %  pkginfo.rprovides)
-