Re: [OE-core] Improve npm support to run build scripts

2021-10-05 Thread Chuck Wolber
On Tue, Oct 5, 2021 at 12:29 PM Konrad Weihmann 
wrote:

>
> While personally I think in the long run, every npm dependency has to be
> provided as a recipe of its own (even I know the costs of that pretty
> well)... esp when CVE checking and basic packaging hygiene should be
> enforced.
>

Emphatically agree. The "stuff it all into one recipe" npm approach is very
broken.

..Ch:W..


-- 
*"Perfection must be reached by degrees; she requires the slow hand of
time." - Voltaire*

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156672): 
https://lists.openembedded.org/g/openembedded-core/message/156672
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] Fix rust-native build issue when debug is enabled

2021-10-05 Thread Randy MacLeod

On 2021-09-29 9:20 a.m., Pgowda wrote:

When DEBUG_BUILD is set for building rust-native, it generated
error as follows:-
=
Building : rustdoc, rustdoc-json-types
error[E0463]: can't find crate for `rustc_llvm`
which `rustc_driver` depends on
   --> src/librustdoc/lib.rs:37:1
|
37 | extern crate rustc_driver;
| ^^ can't find crate
=
On analyzing the issue, it was found that rustc_llvm crate was present
at required path. However, it was very huge due to the presence of
debugging information. Hence, it was somehow not recognized as a valid
crate. 


So we need to know more about this. What tool is being used to identify
the crate and has there been any changes to fix is since 1.54?

Also, please check this problem still happens with Alex's 1.55 upgrade:

http://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=akanavin/package-version-updates




The following patch removes the debug information from
rust-llvm-native which is built prior to rust-native but retains debug
information as required in rust-native binaries.


This is a functional work-around but I suspect that we'll hold-off
for a while before giving in and accepting it in oe-core/master.
Some people might find it useful so thanks for posting it as I suggested.

Hopefully we can better understand and fix the root cause.

Thanks Naveen,

../Randy



Signed-off-by: Pgowda 
---
  meta/recipes-devtools/rust/rust-llvm.inc | 5 +
  1 file changed, 5 insertions(+)

diff --git a/meta/recipes-devtools/rust/rust-llvm.inc 
b/meta/recipes-devtools/rust/rust-llvm.inc
index d7f445385b..0f8fb785b7 100644
--- a/meta/recipes-devtools/rust/rust-llvm.inc
+++ b/meta/recipes-devtools/rust/rust-llvm.inc
@@ -15,6 +15,11 @@ DEPENDS += "ninja-native rust-llvm-native"
  ARM_INSTRUCTION_SET:armv5 = "arm"
  ARM_INSTRUCTION_SET:armv4t = "arm"
  
+# rustc_llvm with debug info is not recognized as a valid crate that's

+# generated by rust-llvm-native.
+CFLAGS:remove = "-g"
+CXXFLAGS:remove = "-g"
+
  LLVM_DIR = "llvm${LLVM_RELEASE}"
  
  EXTRA_OECMAKE = " \









--
# Randy MacLeod
# Wind River Linux


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156671): 
https://lists.openembedded.org/g/openembedded-core/message/156671
Mute This Topic: https://lists.openembedded.org/mt/85948023/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] linux-yocto: add libmpc-native to DEPENDS

2021-10-05 Thread Bruce Ashfield
On Tue, Oct 5, 2021 at 10:07 AM Ross Burton  wrote:
>
> 5.14 changed how the GCC plugins are built, which means they now
> depend on both GMP and MPC to be built. We already depend on gmp-native,
> so add libmpc-native aswell.

What's the symptom when the native dependency isn't around ? I'm just
wondering why none of my tests have picked this up. Is it only showing
on ARM hosts ? Something else ?

linux-yocto-dev can use this as well,  I can take care of that, if you
don't have the cycles.

I'm also factoring some of these things into kernel.bbclass, but this
makes sense in the recipe for now.

Bruce

>
> Signed-off-by: Ross Burton 
> ---
>  meta/recipes-kernel/linux/linux-yocto_5.14.bb | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-kernel/linux/linux-yocto_5.14.bb 
> b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
> index 0c6fbff75e..8c44c294bd 100644
> --- a/meta/recipes-kernel/linux/linux-yocto_5.14.bb
> +++ b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
> @@ -46,7 +46,7 @@ LINUX_VERSION ?= "5.14.6"
>
>  DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
>  DEPENDS += "openssl-native util-linux-native"
> -DEPENDS += "gmp-native"
> +DEPENDS += "gmp-native libmpc-native"
>
>  PV = "${LINUX_VERSION}+git${SRCPV}"
>
> --
> 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 (#156670): 
https://lists.openembedded.org/g/openembedded-core/message/156670
Mute This Topic: https://lists.openembedded.org/mt/86092630/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][dunfell] linux-yocto/5.4: update to v5.4.150

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

3a7dc5b4cfbd Linux 5.4.150
27f8c4402c4a qnx4: work around gcc false positive warning bug
3a0f951e3725 xen/balloon: fix balloon kthread freezing
f80b6793811d arm64: dts: marvell: armada-37xx: Extend PCIe MEM space
04783de9c0f3 thermal/drivers/int340x: Do not set a wrong tcc offset on 
resume
de1c3506806d EDAC/synopsys: Fix wrong value type assignment for edac_mode
8ede848bc99e spi: Fix tegra20 build with CONFIG_PM=n
d193f7dbf4ec net: 6pack: Fix tx timeout and slot time
fa56f2c987c7 alpha: Declare virt_to_phys and virt_to_bus parameter as 
pointer to volatile
af4a142ab798 arm64: Mark __stack_chk_guard as __ro_after_init
aeb19da46c7d parisc: Use absolute_pointer() to define PAGE0
8cd34eb616d9 qnx4: avoid stringop-overread errors
1214ace61402 sparc: avoid stringop-overread errors
113a8edfb9c9 net: i825xx: Use absolute_pointer for memcpy from fixed memory 
location
2397ea2db22b compiler.h: Introduce absolute_pointer macro
d12ddd843f18 blk-cgroup: fix UAF by grabbing blkcg lock before destroying 
blkg pd
9d7798823264 sparc32: page align size in arch_dma_alloc
ec49f3f7f669 nvme-multipath: fix ANA state updates when a namespace is not 
present
29917bbb07c3 xen/balloon: use a kernel thread instead a workqueue
93937596e065 bpf: Add oversize check before call kvcalloc()
7273cb182f13 ipv6: delay fib6_sernum increase in fib6_add
7432ecc55fe9 m68k: Double cast io functions to unsigned long
29c70b0d335a net: stmmac: allow CSR clock of 300MHz
1da750d1e214 net: macb: fix use after free on rmmod
ebb8d26d93c3 blktrace: Fix uaf in blk_trace access after removing by sysfs
2b5befcd4045 md: fix a lock order reversal in md_alloc
42d3711c2378 irqchip/gic-v3-its: Fix potential VPE leak on error
71f323f60592 irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
1b59625da697 scsi: lpfc: Use correct scnprintf() limit
30d373dc3501 scsi: qla2xxx: Restore initiator in dual mode
d140ccb140c2 cifs: fix a sign extension bug
1c1062c5cf21 thermal/core: Potential buffer overflow in 
thermal_build_list_of_policies()
b869901caba4 fpga: machxo2-spi: Fix missing error code in 
machxo2_write_complete()
0ebc3e688f54 fpga: machxo2-spi: Return an error on failure
5bcead7cde68 tty: synclink_gt: rename a conflicting function name
c5f27aedf6bb tty: synclink_gt, drop unneeded forward declarations
1deb94d37a7e scsi: iscsi: Adjust iface sysfs attr detection
d0f4a2eeebbe net/mlx4_en: Don't allow aRFS for encapsulated packets
ae7b957ef003 qed: rdma - don't wait for resources under hw error recovery 
flow
23716d7153fc gpio: uniphier: Fix void functions to remove return value
f7fb7dbdfb25 net/smc: add missing error check in smc_clc_prfx_set()
363438ed5de0 bnxt_en: Fix TX timeout when TX ring size is set to the 
smallest
4c4c3052911b enetc: Fix illegal access when reading affinity_hint
cf9138c966dd platform/x86/intel: punit_ipc: Drop wrong use of ACPI_PTR()
a8e8b1481930 afs: Fix incorrect triggering of sillyrename on 3rd-party 
invalidation
acce91ba0d9f net: hso: fix muxed tty registration
494260e20ac2 serial: mvebu-uart: fix driver's tx_empty callback
2d7c20db7220 xhci: Set HCD flag to defer primary roothub registration
381c8ce0abc0 btrfs: prevent __btrfs_dump_space_info() to underflow its free 
space
d4ec140e7158 erofs: fix up erofs_lookup tracepoint
7751f609eadf mcb: fix error handling in mcb_alloc_bus()
406ff5bf727d USB: serial: option: add device id for Foxconn T99W265
4b2cf0faffce USB: serial: option: remove duplicate USB device ID
59564b0183cb USB: serial: option: add Telit LN920 compositions
5cc674a3f18e USB: serial: mos7840: remove duplicated 0xac24 device ID
20c9fdde30fb usb: core: hcd: Add support for deferring roothub registration
a6c7d3c2d127 Re-enable UAS for LaCie Rugged USB3-FW with fk quirk
4dc56951a8d9 staging: greybus: uart: fix tty use after free
aa2c274c279f binder: make sure fd closes complete
93fa08e9a32f USB: cdc-acm: fix minor-number release
0dc1cfa7b907 USB: serial: cp210x: add ID for GW Instek GDM-834x Digital 
Multimeter
85d3493085ab usb-storage: Add quirk for ScanLogic SL11R-IDE older than 2.6c
d4e7647695c9 xen/x86: fix PV trap handling on secondary processors
8b06b0f17f35 cifs: fix incorrect check for null pointer in header_assemble
b1f6efa27b24 usb: musb: tusb6010: uninitialized data in 
tusb_fifo_write_unaligned()
b8c806065160 usb: dwc2: gadget: Fix ISOC transfer complete handling for DDMA
ff275c870e1b usb: dwc2: gadget: Fix ISOC flow for BDMA and Slave
f013a5001b4a usb: gadget: r8a66597: fix a loop in set_feature()
aa40438c7174 ocfs2: drop acl cache for directories too

Signed-off-by: Bruce Ashfield 
---
 

[OE-core] [PATCH 1/2][dunfell] linux-yocto/5.4: update to v5.4.149

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

e74e2950a0d6 Linux 5.4.149
382526348612 drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
409cb0b3d45a rtc: rx8010: select REGMAP_I2C
43832bf76363 blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
c37a34d7975f pwm: stm32-lp: Don't modify HW state in .remove() callback
8a29e68ea8e8 pwm: rockchip: Don't modify HW state in .remove() callback
ed60d2db3171 pwm: img: Don't modify HW state in .remove() callback
b16f4acf6b65 nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
594addd4369e nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
237ca37ca5ac nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
288c8b5ba52d nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
dc70f0c8c3de nilfs2: fix NULL pointer in nilfs_##name##_attr_release
9c3ba404881d nilfs2: fix memory leak in nilfs_sysfs_create_device_group
fb4c7d2923de btrfs: fix lockdep warning while mounting sprout fs
3f2d5c11bef8 ceph: lockdep annotations for try_nonblocking_invalidate
3bbb11261a75 ceph: request Fw caps before updating the mtime in 
ceph_write_iter
2c89a856fa49 dmaengine: xilinx_dma: Set DMA mask for coherent APIs
2f3206199dc9 dmaengine: ioat: depends on !UML
644f1e87fe73 dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
445a3379f6df parisc: Move pci_dev_is_behind_card_dino to where it is used
2f7bfc07e386 drivers: base: cacheinfo: Get rid of 
DEFINE_SMP_CALL_CACHE_FUNCTION()
a12743d07249 thermal/core: Fix thermal_cooling_device_register() prototype
c7b9a866ee25 Kconfig.debug: drop selecting non-existing 
HARDLOCKUP_DETECTOR_ARCH
3c1d9b650c08 net: stmmac: reset Tx desc base address before restarting Tx
729f9d5ee374 phy: avoid unnecessary link-up delay in polling mode
81e6b51709da pwm: lpc32xx: Don't modify HW state in .probe() after the PWM 
chip was registered
b94def8a475f profiling: fix shift-out-of-bounds bugs
7e98111cb28e nilfs2: use refcount_dec_and_lock() to fix potential UAF
5607b1bae1c8 prctl: allow to setup brk for et_dyn executables
b40301607ca8 9p/trans_virtio: Remove sysfs file on probe failure
c3b45ea0a3c8 thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
e1060803039d dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
93f8a98ad89c um: virtio_uml: fix memory leak on init failures
4cd05e390a3b staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
2f4b67bceb09 sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
cbd10b118902 sctp: validate chunk size in __rcv_asconf_lookup
6a12918e9065 ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without 
DYNAMIC_FTRACE
2f7974cd7b12 ARM: 9079/1: ftrace: Add MODULE_PLTS support
1b27a03d1292 ARM: 9078/1: Add warn suppress parameter to 
arm_gen_branch_link()
490be340c86c ARM: 9077/1: PLT: Move struct plt_entries definition to header
278df0646003 apparmor: remove duplicate macro list_entry_is_head()
f23763ab464f ARM: Qualify enabling of swiotlb_init()
6bfdc3056ca8 s390/pci_mmio: fully validate the VMA before calling 
follow_pte()
bd292c687390 console: consume APC, DM, DCS
b0c813fbbf75 KVM: remember position in kvm->vcpus array
5163578e9d0b PCI/ACPI: Add Ampere Altra SOC MCFG quirk
ec29e33e5cba PCI: aardvark: Fix reporting CRS value
3f0e275e43f6 PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
296895c4f0c8 PCI: aardvark: Indicate error in 'val' when config read fails
2fcb7b7a1d20 PCI: pci-bridge-emul: Fix big-endian support
07e5f23d3fa6 Linux 5.4.148
54ac8339ae99 s390/bpf: Fix 64-bit subtraction of the -0x8000 constant
a5fc48000b0e s390/bpf: Fix optimizing out zero-extensions
f7f1bac8983f net: renesas: sh_eth: Fix freeing wrong tx descriptor
3d32ce5472bb ip_gre: validate csum_start only on pull
f9b308f7302e qlcnic: Remove redundant unlock in qlcnic_pinit_from_rom
93f54354ccc8 fq_codel: reject silly quantum parameters
d448b240b175 netfilter: socket: icmp6: fix use-after-scope
b79204169de5 net: dsa: b53: Fix calculating number of switch ports
d5c0f016ae85 perf unwind: Do not overwrite 
FEATURE_CHECK_LDFLAGS-libunwind-{x86,aarch64}
114bf5776f56 ARC: export clear_user_page() for modules
9b63c27d6b70 mtd: rawnand: cafe: Fix a resource leak in the error handling 
path of 'cafe_nand_probe()'
14e0fdc43ddf PCI: Sync __pci_register_driver() stub for CONFIG_PCI=n
810f9b6f0a40 KVM: arm64: Handle PSCI resets before userspace touches vCPU 
state
5f289dcf0b02 mfd: tqmx86: Clear GPIO IRQ resource when no IRQ is set
e1746c27c373 PCI: Fix pci_dev_str_match_path() alloc while atomic bug
beaf65f0fe0c mfd: axp20x: Update AXP288 volatile ranges
4a6c7c818bcb NTB: perf: Fix an error code in perf_setup_inbuf()
5a1614194963 

[OE-core] [PATCH 7/7] kernel-yocto: don't apply config metadata patches twice

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

Signed-off-by: Bruce Ashfield 
---
 meta/classes/kernel-yocto.bbclass | 5 -
 1 file changed, 4 insertions(+), 1 deletion(-)

diff --git a/meta/classes/kernel-yocto.bbclass 
b/meta/classes/kernel-yocto.bbclass
index 549dfd97a4..1d5a8cdf29 100644
--- a/meta/classes/kernel-yocto.bbclass
+++ b/meta/classes/kernel-yocto.bbclass
@@ -36,7 +36,10 @@ def find_patches(d,subdir):
 if subdir == patchdir:
 patch_list.append(local)
 else:
-patch_list.append(local)
+# skip the patch if a patchdir was supplied, it won't be handled
+# properly
+if not patchdir:
+patch_list.append(local)
 
 return patch_list
 
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156667): 
https://lists.openembedded.org/g/openembedded-core/message/156667
Mute This Topic: https://lists.openembedded.org/mt/86108495/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 6/7] linux-yocto/5.14: update to v5.14.9

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

70248e7b378b Linux 5.14.9
f6fceb4e9ce6 usb: gadget: f_uac2: Populate SS descriptors' wBytesPerInterval
007574d6ac26 usb: gadget: f_uac2: Add missing companion descriptor for 
feedback EP
d401d7d2f5c8 nvmet: fix a width vs precision bug in 
nvmet_subsys_attr_serial_show()
958c616efce3 qnx4: work around gcc false positive warning bug
f67f85ec19fa xen/balloon: fix balloon kthread freezing
8ea750370cd6 software node: balance refcount for managed software nodes
62a27861b4ea USB: serial: cp210x: fix dropped characters with CP2102
7b389ef53115 arm64: add MTE supported check to thread switching and syscall 
entry/exit
338db6ec41ca irqchip/armada-370-xp: Fix ack/eoi breakage
8467f200fd38 thermal/drivers/int340x: Do not set a wrong tcc offset on 
resume
fe5eaf1cdf9c x86/setup: Call early_reserve_memory() earlier
5111b05125bd EDAC/dmc520: Assign the proper type to dimm->edac_mode
845350d4e34b EDAC/synopsys: Fix wrong value type assignment for edac_mode
ef8eac0c61d7 Revert drm/vc4 hdmi runtime PM changes
8aef50b390c4 libperf evsel: Make use of FD robust.
5f35f78ead51 spi: Fix tegra20 build with CONFIG_PM=n
9367a8fbd9d9 net: 6pack: Fix tx timeout and slot time
501b0fa2f7f2 alpha: Declare virt_to_phys and virt_to_bus parameter as 
pointer to volatile
95d6bf1d19fd arm64: Mark __stack_chk_guard as __ro_after_init
28f2eee9fc03 amd/display: enable panel orientation quirks
fca67e1c4b8c drm/amd/display: Link training retry fix for abort case
76438685048a drm/amd/display: Fix unstable HPCP compliance on Chrome Barcelo
b58ffd21ec45 drm/amdkfd: make needs_pcie_atomics FW-version dependent
47c6e796abe4 parisc: Use absolute_pointer() to define PAGE0
01452e3c727e qnx4: avoid stringop-overread errors
dd24b4ba2d8d sparc: avoid stringop-overread errors
32f93161620a net: i825xx: Use absolute_pointer for memcpy from fixed memory 
location
eb136917b022 compiler.h: Introduce absolute_pointer macro
7c2c69e01043 blk-cgroup: fix UAF by grabbing blkcg lock before destroying 
blkg pd
a5067abc52ef block: flush the integrity workqueue in 
blk_integrity_unregister
282aed19c590 block: check if a profile is actually registered in 
blk_integrity_unregister
e7f8b507fe58 drm/ttm: fix type mismatch error on sparc64
2b60676ac850 amd/display: downgrade validation failure log level
5780971d7dbd sparc32: page align size in arch_dma_alloc
d268a182c56e nvme-rdma: destroy cm id before destroy qp to avoid use after 
free
e0b9644a4903 nvme-multipath: fix ANA state updates when a namespace is not 
present
922fd5b6bb13 xen/balloon: use a kernel thread instead a workqueue
b5fe7cdfee59 bpf: Add oversize check before call kvcalloc()
ded7d5c44d8a cpufreq: intel_pstate: Override parameters if HWP forced by 
BIOS
de4afec2d294 dma-debug: prevent an error message from causing runtime 
problems
4a23ae2c6a60 ipv6: delay fib6_sernum increase in fib6_add
88ad6f3803ca m68k: Double cast io functions to unsigned long
5cee359945e0 blk-mq: avoid to iterate over stale request
cde9ad77f20b net: stmmac: allow CSR clock of 300MHz
4ad6f2d23b0f net: macb: fix use after free on rmmod
b7646fadde06 net: phylink: Update SFP selected interface on advertising 
changes
a5f8e8619261 blktrace: Fix uaf in blk_trace access after removing by sysfs
2f6caa538735 io_uring: don't punt files update to io-wq unconditionally
05ac8e4c8aec io_uring: put provided buffer meta data under memcg accounting
24d38dcce407 io_uring: fix missing set of EPOLLONESHOT for CQ ring overflow
4e81f12cc00c io_uring: fix race between poll completion and cancel_hash 
insertion
6724710fd8d4 x86/asm: Fix SETZ size enqcmds() build failure
a46d5e3603bd md: fix a lock order reversal in md_alloc
e0c1c2e5da19 irqchip/gic-v3-its: Fix potential VPE leak on error
546886700105 irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
329cb72b3241 scsi: lpfc: Use correct scnprintf() limit
f56250ae28af scsi: qla2xxx: Restore initiator in dual mode
e607120e15b0 scsi: ufs: core: Unbreak the reset handler
1d65bff00936 scsi: ufs: Retry aborted SCSI commands instead of completing 
these successfully
4368d7a1aa0f scsi: ufs: Revert "Utilize Transfer Request List Completion 
Notification Register"
1fc9119eda5b scsi: sd_zbc: Support disks with more than 2**32 logical blocks
309c4b00c687 cifs: fix a sign extension bug
a5024c719888 thermal/core: Potential buffer overflow in 
thermal_build_list_of_policies()
ed1e0252111b nvme: keep ctrl->namespaces ordered
08a14a654f4f nvme-tcp: fix incorrect h2cdata pdu offset accounting
8cd1ae341b22 x86/fault: Fix wrong signal when vsyscall fails with pkey
bfacc1de136d fpga: machxo2-spi: Fix missing error code in 

[OE-core] [PATCH 1/7] linux-yocto/5.14: scripts/gcc-plugins: consistently use HOSTCC

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

Integrating the following commit(s) to linux-yocto/5.14:

724df5812165 scripts/gcc-plugins: consistently use HOSTCC

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

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
index a147e632e4..06064706e0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
@@ -11,8 +11,8 @@ python () {
 raise bb.parse.SkipRecipe("Set PREFERRED_PROVIDER_virtual/kernel to 
linux-yocto-rt to enable it")
 }
 
-SRCREV_machine ?= "7630ebb9fd510cf7aa31b6f1dd472f3b0442afb3"
-SRCREV_meta ?= "42d2cf670ed06f42a035611a519ea68e2d26"
+SRCREV_machine ?= "87e920626b63515458e304527509289993be2796"
+SRCREV_meta ?= "a1e3f40a0f4c5d05d1a6110a42d53eb3c3947ec8"
 
 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.14;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
index 20ff40d267..699c8c7da0 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
@@ -15,9 +15,9 @@ DEPENDS += "openssl-native util-linux-native"
 KMETA = "kernel-meta"
 KCONF_BSP_AUDIT_LEVEL = "2"
 
-SRCREV_machine:qemuarm ?= "ee2ccc84e65ade5ba0f8e1a700fba29a755746a1"
-SRCREV_machine ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_meta ?= "42d2cf670ed06f42a035611a519ea68e2d26"
+SRCREV_machine:qemuarm ?= "f956536237159b85f94d70bb9e74b5894e6bf07d"
+SRCREV_machine ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_meta ?= "a1e3f40a0f4c5d05d1a6110a42d53eb3c3947ec8"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
index 0c6fbff75e..809b6fa066 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
@@ -13,17 +13,17 @@ KBRANCH:qemux86  ?= "v5.14/standard/base"
 KBRANCH:qemux86-64 ?= "v5.14/standard/base"
 KBRANCH:qemumips64 ?= "v5.14/standard/mti-malta64"
 
-SRCREV_machine:qemuarm ?= "8226a3a65df2dbae0fe71e9ff54cba70a9ba85e5"
-SRCREV_machine:qemuarm64 ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemumips ?= "b5389debd85300e24b877f25c2e90381f1df7678"
-SRCREV_machine:qemuppc ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemuriscv64 ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemuriscv32 ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemux86 ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemux86-64 ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_machine:qemumips64 ?= "56cc67b699194944809832f4c8f58b9828f02bf9"
-SRCREV_machine ?= "7ae156be3bdbf033839f7f3ec2e9a0b18818"
-SRCREV_meta ?= "42d2cf670ed06f42a035611a519ea68e2d26"
+SRCREV_machine:qemuarm ?= "139cd4a6ac01e83002011680d9fbb14048c1bc3a"
+SRCREV_machine:qemuarm64 ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemumips ?= "f5a73ebec6f028075220c690bbb121284313ebd3"
+SRCREV_machine:qemuppc ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemuriscv64 ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemuriscv32 ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemux86 ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemux86-64 ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_machine:qemumips64 ?= "912fc3d0cf57239e6fe5030b82165b2d6f0632e3"
+SRCREV_machine ?= "724df5812165b61d20e93866be8f3e7e1e5e6b5c"
+SRCREV_meta ?= "a1e3f40a0f4c5d05d1a6110a42d53eb3c3947ec8"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and 
you'll
 # get the /base branch, which is pure upstream -stable, and the same
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156661): 
https://lists.openembedded.org/g/openembedded-core/message/156661
Mute This Topic: https://lists.openembedded.org/mt/86108488/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/7] linux-yocto/5.10: update to v5.10.69

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

5f4196eaa90c Linux 5.10.69
7c09505e9e6b drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
83a3cb200eff sched/idle: Make the idle timer expire in hard interrupt 
context
647c19bc6102 rtc: rx8010: select REGMAP_I2C
9a14014df72d blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for 
multiple_queues
23dfb959c6cb blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
a2551d0a29e9 pwm: stm32-lp: Don't modify HW state in .remove() callback
a6a2b36a8cc4 pwm: rockchip: Don't modify HW state in .remove() callback
0a2ea5c0e5d1 pwm: img: Don't modify HW state in .remove() callback
db8838e48a0a habanalabs: add validity check for event ID received from F/W
d7736e2faa13 nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
0f36028d0133 nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
5770b54b112e nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
5acb21e30d85 nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
0480f7a480bc nilfs2: fix NULL pointer in nilfs_##name##_attr_release
d95b50ff07b8 nilfs2: fix memory leak in nilfs_sysfs_create_device_group
aa1af89a6697 btrfs: fix lockdep warning while mounting sprout fs
c43803c1aa76 btrfs: update the bdev time directly when closing
921ef7cfef15 ceph: lockdep annotations for try_nonblocking_invalidate
487ead34a208 ceph: remove the capsnaps when removing caps
386fd6fd01bd ceph: request Fw caps before updating the mtime in 
ceph_write_iter
b26ced26251c dmaengine: xilinx_dma: Set DMA mask for coherent APIs
9c1ea8537730 dmaengine: ioat: depends on !UML
35492619e010 dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
c12cf7f9afe2 dmaengine: idxd: depends on !UML
b4bb0b171b6e iommu/amd: Relocate GAMSup check to early_enable_iommus
2a07348e9821 parisc: Move pci_dev_is_behind_card_dino to where it is used
ca907291e116 dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
b9a1526d5174 drivers: base: cacheinfo: Get rid of 
DEFINE_SMP_CALL_CACHE_FUNCTION()
45bd9dd1bee8 drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
c9538018cb2d thermal/core: Fix thermal_cooling_device_register() prototype
d1f9ecc00da1 tools/bootconfig: Fix tracing_on option checking in 
ftrace2bconf.sh
912afe602eac Kconfig.debug: drop selecting non-existing 
HARDLOCKUP_DETECTOR_ARCH
e418ce8b8dfd ceph: cancel delayed work instead of flushing on mdsc teardown
8193ad306ea0 ceph: allow ceph_put_mds_session to take NULL or ERR_PTR
41aa21573486 platform/chrome: cros_ec_trace: Fix format warnings
113a69460de5 platform/chrome: sensorhub: Add trace events for sample
48271d10bf4c dmaengine: idxd: fix wq slot allocation index check
777344da345a pwm: mxs: Don't modify HW state in .probe() after the PWM chip 
was registered
322b70b522ab pwm: lpc32xx: Don't modify HW state in .probe() after the PWM 
chip was registered
c63df77c40ca PM: sleep: core: Avoid setting power.must_resume to false
74190973ab01 profiling: fix shift-out-of-bounds bugs
0796d99c1b16 nilfs2: use refcount_dec_and_lock() to fix potential UAF
30417cbeccff prctl: allow to setup brk for et_dyn executables
e464b3876b02 9p/trans_virtio: Remove sysfs file on probe failure
375e779ec32a thermal/drivers/exynos: Fix an error code in exynos_tmu_probe()
38ab04186fb3 perf tools: Allow build-id with trailing zeros
87c4144450e6 tools lib: Adopt memchr_inv() from kernel
ebcd3fd9207c perf test: Fix bpf test sample mismatch reporting
fa64b08931ee dmaengine: acpi: Avoid comparison GSI with Linux vIRQ
9d49973b0848 um: virtio_uml: fix memory leak on init failures
5d0e6a5e4441 coredump: fix memleak in dump_vma_snapshot()
6b24588708fe staging: rtl8192u: Fix bitwise vs logical operator in 
TranslateRxSignalStuff819xUsb()
ccb79116c372 sctp: add param size validation for SCTP_PARAM_SET_PRIMARY
ffca46766850 sctp: validate chunk size in __rcv_asconf_lookup
473cea4983b5 Revert "net/mlx5: Register to devlink ingress VLAN filter trap"
5ce134e65f3b ARM: 9098/1: ftrace: MODULE_PLT: Fix build problem without 
DYNAMIC_FTRACE
f91d25a7c89e ARM: 9079/1: ftrace: Add MODULE_PLTS support
ad00533858f7 ARM: 9078/1: Add warn suppress parameter to 
arm_gen_branch_link()
ce90c6706d5a ARM: 9077/1: PLT: Move struct plt_entries definition to header
eb46d7c8ae83 ARM: Qualify enabling of swiotlb_init()
79286ea830b3 s390/pci_mmio: fully validate the VMA before calling 
follow_pte()
74d54e5ceba3 console: consume APC, DM, DCS
9493e92a3953 PCI: aardvark: Fix reporting CRS value
9e766b86a9ef PCI: pci-bridge-emul: Add PCIe Root Capabilities Register
4d8524048a35 Linux 5.10.68
a23d3576215f net: dsa: bcm_sf2: Fix array overrun in 
bcm_sf2_num_active_ports()
9f2972e151dd bnxt_en: Fix 

[OE-core] [PATCH 5/7] linux-yocto/5.10: update to v5.10.70

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

f93026b28e2a Linux 5.10.70
59094296058d qnx4: work around gcc false positive warning bug
35c0dfbbd344 xen/balloon: fix balloon kthread freezing
8373d58c89be USB: serial: cp210x: fix dropped characters with CP2102
67cdb51ab5e2 thermal/drivers/int340x: Do not set a wrong tcc offset on 
resume
cc71740ee4d4 EDAC/dmc520: Assign the proper type to dimm->edac_mode
9afad85a43f5 EDAC/synopsys: Fix wrong value type assignment for edac_mode
db76cb05c046 spi: Fix tegra20 build with CONFIG_PM=n
890e25c424ea net: 6pack: Fix tx timeout and slot time
044513c1fada alpha: Declare virt_to_phys and virt_to_bus parameter as 
pointer to volatile
0a511ba6d2a7 arm64: Mark __stack_chk_guard as __ro_after_init
fec3bd622db0 parisc: Use absolute_pointer() to define PAGE0
61454e7fd624 qnx4: avoid stringop-overread errors
5520d27f02a1 sparc: avoid stringop-overread errors
8d768beaf0ef net: i825xx: Use absolute_pointer for memcpy from fixed memory 
location
e99f9032715e compiler.h: Introduce absolute_pointer macro
f58d305887ad blk-cgroup: fix UAF by grabbing blkcg lock before destroying 
blkg pd
1ef68b84bc11 block: flush the integrity workqueue in 
blk_integrity_unregister
1963bdb7489c block: check if a profile is actually registered in 
blk_integrity_unregister
526261c1b706 amd/display: downgrade validation failure log level
54a4860c6257 sparc32: page align size in arch_dma_alloc
ecf0dc5a9048 nvme-rdma: destroy cm id before destroy qp to avoid use after 
free
2a08960577af nvme-multipath: fix ANA state updates when a namespace is not 
present
372d3e6ea1e1 xen/balloon: use a kernel thread instead a workqueue
6345a0bee801 bpf: Add oversize check before call kvcalloc()
e567d33508a9 cpufreq: intel_pstate: Override parameters if HWP forced by 
BIOS
9561bb98879e ipv6: delay fib6_sernum increase in fib6_add
31df1d037cfd m68k: Double cast io functions to unsigned long
cc3dd119d3cf blk-mq: avoid to iterate over stale request
de7e03003367 net: stmmac: allow CSR clock of 300MHz
7721221e87d2 net: macb: fix use after free on rmmod
a632288053b7 net: phylink: Update SFP selected interface on advertising 
changes
3815fe7371d2 blktrace: Fix uaf in blk_trace access after removing by sysfs
ce092350b452 io_uring: put provided buffer meta data under memcg accounting
7040b37a9630 x86/asm: Fix SETZ size enqcmds() build failure
54e85b6c287c x86/asm: Add a missing __iomem annotation in enqcmds()
b18ba3f477a2 md: fix a lock order reversal in md_alloc
568662e37f92 irqchip/gic-v3-its: Fix potential VPE leak on error
af7c9ffe2bee irqchip/goldfish-pic: Select GENERIC_IRQ_CHIP to fix build
0595fc4794c3 scsi: lpfc: Use correct scnprintf() limit
cb948b158a86 scsi: qla2xxx: Restore initiator in dual mode
3d42ed6b7905 cifs: fix a sign extension bug
8cba4c2698e2 thermal/core: Potential buffer overflow in 
thermal_build_list_of_policies()
215df4349916 nvme: keep ctrl->namespaces ordered
55e6f8b3c0f5 treewide: Change list_sort to use const pointers
419fab1cb086 nvme-tcp: fix incorrect h2cdata pdu offset accounting
c6ecdcba9da3 fpga: machxo2-spi: Fix missing error code in 
machxo2_write_complete()
5c6bfde245d8 fpga: machxo2-spi: Return an error on failure
4ea4925c70fd tty: synclink_gt: rename a conflicting function name
56a8f0b18f46 tty: synclink_gt, drop unneeded forward declarations
c64e6c307a76 scsi: target: Fix the pgr/alua_support_store functions
2d0305425179 scsi: iscsi: Adjust iface sysfs attr detection
0032f8b3cf2a atlantic: Fix issue in the pm resume flow.
c2598bce4152 net/mlx4_en: Don't allow aRFS for encapsulated packets
b4e54f5f4288 qed: rdma - don't wait for resources under hw error recovery 
flow
1bba406c07b3 gpio: uniphier: Fix void functions to remove return value
db94f89e1dad s390/qeth: fix NULL deref in qeth_clear_working_pool_list()
3aa50241e1ed kselftest/arm64: signal: Skip tests if required features are 
missing
91d4da33c367 kselftest/arm64: signal: Add SVE to the set of features we can 
check for
2eaa39d83e30 net: dsa: realtek: register the MDIO bus under devres
43c880b860c7 net: dsa: don't allocate the slave_mii_bus using devres
b4561bd29e62 net/smc: fix 'workqueue leaked lock' in smc_conn_abort_work
8a00c832ef88 net/smc: add missing error check in smc_clc_prfx_set()
4e0fd1d79534 net: hns3: check queue id range before using
ca435999bcaf net: hns3: fix change RSS 'hfunc' ineffective issue
1365a0dc5596 bnxt_en: Fix TX timeout when TX ring size is set to the 
smallest
d5afe3cf52e5 enetc: Fix uninitialized struct dim_sample field usage
6c3f1b741c6c enetc: Fix illegal access when reading affinity_hint
117661cb9d3a platform/x86/intel: punit_ipc: Drop wrong use of 

[OE-core] [PATCH 3/7] linux-yocto/5.14: bsp/qemuarm*-gfx: use virtio graphics

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

Integrating the following configuration change:

  Author: Jon Mason 
  Date:   Thu Sep 16 18:22:33 2021 -0400

  bsp/qemuarm*-gfx: use virtio graphics

  Remove Bochs and start using virtio graphics

  Signed-off-by: Jon Mason 

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

diff --git a/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
index 5e5be1362a..a16612eb31 100644
--- a/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-rt_5.14.bb
@@ -12,7 +12,7 @@ python () {
 }
 
 SRCREV_machine ?= "61d40facfa18554ae6c57cd4d3cab9be8272e177"
-SRCREV_meta ?= "cb45cbb1f55bc80b49d8b037d3b89121841a5963"
+SRCREV_meta ?= "bb52c5cfd4b600d9fb4413ff1a668b47f1937057"
 
 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.14;destsuffix=${KMETA}"
diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
index 8ba2d0a737..89696fbec2 100644
--- a/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto-tiny_5.14.bb
@@ -17,7 +17,7 @@ KCONF_BSP_AUDIT_LEVEL = "2"
 
 SRCREV_machine:qemuarm ?= "372ed9b008af35e56e5dacc906522203a4dd897b"
 SRCREV_machine ?= "b6850b99071366f57df504f6deefbd0276189554"
-SRCREV_meta ?= "cb45cbb1f55bc80b49d8b037d3b89121841a5963"
+SRCREV_meta ?= "bb52c5cfd4b600d9fb4413ff1a668b47f1937057"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
diff --git a/meta/recipes-kernel/linux/linux-yocto_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
index 4fec074a58..47ada6e184 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
@@ -23,7 +23,7 @@ SRCREV_machine:qemux86 ?= 
"b6850b99071366f57df504f6deefbd0276189554"
 SRCREV_machine:qemux86-64 ?= "b6850b99071366f57df504f6deefbd0276189554"
 SRCREV_machine:qemumips64 ?= "d333b4641aa536e004174d65a3e91f0018eedf43"
 SRCREV_machine ?= "b6850b99071366f57df504f6deefbd0276189554"
-SRCREV_meta ?= "cb45cbb1f55bc80b49d8b037d3b89121841a5963"
+SRCREV_meta ?= "bb52c5cfd4b600d9fb4413ff1a668b47f1937057"
 
 # set your preferred provider of linux-yocto to 'linux-yocto-upstream', and 
you'll
 # get the /base branch, which is pure upstream -stable, and the same
-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156663): 
https://lists.openembedded.org/g/openembedded-core/message/156663
Mute This Topic: https://lists.openembedded.org/mt/86108490/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/7] linux-yocto/5.14: update to v5.14.8

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

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

c34892e1995d Linux 5.14.8
1236431c8531 drm/nouveau/nvkm: Replace -ENOSYS with -ENODEV
bef2b32a1490 selinux,smack: fix subjective/objective credential use mixups
dcd45a08b9a6 io_uring: fix off-by-one in BUILD_BUG_ON check of 
__REQ_F_LAST_BIT
d1217e40d082 cifs: properly invalidate cached root handle when closing it
cacfce79af9b sched/idle: Make the idle timer expire in hard interrupt 
context
affd236df3e8 rtc: rx8010: select REGMAP_I2C
46384252a8f4 blk-mq: allow 4x BLK_MAX_REQUEST_COUNT at blk_plug for 
multiple_queues
a3330c1c8319 blk-throttle: fix UAF by deleteing timer in blk_throtl_exit()
2ab96bfe3201 block: genhd: don't call blkdev_show() with major_names_lock 
held
e2860e2175c0 nvmet: fixup buffer overrun in nvmet_subsys_attr_serial()
da6643141740 pwm: stm32-lp: Don't modify HW state in .remove() callback
2c92f9e8e039 pwm: rockchip: Don't modify HW state in .remove() callback
f53bd7fe1bf6 pwm: img: Don't modify HW state in .remove() callback
ddd8601dd853 habanalabs: cannot sleep while holding spinlock
f621eeead8d6 habanalabs: add "in device creation" status
836c0806500d habanalabs: fix mmu node address resolution in debugfs
46d712b46080 habanalabs: add validity check for event ID received from F/W
350b2f2b1f2a drm/amdgpu: fix fdinfo race with process exit
25b4e51e2333 drm/amd/display: Fix memory leak reported by coverity
682645659796 drm/amdgpu: Fixes to returning VBIOS RAS EEPROM address
d5b10c0b4288 habanalabs: fix nullifying of destroyed mmu pgt pool
d51100f73561 thermal/drivers/rcar_gen3_thermal: Store TSC id as unsigned int
0ea5f803c39d nilfs2: fix memory leak in nilfs_sysfs_delete_snapshot_group
7797daf14c3f nilfs2: fix memory leak in nilfs_sysfs_create_snapshot_group
6e17978ca9b8 nilfs2: fix memory leak in nilfs_sysfs_delete_##name##_group
90b8f51480a4 nilfs2: fix memory leak in nilfs_sysfs_create_##name##_group
e005476348f9 nilfs2: fix NULL pointer in nilfs_##name##_attr_release
255c3bfa2826 nilfs2: fix memory leak in nilfs_sysfs_create_device_group
0e78f3da8e58 btrfs: fix lockdep warning while mounting sprout fs
ebed7d89e54c btrfs: delay blkdev_put until after the device remove
13d4c38e5c51 btrfs: update the bdev time directly when closing
e0f8639c87e1 s390/unwind: use current_frame_address() to unwind current task
31db9b13e54e ceph: lockdep annotations for try_nonblocking_invalidate
6ca3781b4664 ceph: remove the capsnaps when removing caps
8e46eccfc10f ceph: request Fw caps before updating the mtime in 
ceph_write_iter
8e4e080b2be0 ceph: fix memory leak on decode error in ceph_handle_caps
abae6b3bab39 ACPI: PM: s2idle: Run both AMD and Microsoft methods if both 
are supported
417cd319e998 ASoC: audio-graph: respawn Platform Support
0a96c9734bd8 s390: add kmemleak annotation in stack_alloc()
5c9fc5418714 dmaengine: xilinx_dma: Set DMA mask for coherent APIs
996a4337be96 dmaengine: ioat: depends on !UML
964a98344922 cxl/pci: Introduce cdevm_file_operations
e921d59a75c7 cxl: Move cxl_core to new directory
786c11aebd4f dmaengine: sprd: Add missing MODULE_DEVICE_TABLE
70100a0fb72d dmaengine: idxd: depends on !UML
4d74704a3975 riscv: dts: microchip: mpfs-icicle: Fix serial console
f8d2c2cfbff3 of: property: Disable fw_devlink DT support for X86
f7525b4c5d40 drm/ttm: Fix a deadlock if the target BO is not idle during 
swap
3a4a126d3515 arm64: mm: limit linear region to 51 bits for KVM in nVHE mode
4ca60140f83e iommu/vt-d: Fix a deadlock in intel_svm_drain_prq()
cab628d695ab iommu/vt-d: Fix PASID leak in intel_svm_unbind_mm()
f74210e642c8 iommu/amd: Relocate GAMSup check to early_enable_iommus
2d0bfe7e6f5d parisc: Move pci_dev_is_behind_card_dino to where it is used
9a9d2fb4995a dma-buf: DMABUF_DEBUG should depend on DMA_SHARED_BUFFER
7eb2c8604702 dma-buf: DMABUF_MOVE_NOTIFY should depend on DMA_SHARED_BUFFER
0a1b8623d10c drivers: base: cacheinfo: Get rid of 
DEFINE_SMP_CALL_CACHE_FUNCTION()
52cf80714d50 drm/amdgpu: Disable PCIE_DPM on Intel RKL Platform
654b40ff096e thermal/core: Fix thermal_cooling_device_register() prototype
57df1f724b35 tracing/boot: Fix to loop on only subkeys
59faa7816df1 tools/bootconfig: Fix tracing_on option checking in 
ftrace2bconf.sh
bdf3f584913c Kconfig.debug: drop selecting non-existing 
HARDLOCKUP_DETECTOR_ARCH
71f9ab9c157c init: move usermodehelper_enable() to populate_rootfs()
4abef9e11035 math: RATIONAL_KUNIT_TEST should depend on RATIONAL instead of 
selecting it
7e68a2bd2169 SUNRPC: don't pause on incomplete allocation
bf55b052cfeb s390/entry: make oklabel within CHKSTG macro local
674534e6327e platform/chrome: cros_ec_trace: Fix format warnings
c3315f6436e7 platform/chrome: 

[OE-core] [PATCH 0/7] kernel-yocto: consolidated pull request

2021-10-05 Thread Bruce Ashfield
From: Bruce Ashfield 

Richard,

Here's the next round of -stable and bug fixes. I didn't detect any issues,
and everything is pretty routine (famous last words).

I assume the release builds are underway now, so these are for post
release, and any stable releases. But if you wanted to grab any of
them, they are all bug fix only.

Cheers,

Bruce

The following changes since commit 80f2b56ad8c270269d9f7f65cc114d8f13f9dfbb:

  reproducible_build: Work around caching issues (2021-10-04 15:03:54 +0100)

are available in the Git repository at:

  git://git.yoctoproject.org/poky-contrib zedd/kernel
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel

Bruce Ashfield (7):
  linux-yocto/5.14: scripts/gcc-plugins: consistently use HOSTCC
  linux-yocto/5.14: update to v5.14.8
  linux-yocto/5.14: bsp/qemuarm*-gfx: use virtio graphics
  linux-yocto/5.10: update to v5.10.69
  linux-yocto/5.10: update to v5.10.70
  linux-yocto/5.14: update to v5.14.9
  kernel-yocto: don't apply config metadata patches twice

 meta/classes/kernel-yocto.bbclass |  5 +++-
 .../linux/linux-yocto-rt_5.10.bb  |  6 ++---
 .../linux/linux-yocto-rt_5.14.bb  |  6 ++---
 .../linux/linux-yocto-tiny_5.10.bb|  8 +++---
 .../linux/linux-yocto-tiny_5.14.bb|  8 +++---
 meta/recipes-kernel/linux/linux-yocto_5.10.bb | 24 -
 meta/recipes-kernel/linux/linux-yocto_5.14.bb | 26 +--
 7 files changed, 43 insertions(+), 40 deletions(-)

-- 
2.19.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156660): 
https://lists.openembedded.org/g/openembedded-core/message/156660
Mute This Topic: https://lists.openembedded.org/mt/86108487/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-fitimage: use correct kernel image

2021-10-05 Thread Andrej Valek
Even if initramfs_bundle_path was used, kernel compression was not
reflected in output its image. Use linux.bin as kernel compressed output
image. File is correctly created from vmlinux which includes a right
initramfs image.

Signed-off-by: Andrej Valek 
Signed-off-by: Walter Schweizer 
---
 meta/classes/kernel-fitimage.bbclass | 17 +
 1 file changed, 1 insertion(+), 16 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 22b77f1858..7969c89f1a 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -495,22 +495,7 @@ fitimage_assemble() {
fitimage_emit_section_maint $1 imagestart
 
uboot_prep_kimage
-
-   if [ "${INITRAMFS_IMAGE_BUNDLE}" = "1" ]; then
-   
initramfs_bundle_path="arch/"${UBOOT_ARCH}"/boot/"${KERNEL_IMAGETYPE_REPLACEMENT}".initramfs"
-   if [ -e "$initramfs_bundle_path" ]; then
-
-   #
-   # Include the kernel/rootfs bundle.
-   #
-
-   fitimage_emit_section_kernel $1 $kernelcount 
"$initramfs_bundle_path" "$linux_comp"
-   else
-   bbwarn "$initramfs_bundle_pat not found."
-   fi
-   else
-   fitimage_emit_section_kernel $1 $kernelcount linux.bin 
"$linux_comp"
-   fi
+   fitimage_emit_section_kernel $1 $kernelcount linux.bin "$linux_comp"
 
#
# Step 2: Prepare a DTB image section
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156659): 
https://lists.openembedded.org/g/openembedded-core/message/156659
Mute This Topic: https://lists.openembedded.org/mt/86104017/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] featimage: refactor style

2021-10-05 Thread Andrej Valek
- use bash variable notation without {} where possible
  - just to make sure it looks like bash variable not bitbake variable one
- fix indent style in "cat" commands
- replace "! -z" -> "-n"

Signed-off-by: Andrej Valek 
---
 meta/classes/kernel-fitimage.bbclass | 292 +--
 meta/classes/uboot-sign.bbclass  |  56 ++---
 2 files changed, 174 insertions(+), 174 deletions(-)

diff --git a/meta/classes/kernel-fitimage.bbclass 
b/meta/classes/kernel-fitimage.bbclass
index 38e05153e3..22b77f1858 100644
--- a/meta/classes/kernel-fitimage.bbclass
+++ b/meta/classes/kernel-fitimage.bbclass
@@ -73,7 +73,7 @@ FIT_SIGN_INDIVIDUAL ?= "0"
 #
 # $1 ... .its filename
 fitimage_emit_fit_header() {
-   cat << EOF >> ${1}
+   cat << EOF >> $1
 /dts-v1/;
 
 / {
@@ -94,24 +94,24 @@ EOF
 fitimage_emit_section_maint() {
case $2 in
imagestart)
-   cat << EOF >> ${1}
+   cat << EOF >> $1
 
 images {
 EOF
;;
confstart)
-   cat << EOF >> ${1}
+   cat << EOF >> $1
 
 configurations {
 EOF
;;
sectend)
-   cat << EOF >> ${1}
+   cat << EOF >> $1
};
 EOF
;;
fitend)
-   cat << EOF >> ${1}
+   cat << EOF >> $1
 };
 EOF
;;
@@ -137,28 +137,28 @@ fitimage_emit_section_kernel() {
awk '$3=="${UBOOT_ENTRYSYMBOL}" {print "0x"$1;exit}'`
fi
 
-   cat << EOF >> ${1}
-kernel-${2} {
+   cat << EOF >> $1
+kernel-$2 {
 description = "Linux kernel";
-data = /incbin/("${3}");
+data = /incbin/("$3");
 type = "kernel";
 arch = "${UBOOT_ARCH}";
 os = "linux";
-compression = "${4}";
+compression = "$4";
 load = <${UBOOT_LOADADDRESS}>;
-entry = <${ENTRYPOINT}>;
+entry = <$ENTRYPOINT>;
 hash-1 {
-algo = "${kernel_csum}";
+algo = "$kernel_csum";
 };
 };
 EOF
 
-   if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a 
-n "${kernel_sign_keyname}" ] ; then
-   sed -i '$ d' ${1}
-   cat << EOF >> ${1}
+   if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a 
-n "$kernel_sign_keyname" ] ; then
+   sed -i '$ d' $1
+   cat << EOF >> $1
 signature-1 {
-algo = "${kernel_csum},${kernel_sign_algo}";
-key-name-hint = "${kernel_sign_keyname}";
+algo = "$kernel_csum,$kernel_sign_algo";
+key-name-hint = "$kernel_sign_keyname";
 };
 };
 EOF
@@ -186,26 +186,26 @@ fitimage_emit_section_dtb() {
elif [ -n "${UBOOT_DTB_LOADADDRESS}" ]; then
dtb_loadline="load = <${UBOOT_DTB_LOADADDRESS}>;"
fi
-   cat << EOF >> ${1}
-fdt-${2} {
+   cat << EOF >> $1
+fdt-$2 {
 description = "Flattened Device Tree blob";
-data = /incbin/("${3}");
+data = /incbin/("$3");
 type = "flat_dt";
 arch = "${UBOOT_ARCH}";
 compression = "none";
-${dtb_loadline}
+$dtb_loadline
 hash-1 {
-algo = "${dtb_csum}";
+algo = "$dtb_csum";
 };
 };
 EOF
 
-   if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a 
-n "${dtb_sign_keyname}" ] ; then
-   sed -i '$ d' ${1}
-   cat << EOF >> ${1}
+   if [ "${UBOOT_SIGN_ENABLE}" = "1" -a "${FIT_SIGN_INDIVIDUAL}" = "1" -a 
-n "$dtb_sign_keyname" ] ; then
+   sed -i '$ d' $1
+   cat << EOF >> $1
 signature-1 {
-algo = "${dtb_csum},${dtb_sign_algo}";
-key-name-hint = "${dtb_sign_keyname}";
+algo = "$dtb_csum,$dtb_sign_algo";
+key-name-hint = "$dtb_sign_keyname";
 };
 };
 EOF
@@ -220,29 +220,29 @@ EOF
 # $3 ... Path to boot script image
 fitimage_emit_section_boot_script() {
 
-bootscr_csum="${FIT_HASH_ALG}"
+   bootscr_csum="${FIT_HASH_ALG}"
bootscr_sign_algo="${FIT_SIGN_ALG}"
bootscr_sign_keyname="${UBOOT_SIGN_IMG_KEYNAME}"
 
-cat << EOF >> 

Re: [OE-core] Improve npm support to run build scripts

2021-10-05 Thread Konrad Weihmann



On 05.10.21 21:17, Alexander Kanavin wrote:
On Tue, 5 Oct 2021 at 19:44, Stefan Herbrechtsmeier 
> wrote:



 > A layer with thousands of recipes seems totally intractable.

What is your concern? The high number of dependencies or to handle it
via OE?


Generating recipes with a tool means the tool will be custom and 
non-standard, and chances of anyone outside of your company
understanding, using and contributing to it are rather small. There's 
also the problem of needing multiple versions of the same thing for 
different
consumer items, which oe doesn't easily support. The link Robert 
provided already exposes some of the pain points with that approach.


I tend to think the best way forward (or least painful at least) is to 
gradually improve what there already is, which is the npm class
and devtool, and send patches to various upstream njs projects when 
they're using outdated dependencies or otherwise need changing.


Alex


Just to chime in :-), I like to question this approach of having 
multiple versions of the same in an image.
As already outlined npm is horrible in many ways, but using the lockfile 
approach multiplies that even more.
But I tend to agree that using the currently available oe-core code 
would be suited best for a broader audience - in your own layer you 
simply can do whatever you like.


While personally I think in the long run, every npm dependency has to be 
provided as a recipe of its own (even I know the costs of that pretty 
well)... esp when CVE checking and basic packaging hygiene should be 
enforced.


Nevertheless for oe-core I wouldn't want to change a lot right now, as 
there is simply a valid set of consumers missing that could enable us to 
do some proper testing. But yeah fixes/improvements for devtool are very 
welcome (also the available docu might need a touch)









-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156657): 
https://lists.openembedded.org/g/openembedded-core/message/156657
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] Improve npm support to run build scripts

2021-10-05 Thread Alexander Kanavin
On Tue, 5 Oct 2021 at 19:44, Stefan Herbrechtsmeier <
stefan.herbrechtsmeier-...@weidmueller.com> wrote:

>
> > A layer with thousands of recipes seems totally intractable.
>
> What is your concern? The high number of dependencies or to handle it
> via OE?
>

Generating recipes with a tool means the tool will be custom and
non-standard, and chances of anyone outside of your company
understanding, using and contributing to it are rather small. There's also
the problem of needing multiple versions of the same thing for different
consumer items, which oe doesn't easily support. The link Robert provided
already exposes some of the pain points with that approach.

I tend to think the best way forward (or least painful at least) is to
gradually improve what there already is, which is the npm class
and devtool, and send patches to various upstream njs projects when they're
using outdated dependencies or otherwise need changing.

Alex

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156656): 
https://lists.openembedded.org/g/openembedded-core/message/156656
Mute This Topic: https://lists.openembedded.org/mt/86089523/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 v2 1/3] Rust oe-selftest script

2021-10-05 Thread Alexandre Belloni
Hello,

I got the following (cryptic) failures today:

https://autobuilder.yoctoproject.org/typhoon/#/builders/59/builds/4100/steps/18/logs/stdio

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/4094/steps/18/logs/stdio


On 29/09/2021 01:04:46-0700, Pgowda wrote:
> The file builds remote-test-server and executes rust testing
> remotely using background ssh. It adds the necessary test environment
> and variables to run the rust oe-selftest.
> 
> Print the results in case of failure of runCmd().
> 
> Signed-off-by: Pgowda 
> ---
>  meta/lib/oeqa/selftest/cases/rust.py | 53 
>  1 file changed, 53 insertions(+)
>  create mode 100644 meta/lib/oeqa/selftest/cases/rust.py
> 
> diff --git a/meta/lib/oeqa/selftest/cases/rust.py 
> b/meta/lib/oeqa/selftest/cases/rust.py
> new file mode 100644
> index 00..7978758221
> --- /dev/null
> +++ b/meta/lib/oeqa/selftest/cases/rust.py
> @@ -0,0 +1,53 @@
> +# SPDX-License-Identifier: MIT
> +import os
> +import subprocess
> +from oeqa.core.decorator import OETestTag
> +from oeqa.core.case import OEPTestResultTestCase
> +from oeqa.selftest.case import OESelftestTestCase
> +from oeqa.utils.commands import runCmd, bitbake, get_bb_var, get_bb_vars, 
> runqemu, Command
> +from oeqa.utils.sshcontrol import SSHControl
> +
> +# Total time taken for testing is of about 2hr 20min, with PARALLEL_MAKE set 
> to 40 number of jobs.
> +class RustSelfTestBase(OESelftestTestCase, OEPTestResultTestCase):
> +
> + def run_check_emulated(self, *args, **kwargs):
> + # build remote-test-server before image build
> + recipe = "rust-testsuite"
> + bitbake("{} -c compile".format(recipe))
> + builddir = get_bb_var("B", "rust-testsuite")
> + # build core-image-minimal with required packages
> + default_installed_packages = ["libgcc", "libstdc++", 
> "libatomic", "libgomp"]
> + features = []
> + features.append('IMAGE_FEATURES += "ssh-server-openssh"')
> + features.append('CORE_IMAGE_EXTRA_INSTALL += "{0}"'.format(" 
> ".join(default_installed_packages)))
> + self.write_config("\n".join(features))
> + bitbake("core-image-minimal")
> + # wrap the execution with a qemu instance
> + with runqemu("core-image-minimal", runqemuparams = "nographic", 
> qemuparams = "-m 512") as qemu:
> + # Copy remote-test-server to image through scp
> + ssh = SSHControl(ip=qemu.ip, logfile=qemu.sshlog, 
> user="root")
> + ssh.copy_to(builddir + "/" + 
> "build/x86_64-unknown-linux-gnu/stage1-tools-bin/remote-test-server","~/")
> + # Execute remote-test-server on image through 
> background ssh
> + command = '~/remote-test-server -v remote'
> + sshrun=subprocess.Popen(("ssh", '-o',  
> 'UserKnownHostsFile=/dev/null', '-o',  'StrictHostKeyChecking=no', '-f', 
> "root@%s" % qemu.ip, command),
> +shell=False,
> +stdout=subprocess.PIPE,
> +stderr=subprocess.PIPE)
> + # Get the values of variables.
> + targetsys = get_bb_var("TARGET_SYS", "rust-testsuite")
> + rustlibpath = get_bb_var("STAGING_LIBDIR_NATIVE", 
> "rust-testsuite")
> + tmpdir = get_bb_var("TMPDIR", "rust-testsuite")
> + testargs = "--no-fail-fast --bless"
> + # Set path for target-poky-linux-gcc, RUST_TARGET_PATH 
> and hosttools.
> + cmd = " export PATH=%s/../bin:$PATH;" % rustlibpath
> + cmd = cmd + " export 
> PATH=%s/../bin/%s:%s/hosttools:$PATH;" % (rustlibpath, targetsys, tmpdir)
> + cmd = cmd + " export RUST_TARGET_PATH=%s/rustlib;" % 
> rustlibpath
> + # Trigger testing.
> + cmd = cmd + " export TEST_DEVICE_ADDR=\"%s:12345\";" % 
> qemu.ip
> + cmd = cmd + " cd %s;  python3 
> src/bootstrap/bootstrap.py test %s --target %s ;" % (builddir, testargs, 
> targetsys)
> + result = runCmd(cmd)
> +
> +@OETestTag("toolchain-system")
> +class RustSelfTestSystemEmulated(RustSelfTestBase):
> + def test_rust(self):
> + self.run_check_emulated("rust")
> -- 
> 2.31.1
> 

> 
> 
> 


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156655): 
https://lists.openembedded.org/g/openembedded-core/message/156655
Mute This Topic: https://lists.openembedded.org/mt/85943724/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] Improve npm support to run build scripts

2021-10-05 Thread Robert Berger

Hi Stefan,

On 05/10/2021 15:48, Stefan Herbrechtsmeier wrote:


Is a layer with more more than 1000 recipes thinkable?


Did you have a look at this[1]?

It says: "For instance I currently am using around 10 NPM-packages, 
those culminated into (currently) 937 recipes that are required to build 
these."


[1] 
https://bitbakesoda.blogspot.com/2020/05/a-different-approach-to-npm-with-yocto.html




Regards
   Stefan


Regards,

Robert

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156654): 
https://lists.openembedded.org/g/openembedded-core/message/156654
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] Improve npm support to run build scripts

2021-10-05 Thread Stefan Herbrechtsmeier

Hi Alex,

Am 05.10.2021 um 15:10 schrieb Alexander Kanavin:
I think the supposed workflow with the new npm.class was to use 'devtool 
create' which would run some npm magic to to create a single recipe that 
has all of the npm-fetched dependencies inside SRC_URI.


There is no magic inside npm. It parse json recipes, calculate a 
dependency tree, download archives, checks the archives, unpack the 
archives and run some commands from the json recipes.


The 'devtool add' create a recipe with over 1000 dependencies. A lot of 
the dependencies have an unknown license. I have improve createtool to 
detect more licenses and fallback to the readme if no license file exist.


The npm class doesn't support run of build scripts. The build of an 
application (ex. angular) need native binaries inside its npm dependencies.


The existing solution have the same problems like embedded dependencies 
in other recipes (ex. multiple version of the same project, unneeded 
dependencies, unforeseeable downloads, pre-builds, on the fly binary 
builds, ...)


You have to fix a bug in different versions of the same project at 
different positions in the dependency tree inside multiple recipes.


The main different between a normal (ex C++) and npm project is that npm 
use many small packages as dependency.



Have you tried that?


Sure. Otherwise I haven't spot the limitations and work on improvements.


A layer with thousands of recipes seems totally intractable.


What is your concern? The high number of dependencies or to handle it 
via OE?


We have the high number of dependencies in any case and need to handle 
the proxy/CVE/license problem. Could we reuse OE or should we use 
different software for the same problems?


Regards
  Stefan

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



[OE-core] machine/qemuarm*: Fix UBOOT_MACHINE value

2021-10-05 Thread Daiane Angolini
Signed-off-by: Daiane Angolini 
---
 meta/conf/machine/qemuarm.conf   | 2 +-
 meta/conf/machine/qemuarm64.conf | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/conf/machine/qemuarm.conf b/meta/conf/machine/qemuarm.conf
index d71a793edf..1bd4e3e154 100644
--- a/meta/conf/machine/qemuarm.conf
+++ b/meta/conf/machine/qemuarm.conf
@@ -7,7 +7,7 @@ require conf/machine/include/qemu.inc
 
 KERNEL_IMAGETYPE = "zImage"
 
-UBOOT_MACHINE ?= "qemu:arm_defconfig"
+UBOOT_MACHINE ?= "qemu_arm_defconfig"
 
 SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
diff --git a/meta/conf/machine/qemuarm64.conf b/meta/conf/machine/qemuarm64.conf
index 3b08dedddc..f245152168 100644
--- a/meta/conf/machine/qemuarm64.conf
+++ b/meta/conf/machine/qemuarm64.conf
@@ -7,7 +7,7 @@ require conf/machine/include/qemu.inc
 
 KERNEL_IMAGETYPE = "Image"
 
-UBOOT_MACHINE ?= "qemu:arm64_defconfig"
+UBOOT_MACHINE ?= "qemu_arm64_defconfig"
 
 SERIAL_CONSOLES ?= "115200;ttyAMA0 115200;hvc0"
 SERIAL_CONSOLES_CHECK = "${SERIAL_CONSOLES}"
-- 
2.30.2


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156652): 
https://lists.openembedded.org/g/openembedded-core/message/156652
Mute This Topic: https://lists.openembedded.org/mt/86098493/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 v2 3/3] Rust oe-selftest file

2021-10-05 Thread Alexandre Belloni
On 05/10/2021 12:13:56-0400, Randy MacLeod wrote:
> On 2021-09-30 12:31 a.m., Pgowda wrote:
> > Hi Alexandre,
> > 
> > Thanks for mentioning it.
> > 
> > It's already been taken care of as the following patch:-
> > http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next=50f7a13e69e8987b3629d455f9f56720c376e89b
> 
> Hi Naveen,
> 
> That link is for a commit in master-next that is no longer valid.
> I guess you should send a v3.
> 

That's fine, I'm also carrying the patch in kirkstone-next now


-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156651): 
https://lists.openembedded.org/g/openembedded-core/message/156651
Mute This Topic: https://lists.openembedded.org/mt/85943726/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 v2 3/3] Rust oe-selftest file

2021-10-05 Thread Randy MacLeod

On 2021-09-30 12:31 a.m., Pgowda wrote:

Hi Alexandre,

Thanks for mentioning it.

It's already been taken care of as the following patch:-
http://git.yoctoproject.org/cgit.cgi/poky/commit/?h=master-next=50f7a13e69e8987b3629d455f9f56720c376e89b


Hi Naveen,

That link is for a commit in master-next that is no longer valid.
I guess you should send a v3.

../Randy



Thanks & Regards,
pgowda


On Thu, Sep 30, 2021 at 4:29 AM Alexandre Belloni
 wrote:


Hello,

On 29/09/2021 01:04:48-0700, Pgowda wrote:

Add file for rust oe-selftest

Signed-off-by: Pgowda 
---
  meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb | 3 +++
  1 file changed, 3 insertions(+)
  create mode 100644 meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb

diff --git a/meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb 
b/meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb
new file mode 100644
index 00..ad758b71f4
--- /dev/null
+++ b/meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb
@@ -0,0 +1,3 @@
+require rust-testsuite.inc
+require rust-source-${PV}.inc
+require rust-snapshot-${PV}.inc


Unless I missed something, this is missing a maintainer entry:

The following recipes do not have a maintainer assigned to them. Please add an 
entry to meta/conf/distro/include/maintainers.inc file.
rust-testsuite 
(/home/pokybuild/yocto-worker/oe-selftest-centos/build/meta/recipes-devtools/rust/rust-testsuite_1.54.0.bb)


--
2.31.1










--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com







--
# Randy MacLeod
# Wind River Linux


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



[OE-core] Yocto Project Status WW40`21

2021-10-05 Thread Stephen Jolley
Current Dev Position: YP 3.4 M4

Next Deadline: 4th Oct. 2021 YP 3.4 M4 build

 

Next Team Meetings:

*   Bug Triage meeting Thursday Oct. 7th at 7:30am PDT (

https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*   Monthly Project Meeting Tuesday Oct. 5th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Weekly Engineering Sync Tuesday Oct. 12th at 8am PDT (

https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09
 )
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   The final 3.4 build is now due.
*   We should be in a reasonable position and ready for the 3.4 build,
except for the SOURCE_DATE_EPOCH corruption issues we're seeing. Once those
issues and the related sstate reuse issues are fixed, we'll build 3.4. At
this point there are other patches but they're causing failures and clearly
aren't ready for merging.
*   There continues to be an sstate reuse issue where native sstate on
aarch64 and x86_64 hosts isn't generating correct hashes when combined with
hash equivalence.
*   Intermittent issues took a significant rise last week as SWAT caught
up with the backlog of issues. Help is very much welcome on these issues.
You can see the list of failures we're continuing to see by searching for
the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

 

Ways to contribute:

*   There are bugs identified as possible for newcomers to the project:

https://wiki.yoctoproject.org/wiki/Newcomers
*   There are bugs that are currently unassigned for YP 3.4. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.4_Unassigned_Enhan
cements.2FBugs
*   We'd welcome new maintainers for recipes in OE-Core. Please see the
list at:

http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/main
tainers.inc and discuss with the existing maintainer, or ask on the OE-Core
mailing list. We will likely move a chunk of these to "Unassigned" soon to
help facilitate this.

 

YP 3.4 Milestone Dates:

*   YP 3.4 M4 build date 2021/10/04
*   YP 3.4 M4 Release date 2021/10/29

 

Tracking Metrics:

*   WDD 2671 (last week 2676) (

https://wiki.yoctoproject.org/charts/combo.html)
*   OE-Core/Poky Patch Metrics

*   Total patches found: 1318 (last week 1309)
*   Patches in the Pending State: 488 (37%) [last week 484 (37%)]

 

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

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

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

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

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156649): 
https://lists.openembedded.org/g/openembedded-core/message/156649
Mute This Topic: https://lists.openembedded.org/mt/86096065/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][dunfell][PATCH] ffmpeg: Add fix for CVEs

2021-10-05 Thread Saloni Jain
From: Saloni 

Add fix for below CVE:
CVE-2021-3566
Link: 
[http://git.videolan.org/?p=ffmpeg.git;a=patch;h=3bce9e9b3ea35c54ba793d7da99ea5157532]

CVE-2021-38291
Link: 
[http://git.videolan.org/?p=ffmpeg.git;a=patch;h=e01d306c647b5827102260b885faa223b646d2d1]

Signed-off-by: Saloni Jain 
---
 .../ffmpeg/ffmpeg/CVE-2021-3566.patch | 61 +++
 .../ffmpeg/ffmpeg/CVE-2021-38291.patch| 53 
 .../recipes-multimedia/ffmpeg/ffmpeg_4.2.2.bb |  4 +-
 3 files changed, 117 insertions(+), 1 deletion(-)
 create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-3566.patch
 create mode 100644 meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-38291.patch

diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-3566.patch 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-3566.patch
new file mode 100644
index 00..abfc024820
--- /dev/null
+++ b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-3566.patch
@@ -0,0 +1,61 @@
+From 3bce9e9b3ea35c54ba793d7da99ea5157532 Mon Sep 17 00:00:00 2001
+From: Paul B Mahol 
+Date: Mon, 27 Jan 2020 21:53:08 +0100
+Subject: [PATCH] avformat/tty: add probe function
+
+CVE: CVE-2021-3566
+Signed-off-by: Saloni Jain 
+
+Upstream-Status: Backport 
[http://git.videolan.org/?p=ffmpeg.git;a=patch;h=3bce9e9b3ea35c54ba793d7da99ea5157532]
+Comment: No changes/refreshing done.
+---
+ libavformat/tty.c | 21 -
+ 1 file changed, 20 insertions(+), 1 deletion(-)
+
+diff --git a/libavformat/tty.c b/libavformat/tty.c
+index 8d48f2c45c12..60f7e9f87ee7 100644
+--- a/libavformat/tty.c
 b/libavformat/tty.c
+@@ -34,6 +34,13 @@
+ #include "internal.h"
+ #include "sauce.h"
+ 
++static int isansicode(int x)
++{
++return x == 0x1B || x == 0x0A || x == 0x0D || (x >= 0x20 && x < 0x7f);
++}
++
++static const char tty_extensions[31] = "ans,art,asc,diz,ice,nfo,txt,vt";
++
+ typedef struct TtyDemuxContext {
+ AVClass *class;
+ int chars_per_frame;
+@@ -42,6 +49,17 @@ typedef struct TtyDemuxContext {
+ AVRational framerate; /**< Set by a private option. */
+ } TtyDemuxContext;
+ 
++static int read_probe(const AVProbeData *p)
++{
++int cnt = 0;
++
++for (int i = 0; i < p->buf_size; i++)
++cnt += !!isansicode(p->buf[i]);
++
++return (cnt * 100LL / p->buf_size) * (cnt > 400) *
++!!av_match_ext(p->filename, tty_extensions);
++}
++
+ /**
+  * Parse EFI header
+  */
+@@ -153,8 +171,9 @@ AVInputFormat ff_tty_demuxer = {
+ .name   = "tty",
+ .long_name  = NULL_IF_CONFIG_SMALL("Tele-typewriter"),
+ .priv_data_size = sizeof(TtyDemuxContext),
++.read_probe = read_probe,
+ .read_header= read_header,
+ .read_packet= read_packet,
+-.extensions = "ans,art,asc,diz,ice,nfo,txt,vt",
++.extensions = tty_extensions,
+ .priv_class = _demuxer_class,
+ };
diff --git a/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-38291.patch 
b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-38291.patch
new file mode 100644
index 00..e5be985fc3
--- /dev/null
+++ b/meta/recipes-multimedia/ffmpeg/ffmpeg/CVE-2021-38291.patch
@@ -0,0 +1,53 @@
+From e01d306c647b5827102260b885faa223b646d2d1 Mon Sep 17 00:00:00 2001
+From: James Almer 
+Date: Wed, 21 Jul 2021 01:02:44 -0300
+Subject: [PATCH] avcodec/utils: don't return negative values in
+ av_get_audio_frame_duration()
+
+In some extrme cases, like with adpcm_ms samples with an extremely high channel
+count, get_audio_frame_duration() may return a negative frame duration value.
+Don't propagate it, and instead return 0, signaling that a duration could not
+be determined.
+
+CVE: CVE-2021-3566
+Fixes ticket #9312
+Signed-off-by: James Almer 
+Signed-off-by: Saloni Jain 
+
+Upstream-Status: Backport 
[http://git.videolan.org/?p=ffmpeg.git;a=patch;h=e01d306c647b5827102260b885faa223b646d2d1]
+Comment: No changes/refreshing done.
+---
+ libavcodec/utils.c | 6 --
+ 1 file changed, 4 insertions(+), 2 deletions(-)
+
+diff --git a/libavcodec/utils.c b/libavcodec/utils.c
+index 5fad782f5a..cfc07cbcb8 100644
+--- a/libavcodec/utils.c
 b/libavcodec/utils.c
+@@ -810,20 +810,22 @@ static int get_audio_frame_duration(enum AVCodecID id, 
int sr, int ch, int ba,
+ 
+ int av_get_audio_frame_duration(AVCodecContext *avctx, int frame_bytes)
+ {
+-return get_audio_frame_duration(avctx->codec_id, avctx->sample_rate,
++int duration = get_audio_frame_duration(avctx->codec_id, 
avctx->sample_rate,
+ avctx->channels, avctx->block_align,
+ avctx->codec_tag, 
avctx->bits_per_coded_sample,
+ avctx->bit_rate, avctx->extradata, 
avctx->frame_size,
+ frame_bytes);
++return FFMAX(0, duration);
+ }
+ 
+ int av_get_audio_frame_duration2(AVCodecParameters *par, int frame_bytes)
+ {
+-return get_audio_frame_duration(par->codec_id, par->sample_rate,
++int duration = 

Re: [OE-core] Improve npm support to run build scripts

2021-10-05 Thread Alexander Kanavin
'devtool add' of course. Test case is in
meta/lib/oeqa/selftest/cases/devtool.py

Alex

On Tue, 5 Oct 2021 at 15:10, Alexander Kanavin via lists.openembedded.org
 wrote:

> I think the supposed workflow with the new npm.class was to use 'devtool
> create' which would run some npm magic to to create a single recipe that
> has all of the npm-fetched dependencies inside SRC_URI. Have you tried that?
>
> A layer with thousands of recipes seems totally intractable.
>
> Alex
>
> On Tue, 5 Oct 2021 at 14:48, Stefan Herbrechtsmeier <
> stefan.herbrechtsmeier-...@weidmueller.com> wrote:
>
>> Hi Richard,
>>
>> Am 05.10.2021 um 13:09 schrieb Richard Purdie:
>> > Thanks for bring this up, I've been wondering on the status of our npm
>> support.
>>
>> Do you know any npm users?
>>
>> > On Tue, 2021-10-05 at 12:04 +0200, Stefan Herbrechtsmeier wrote:
>> >> I must improve the npm support for our use cases but need some
>> >> fundamental decisions to proceed. I need to build express and angular
>> >> applications from git repositories.
>> >>
>> >> I have the following changes in my pipeline until now:
>> >> - Support npm packages with missing execute mode for directories
>> >> - Reduce command calls in npm run
>> >> - Add support for local tarball and local link sources
>> >> - Rework crunch license to recognize more variants
>> >> - Move known license checksums to CSV file
>> >> - Pass README as fallback to guess license if a license is missing
>> >> - Add support to pass build arguments to npm install
>> >> - Add support to run build scripts with native packages
>> >> - Parallelize the populate of the npm cache
>> >>
>> >> The build (install) of npm packages leads to problems because of old
>> >> versions in the dependency tree. For example, older versions of
>> packages
>> >> are incompatible with the Node.js version and older versions of
>> node-gyp
>> >> require Python 2.
>> >
>> > Hopefully over time the python2 issue should reduce and fade at least.
>> The
>> > node.js version is trickier.
>>
>> The current implementation works like an project with embedded external
>> dependencies. I both cases I have to patch the embedded dependencies or
>> replace them with external DEPENDS.
>>
>> >> I see three solutions to integrate npm packages:
>> >> - Build npm packages from the npm project outside of OE and only fetch
>> >> the data.
>> >> - Fork the npm project repository and fix everything inside the fork.
>> >> Use the fork direct or create patches from the fork to build inside OE.
>> >> - Create recipes per project and incompatible version to fix everything
>> >> in OE and reduce redundancy.
>> >>
>> >> The last solution keeps everything in OE and benefit from the existing
>> >> OE functions like download proxy as well as license, CVE and version
>> >> check. But it increases the initial costs and makes only sense if there
>> >> is an interest in an meta-nodejs layer.
>> >
>> > The latter solution sounds like the only really viable option from an OE
>> > perspective since we do need the proxy/CVE/license handling, it is a
>> huge part
>> > of our value and without it, it isn't really OE.
>>
>> The problem are the many different packages. An Angular project could
>> have more than 1000 different project. Thereby some dependencies only
>> differ in the version or needed only for development like a development
>> server or a unit test framework.
>>
>> > Creating a meta-nodejs layer isn't an issue if there are people willing
>> to look
>> > after it.
>>
>> Is a layer with more more than 1000 recipes thinkable?
>>
>> Regards
>>Stefan
>>
>>
>>
>>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156647): 
https://lists.openembedded.org/g/openembedded-core/message/156647
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] Improve npm support to run build scripts

2021-10-05 Thread Alexander Kanavin
I think the supposed workflow with the new npm.class was to use 'devtool
create' which would run some npm magic to to create a single recipe that
has all of the npm-fetched dependencies inside SRC_URI. Have you tried that?

A layer with thousands of recipes seems totally intractable.

Alex

On Tue, 5 Oct 2021 at 14:48, Stefan Herbrechtsmeier <
stefan.herbrechtsmeier-...@weidmueller.com> wrote:

> Hi Richard,
>
> Am 05.10.2021 um 13:09 schrieb Richard Purdie:
> > Thanks for bring this up, I've been wondering on the status of our npm
> support.
>
> Do you know any npm users?
>
> > On Tue, 2021-10-05 at 12:04 +0200, Stefan Herbrechtsmeier wrote:
> >> I must improve the npm support for our use cases but need some
> >> fundamental decisions to proceed. I need to build express and angular
> >> applications from git repositories.
> >>
> >> I have the following changes in my pipeline until now:
> >> - Support npm packages with missing execute mode for directories
> >> - Reduce command calls in npm run
> >> - Add support for local tarball and local link sources
> >> - Rework crunch license to recognize more variants
> >> - Move known license checksums to CSV file
> >> - Pass README as fallback to guess license if a license is missing
> >> - Add support to pass build arguments to npm install
> >> - Add support to run build scripts with native packages
> >> - Parallelize the populate of the npm cache
> >>
> >> The build (install) of npm packages leads to problems because of old
> >> versions in the dependency tree. For example, older versions of packages
> >> are incompatible with the Node.js version and older versions of node-gyp
> >> require Python 2.
> >
> > Hopefully over time the python2 issue should reduce and fade at least.
> The
> > node.js version is trickier.
>
> The current implementation works like an project with embedded external
> dependencies. I both cases I have to patch the embedded dependencies or
> replace them with external DEPENDS.
>
> >> I see three solutions to integrate npm packages:
> >> - Build npm packages from the npm project outside of OE and only fetch
> >> the data.
> >> - Fork the npm project repository and fix everything inside the fork.
> >> Use the fork direct or create patches from the fork to build inside OE.
> >> - Create recipes per project and incompatible version to fix everything
> >> in OE and reduce redundancy.
> >>
> >> The last solution keeps everything in OE and benefit from the existing
> >> OE functions like download proxy as well as license, CVE and version
> >> check. But it increases the initial costs and makes only sense if there
> >> is an interest in an meta-nodejs layer.
> >
> > The latter solution sounds like the only really viable option from an OE
> > perspective since we do need the proxy/CVE/license handling, it is a
> huge part
> > of our value and without it, it isn't really OE.
>
> The problem are the many different packages. An Angular project could
> have more than 1000 different project. Thereby some dependencies only
> differ in the version or needed only for development like a development
> server or a unit test framework.
>
> > Creating a meta-nodejs layer isn't an issue if there are people willing
> to look
> > after it.
>
> Is a layer with more more than 1000 recipes thinkable?
>
> Regards
>Stefan
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156646): 
https://lists.openembedded.org/g/openembedded-core/message/156646
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] linux-yocto: add libmpc-native to DEPENDS

2021-10-05 Thread Ross Burton
5.14 changed how the GCC plugins are built, which means they now
depend on both GMP and MPC to be built. We already depend on gmp-native,
so add libmpc-native aswell.

Signed-off-by: Ross Burton 
---
 meta/recipes-kernel/linux/linux-yocto_5.14.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meta/recipes-kernel/linux/linux-yocto_5.14.bb 
b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
index 0c6fbff75e..8c44c294bd 100644
--- a/meta/recipes-kernel/linux/linux-yocto_5.14.bb
+++ b/meta/recipes-kernel/linux/linux-yocto_5.14.bb
@@ -46,7 +46,7 @@ LINUX_VERSION ?= "5.14.6"
 
 DEPENDS += "${@bb.utils.contains('ARCH', 'x86', 'elfutils-native', '', d)}"
 DEPENDS += "openssl-native util-linux-native"
-DEPENDS += "gmp-native"
+DEPENDS += "gmp-native libmpc-native"
 
 PV = "${LINUX_VERSION}+git${SRCPV}"
 
-- 
2.25.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156645): 
https://lists.openembedded.org/g/openembedded-core/message/156645
Mute This Topic: https://lists.openembedded.org/mt/86092630/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] Improve npm support to run build scripts

2021-10-05 Thread Stefan Herbrechtsmeier

Hi Richard,

Am 05.10.2021 um 13:09 schrieb Richard Purdie:

Thanks for bring this up, I've been wondering on the status of our npm support.


Do you know any npm users?


On Tue, 2021-10-05 at 12:04 +0200, Stefan Herbrechtsmeier wrote:

I must improve the npm support for our use cases but need some
fundamental decisions to proceed. I need to build express and angular
applications from git repositories.

I have the following changes in my pipeline until now:
- Support npm packages with missing execute mode for directories
- Reduce command calls in npm run
- Add support for local tarball and local link sources
- Rework crunch license to recognize more variants
- Move known license checksums to CSV file
- Pass README as fallback to guess license if a license is missing
- Add support to pass build arguments to npm install
- Add support to run build scripts with native packages
- Parallelize the populate of the npm cache

The build (install) of npm packages leads to problems because of old
versions in the dependency tree. For example, older versions of packages
are incompatible with the Node.js version and older versions of node-gyp
require Python 2.


Hopefully over time the python2 issue should reduce and fade at least. The
node.js version is trickier.


The current implementation works like an project with embedded external 
dependencies. I both cases I have to patch the embedded dependencies or 
replace them with external DEPENDS.



I see three solutions to integrate npm packages:
- Build npm packages from the npm project outside of OE and only fetch
the data.
- Fork the npm project repository and fix everything inside the fork.
Use the fork direct or create patches from the fork to build inside OE.
- Create recipes per project and incompatible version to fix everything
in OE and reduce redundancy.

The last solution keeps everything in OE and benefit from the existing
OE functions like download proxy as well as license, CVE and version
check. But it increases the initial costs and makes only sense if there
is an interest in an meta-nodejs layer.


The latter solution sounds like the only really viable option from an OE
perspective since we do need the proxy/CVE/license handling, it is a huge part
of our value and without it, it isn't really OE.


The problem are the many different packages. An Angular project could 
have more than 1000 different project. Thereby some dependencies only 
differ in the version or needed only for development like a development 
server or a unit test framework.



Creating a meta-nodejs layer isn't an issue if there are people willing to look
after it.


Is a layer with more more than 1000 recipes thinkable?

Regards
  Stefan

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156644): 
https://lists.openembedded.org/g/openembedded-core/message/156644
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] Improve npm support to run build scripts

2021-10-05 Thread Richard Purdie
Hi Stefan,

Thanks for bring this up, I've been wondering on the status of our npm support.

On Tue, 2021-10-05 at 12:04 +0200, Stefan Herbrechtsmeier wrote:
> I must improve the npm support for our use cases but need some 
> fundamental decisions to proceed. I need to build express and angular 
> applications from git repositories.
> 
> I have the following changes in my pipeline until now:
> - Support npm packages with missing execute mode for directories
> - Reduce command calls in npm run
> - Add support for local tarball and local link sources
> - Rework crunch license to recognize more variants
> - Move known license checksums to CSV file
> - Pass README as fallback to guess license if a license is missing
> - Add support to pass build arguments to npm install
> - Add support to run build scripts with native packages
> - Parallelize the populate of the npm cache
> 
> The build (install) of npm packages leads to problems because of old 
> versions in the dependency tree. For example, older versions of packages 
> are incompatible with the Node.js version and older versions of node-gyp 
> require Python 2.

Hopefully over time the python2 issue should reduce and fade at least. The
node.js version is trickier.

> 
> I see three solutions to integrate npm packages:
> - Build npm packages from the npm project outside of OE and only fetch 
> the data.
> - Fork the npm project repository and fix everything inside the fork. 
> Use the fork direct or create patches from the fork to build inside OE.
> - Create recipes per project and incompatible version to fix everything 
> in OE and reduce redundancy.
> 
> The last solution keeps everything in OE and benefit from the existing 
> OE functions like download proxy as well as license, CVE and version 
> check. But it increases the initial costs and makes only sense if there 
> is an interest in an meta-nodejs layer.

The latter solution sounds like the only really viable option from an OE
perspective since we do need the proxy/CVE/license handling, it is a huge part
of our value and without it, it isn't really OE.

Creating a meta-nodejs layer isn't an issue if there are people willing to look
after it.

Cheers,

Richard


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156643): 
https://lists.openembedded.org/g/openembedded-core/message/156643
Mute This Topic: https://lists.openembedded.org/mt/86089523/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/2] kernel, kernel-module-split: Add runtime dependency to subpackages on main package

2021-10-05 Thread Zoltan Boszormenyi via lists.openembedded.org

On 2021. 10. 05. 12:18, Alexandre Belloni wrote:

Hello,

On 30/09/2021 16:14:43+0200, Zoltan Boszormenyi via lists.openembedded.org 
wrote:

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

This creates a circular dependency between the main kernel package
and its subpackages. It helps package managers to automatically
remove all kernel packages of the same version when upgrading.

Signed-off-by: Zoltán Böszörményi 
---
v2: No changes

v3: Add reverse RDEPENDS to subpackages unconditionally
 Handle KERNEL_SPLIT_MODULES=1 (default) case in
 meta/classes/kernel-module-split.bbclass

  meta/classes/kernel-module-split.bbclass | 5 +++--
  meta/classes/kernel.bbclass  | 7 ++-
  2 files changed, 9 insertions(+), 3 deletions(-)

diff --git a/meta/classes/kernel-module-split.bbclass 
b/meta/classes/kernel-module-split.bbclass
index a29c294810..2ddcea538c 100644
--- a/meta/classes/kernel-module-split.bbclass
+++ b/meta/classes/kernel-module-split.bbclass
@@ -176,8 +176,9 @@ python split_kernel_module_packages () {
  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))

-if modules:
-d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
+for mod in modules:
+d.appendVar('RDEPENDS:' + metapkg, ' %s (= ${EXTENDPKGV})' % mod)
+d.appendVar('RDEPENDS:' + mod, ' %s (= ${EXTENDPKGV})' % 
kernel_package_name)
  


I believe this causes the following issues:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/4135/steps/18/logs/stdio

Error:
  Problem: package hello-mod-0.1-r0.qemux86_64 requires 
kernel-module-hello-5.14.6-yocto-standard = 0.1-r0, but none of the providers 
can be installed

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2342/steps/11/logs/stdio

Error:
  Problem: package lttng-tools-ptest-2.13.0-r0.cortexa57 requires 
lttng-modules, but none of the providers can be installed
   - package lttng-modules-2.13.0-r0.qemuarm64 requires 
kernel-module-lttng-wrapper-5.14.6-yocto-standard = 2.13.0-r0, but none of the 
providers can be installed
   - conflicting requests
   - nothing provides kernel = 2.13.0-r0 needed by 
kernel-module-lttng-wrapper-5.14.6-yocto-standard-2.13.0-r0.qemuarm64
(try to add '--skip-broken' to skip uninstallable packages)


Arrggh. Externally built modules?

That exact ${EXTENDPKGV} match was intended only for
the kernel and its own modules.

An extra opt-out knob should be devised to be used
by such individual module recipes because their
full version may not match the kernel's.





  # If modules-load.d and modprobe.d are empty at this point, remove them to
  # avoid warnings. removedirs only raises an OSError if an empty
diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
index 4acec1877e..afd9f8045e 100644
--- a/meta/classes/kernel.bbclass
+++ b/meta/classes/kernel.bbclass
@@ -98,7 +98,9 @@ python __anonymous () {
  typelower = type.lower()
  d.appendVar('PACKAGES', ' %s-image-%s' % (kname, typelower))
  d.setVar('FILES:' + kname + '-image-' + typelower, '/' + imagedest + 
'/' + type + '-${KERNEL_VERSION_NAME}' + ' /' + imagedest + '/' + type)
+d.appendVar('RDEPENDS:%s-image' % kname, ' %s (= ${EXTENDPKGV})' % 
kname)
  d.appendVar('RDEPENDS:%s-image' % kname, ' %s-image-%s (= 
${EXTENDPKGV})' % (kname, typelower))
+d.appendVar('RDEPENDS:%s-image-%s' % (kname, typelower), ' %s (= 
${EXTENDPKGV})' % kname)
  splitmods = d.getVar("KERNEL_SPLIT_MODULES")
  if splitmods != '1':
  d.appendVar('RDEPENDS:%s-image' % kname, ' %s-modules (= 
${EXTENDPKGV})' % kname)
@@ -627,8 +629,11 @@ RDEPENDS:${KERNEL_PACKAGE_NAME} = 
"${KERNEL_PACKAGE_NAME}-base (= ${EXTENDPKGV})
  # 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})"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-base:append = " ${KERNEL_PACKAGE_NAME} (= 
${EXTENDPKGV})"
  PKG:${KERNEL_PACKAGE_NAME}-image = 
"${KERNEL_PACKAGE_NAME}-image-${@legitimize_package_name(d.getVar('KERNEL_VERSION'))}"
-RDEPENDS:${KERNEL_PACKAGE_NAME}-image += 
"${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', 
'${KERNEL_PACKAGE_NAME}-vmlinux (= ${EXTENDPKGV})', '', d)}"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-image:append = 
"${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', ' 
${KERNEL_PACKAGE_NAME}-vmlinux (= ${EXTENDPKGV})', '', d)}"
+RDEPENDS:${KERNEL_PACKAGE_NAME}-vmlinux:append = 
"${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', ' ${KERNEL_PACKAGE_NAME} (= 
${EXTENDPKGV})', '', d)}"

Re: [OE-core] [PATCH v3 1/2] kernel, kernel-module-split: Add runtime dependency to subpackages on main package

2021-10-05 Thread Alexandre Belloni
Hello,

On 30/09/2021 16:14:43+0200, Zoltan Boszormenyi via lists.openembedded.org 
wrote:
> From: Zoltán Böszörményi 
> 
> This creates a circular dependency between the main kernel package
> and its subpackages. It helps package managers to automatically
> remove all kernel packages of the same version when upgrading.
> 
> Signed-off-by: Zoltán Böszörményi 
> ---
> v2: No changes
> 
> v3: Add reverse RDEPENDS to subpackages unconditionally
> Handle KERNEL_SPLIT_MODULES=1 (default) case in
> meta/classes/kernel-module-split.bbclass
> 
>  meta/classes/kernel-module-split.bbclass | 5 +++--
>  meta/classes/kernel.bbclass  | 7 ++-
>  2 files changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/meta/classes/kernel-module-split.bbclass 
> b/meta/classes/kernel-module-split.bbclass
> index a29c294810..2ddcea538c 100644
> --- a/meta/classes/kernel-module-split.bbclass
> +++ b/meta/classes/kernel-module-split.bbclass
> @@ -176,8 +176,9 @@ python split_kernel_module_packages () {
>  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))
> -if modules:
> -d.appendVar('RDEPENDS:' + metapkg, ' '+' '.join(modules))
> +for mod in modules:
> +d.appendVar('RDEPENDS:' + metapkg, ' %s (= ${EXTENDPKGV})' % mod)
> +d.appendVar('RDEPENDS:' + mod, ' %s (= ${EXTENDPKGV})' % 
> kernel_package_name)
>  

I believe this causes the following issues:

https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/4135/steps/18/logs/stdio

Error: 
 Problem: package hello-mod-0.1-r0.qemux86_64 requires 
kernel-module-hello-5.14.6-yocto-standard = 0.1-r0, but none of the providers 
can be installed

https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/2342/steps/11/logs/stdio

Error: 
 Problem: package lttng-tools-ptest-2.13.0-r0.cortexa57 requires lttng-modules, 
but none of the providers can be installed
  - package lttng-modules-2.13.0-r0.qemuarm64 requires 
kernel-module-lttng-wrapper-5.14.6-yocto-standard = 2.13.0-r0, but none of the 
providers can be installed
  - conflicting requests
  - nothing provides kernel = 2.13.0-r0 needed by 
kernel-module-lttng-wrapper-5.14.6-yocto-standard-2.13.0-r0.qemuarm64
(try to add '--skip-broken' to skip uninstallable packages)


>  # If modules-load.d and modprobe.d are empty at this point, remove them 
> to
>  # avoid warnings. removedirs only raises an OSError if an empty
> diff --git a/meta/classes/kernel.bbclass b/meta/classes/kernel.bbclass
> index 4acec1877e..afd9f8045e 100644
> --- a/meta/classes/kernel.bbclass
> +++ b/meta/classes/kernel.bbclass
> @@ -98,7 +98,9 @@ python __anonymous () {
>  typelower = type.lower()
>  d.appendVar('PACKAGES', ' %s-image-%s' % (kname, typelower))
>  d.setVar('FILES:' + kname + '-image-' + typelower, '/' + imagedest + 
> '/' + type + '-${KERNEL_VERSION_NAME}' + ' /' + imagedest + '/' + type)
> +d.appendVar('RDEPENDS:%s-image' % kname, ' %s (= ${EXTENDPKGV})' % 
> kname)
>  d.appendVar('RDEPENDS:%s-image' % kname, ' %s-image-%s (= 
> ${EXTENDPKGV})' % (kname, typelower))
> +d.appendVar('RDEPENDS:%s-image-%s' % (kname, typelower), ' %s (= 
> ${EXTENDPKGV})' % kname)
>  splitmods = d.getVar("KERNEL_SPLIT_MODULES")
>  if splitmods != '1':
>  d.appendVar('RDEPENDS:%s-image' % kname, ' %s-modules (= 
> ${EXTENDPKGV})' % kname)
> @@ -627,8 +629,11 @@ RDEPENDS:${KERNEL_PACKAGE_NAME} = 
> "${KERNEL_PACKAGE_NAME}-base (= ${EXTENDPKGV})
>  # 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})"
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-base:append = " ${KERNEL_PACKAGE_NAME} (= 
> ${EXTENDPKGV})"
>  PKG:${KERNEL_PACKAGE_NAME}-image = 
> "${KERNEL_PACKAGE_NAME}-image-${@legitimize_package_name(d.getVar('KERNEL_VERSION'))}"
> -RDEPENDS:${KERNEL_PACKAGE_NAME}-image += 
> "${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', 
> '${KERNEL_PACKAGE_NAME}-vmlinux (= ${EXTENDPKGV})', '', d)}"
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-image:append = 
> "${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', ' 
> ${KERNEL_PACKAGE_NAME}-vmlinux (= ${EXTENDPKGV})', '', d)}"
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-vmlinux:append = 
> "${@oe.utils.conditional('KERNEL_IMAGETYPE', 'vmlinux', ' 
> ${KERNEL_PACKAGE_NAME} (= ${EXTENDPKGV})', '', d)}"
> +RDEPENDS:${KERNEL_PACKAGE_NAME}-modules:append = " ${KERNEL_PACKAGE_NAME} (= 
> ${EXTENDPKGV})"
>  PKG:${KERNEL_PACKAGE_NAME}-base = 
> 

[OE-core] Improve npm support to run build scripts

2021-10-05 Thread Stefan Herbrechtsmeier

Hi Jean-Marie and Richard,

I must improve the npm support for our use cases but need some 
fundamental decisions to proceed. I need to build express and angular 
applications from git repositories.


I have the following changes in my pipeline until now:
- Support npm packages with missing execute mode for directories
- Reduce command calls in npm run
- Add support for local tarball and local link sources
- Rework crunch license to recognize more variants
- Move known license checksums to CSV file
- Pass README as fallback to guess license if a license is missing
- Add support to pass build arguments to npm install
- Add support to run build scripts with native packages
- Parallelize the populate of the npm cache

The build (install) of npm packages leads to problems because of old 
versions in the dependency tree. For example, older versions of packages 
are incompatible with the Node.js version and older versions of node-gyp 
require Python 2.


I see three solutions to integrate npm packages:
- Build npm packages from the npm project outside of OE and only fetch 
the data.
- Fork the npm project repository and fix everything inside the fork. 
Use the fork direct or create patches from the fork to build inside OE.
- Create recipes per project and incompatible version to fix everything 
in OE and reduce redundancy.


The last solution keeps everything in OE and benefit from the existing 
OE functions like download proxy as well as license, CVE and version 
check. But it increases the initial costs and makes only sense if there 
is an interest in an meta-nodejs layer.


Regards
  Stefan


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156640): 
https://lists.openembedded.org/g/openembedded-core/message/156640
Mute This Topic: https://lists.openembedded.org/mt/86089523/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] libevent,btrfs-tools: fix Upstream-Status tag

2021-10-05 Thread Alexander Kanavin
The first two should say Backport and Inappropriate [oe-core specific
...explanation]

Definitions here:
https://www.openembedded.org/wiki/Commit_Patch_Message_Guidelines#Patch_Header_Recommendations:_Upstream-Status

Alex

On Tue, 5 Oct 2021 at 10:41, Alexandre Belloni <
alexandre.bell...@bootlin.com> wrote:

> Signed-off-by: Alexandre Belloni 
> ---
>  ...1-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch | 2 +-
>  ...003-test-mark-util-monotonic_prc_fallback-as-retriable.patch | 2 +-
>  ...test-retriable-tests-are-marked-failed-only-when-all-a.patch | 2 +-
>  3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git
> a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
> index d711da8d..f57089e963fe 100644
> ---
> a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
> +++
> b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
> @@ -18,7 +18,7 @@ add an explicit include of const.h to pickup the macro:
>  This is safe for older kernel's as well, since the header still
>  exists, and is valid to include.
>
> -Upstream-status: OE Specific [mips64 + musl + libc-headers]
> +Upstream-Status: OE Specific [mips64 + musl + libc-headers]
>
>  Signed-off-by: Bruce Ashfield 
>  ---
> diff --git
> a/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
> b/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
> index 8a2c78983e1d..519bccf8d794 100644
> ---
> a/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
> +++
> b/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
> @@ -5,7 +5,7 @@ Subject: [PATCH] test: mark util/monotonic_prc_fallback as
> retriable
>
>  Refs: #1193
>
> -Upstream-status: Backported
> +Upstream-Status: Backported
>  ---
>   test/regress_util.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git
> a/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
> b/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
> index ae7db0b7aa85..e453c80d7fcd 100644
> ---
> a/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
> +++
> b/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
> @@ -6,7 +6,7 @@ Subject: [PATCH] test: retriable tests are marked failed
> only when all
>
>  Fixes: #1193
>
> -Upstream-status: Pending
> +Upstream-Status: Pending
>
>  Signed-off-by: Thomas Perrot 
>  ---
> --
> 2.31.1
>
>
> 
>
>

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156639): 
https://lists.openembedded.org/g/openembedded-core/message/156639
Mute This Topic: https://lists.openembedded.org/mt/86088669/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] libevent,btrfs-tools: fix Upstream-Status tag

2021-10-05 Thread Alexandre Belloni
Signed-off-by: Alexandre Belloni 
---
 ...1-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch | 2 +-
 ...003-test-mark-util-monotonic_prc_fallback-as-retriable.patch | 2 +-
 ...test-retriable-tests-are-marked-failed-only-when-all-a.patch | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git 
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
index d711da8d..f57089e963fe 100644
--- 
a/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
+++ 
b/meta/recipes-devtools/btrfs-tools/btrfs-tools/0001-btrfs-tools-include-linux-const.h-to-fix-build-with-.patch
@@ -18,7 +18,7 @@ add an explicit include of const.h to pickup the macro:
 This is safe for older kernel's as well, since the header still
 exists, and is valid to include.
 
-Upstream-status: OE Specific [mips64 + musl + libc-headers]
+Upstream-Status: OE Specific [mips64 + musl + libc-headers]
 
 Signed-off-by: Bruce Ashfield 
 ---
diff --git 
a/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
 
b/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
index 8a2c78983e1d..519bccf8d794 100644
--- 
a/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
+++ 
b/meta/recipes-support/libevent/libevent/0003-test-mark-util-monotonic_prc_fallback-as-retriable.patch
@@ -5,7 +5,7 @@ Subject: [PATCH] test: mark util/monotonic_prc_fallback as 
retriable
 
 Refs: #1193
 
-Upstream-status: Backported
+Upstream-Status: Backported
 ---
  test/regress_util.c | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
diff --git 
a/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
 
b/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
index ae7db0b7aa85..e453c80d7fcd 100644
--- 
a/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
+++ 
b/meta/recipes-support/libevent/libevent/0004-test-retriable-tests-are-marked-failed-only-when-all-a.patch
@@ -6,7 +6,7 @@ Subject: [PATCH] test: retriable tests are marked failed only 
when all
 
 Fixes: #1193
 
-Upstream-status: Pending
+Upstream-Status: Pending
 
 Signed-off-by: Thomas Perrot 
 ---
-- 
2.31.1


-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156638): 
https://lists.openembedded.org/g/openembedded-core/message/156638
Mute This Topic: https://lists.openembedded.org/mt/86088669/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] devpyshell: rename to pydevshell

2021-10-05 Thread Michael Opdenacker
For consistency with "pydevshell" which is also used.
This addresses [YOCTO #14531]

Signed-off-by: Michael Opdenacker 
---
 meta/classes/devshell.bbclass| 10 +-
 meta/conf/documentation.conf |  2 +-
 scripts/oepydevshell-internal.py |  2 +-
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/meta/classes/devshell.bbclass b/meta/classes/devshell.bbclass
index 76dd0b42ee..62dc958d9a 100644
--- a/meta/classes/devshell.bbclass
+++ b/meta/classes/devshell.bbclass
@@ -34,7 +34,7 @@ python () {
d.delVarFlag("do_devshell", "fakeroot")
 } 
 
-def devpyshell(d):
+def pydevshell(d):
 
 import code
 import select
@@ -140,17 +140,17 @@ def devpyshell(d):
 os.kill(child, signal.SIGTERM)
 break
 
-python do_devpyshell() {
+python do_pydevshell() {
 import signal
 
 try:
-devpyshell(d)
+pydevshell(d)
 except SystemExit:
 # Stop the SIGTERM above causing an error exit code
 return
 finally:
 return
 }
-addtask devpyshell after do_patch
+addtask pydevshell after do_patch
 
-do_devpyshell[nostamp] = "1"
+do_pydevshell[nostamp] = "1"
diff --git a/meta/conf/documentation.conf b/meta/conf/documentation.conf
index c5a38b0764..80ad8e10d5 100644
--- a/meta/conf/documentation.conf
+++ b/meta/conf/documentation.conf
@@ -17,7 +17,7 @@ do_compile_ptest_base[doc] = "Compiles the runtime test suite 
included in the so
 do_configure[doc] = "Configures the source by enabling and disabling any 
build-time and configuration options for the software being built"
 do_configure_ptest_base[doc] = "Configures the runtime test suite included in 
the software being built"
 do_deploy[doc] = "Writes deployable output files to the deploy directory"
-do_devpyshell[doc] = "Starts an interactive Python shell for 
development/debugging"
+do_pydevshell[doc] = "Starts an interactive Python shell for 
development/debugging"
 do_devshell[doc] = "Starts a shell with the environment set up for 
development/debugging"
 do_diffconfig[doc] = "Compares the old and new config files after running 
do_menuconfig for the kernel"
 do_fetch[doc] = "Fetches the source code"
diff --git a/scripts/oepydevshell-internal.py b/scripts/oepydevshell-internal.py
index 96c078ef3d..e3c35bbe2c 100755
--- a/scripts/oepydevshell-internal.py
+++ b/scripts/oepydevshell-internal.py
@@ -43,7 +43,7 @@ nonblockingfd(pty)
 nonblockingfd(sys.stdin)
 
 
-histfile = os.path.expanduser("~/.oedevpyshell-history")
+histfile = os.path.expanduser("~/.oepydevshell-history")
 readline.parse_and_bind("tab: complete")
 try:
 readline.read_history_file(histfile)
-- 
2.25.1


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