Re: [OE-core] Easy way to talk to hashserv or prserv?

On Fri, Mar 1, 2024 at 11:34 AM Michael Opdenacker wrote: > > Hi Joshua and all, > > I'm going to test changes to the prserv server, to implement > "passthrough" to another server. > > I can make tests by checking the impact of my changes on the build > results, like checking the revision of

[OE-core] [AUH] libpcre2: upgrading to 10.43 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libpcre2* to *10.43* has Succeeded. Next steps: - apply the patch: git am 0001-libpcre2-upgrade-10.42-10.43.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] libusb1: upgrading to 1.0.27 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libusb1* to *1.0.27* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-libusb1-upgrade-1.0.26-1.0.27.patch

[OE-core] [AUH] libpciaccess: upgrading to 0.18 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libpciaccess* to *0.18* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] nghttp2: upgrading to 1.60.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *nghttp2* to *1.60.0* has Succeeded. Next steps: - apply the patch: git am 0001-nghttp2-upgrade-1.59.0-1.60.0.patch - check the changes to upstream patches and summarize

[OE-core] [AUH] waffle: upgrading to 1.8.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *waffle* to *1.8.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe waffle failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] diffoscope: upgrading to 259 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *diffoscope* to *259* has Succeeded. Next steps: - apply the patch: git am 0001-diffoscope-upgrade-253-259.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] taglib: upgrading to 2.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *taglib* to *2.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-taglib-upgrade-1.13.1-2.0.patch -

[OE-core] [AUH] kmscube: upgrading to 6ab022fdfcfedd28f4b5dbd8d3299414a367746f SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *kmscube* to *6ab022fdfcfedd28f4b5dbd8d3299414a367746f* has Succeeded. Next steps: - apply the patch: git am 0001-kmscube-upgrade-to-latest-revision.patch - check the

[OE-core] [AUH] npth: upgrading to 1.7 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *npth* to *1.7* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe npth failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] vulkan-utility-libraries: upgrading to 1.3.275.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-utility-libraries* to *1.3.275.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] puzzles: upgrading to e20644a3baa70dfd5baf790047ce821b396df312 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *puzzles* to *e20644a3baa70dfd5baf790047ce821b396df312* has Succeeded. Next steps: - apply the patch: git am 0001-puzzles-upgrade-to-latest-revision.patch - check the

[OE-core] [AUH] libstd-rs: upgrading to 1.76.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libstd-rs* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libstd-rs failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] piglit: upgrading to 22eaf6a91cfd57f7bb3df4e5068c2ac1472d4ec1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *piglit* to *22eaf6a91cfd57f7bb3df4e5068c2ac1472d4ec1* has Succeeded. Next steps: - apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch - check the changes

[OE-core] [AUH] rpm: upgrading to 4.19.1.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rpm* to *4.19.1.1* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rpm failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] shaderc: upgrading to 2023.8 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shaderc* to *2023.8* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe shaderc failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] minicom: upgrading to 2.9 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *minicom* to *2.9* has Succeeded. Next steps: - apply the patch: git am 0001-minicom-upgrade-2.8-2.9.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] shadow: upgrading to 4.15.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *shadow* to *4.15.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade shadow -V 4.15.0 NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] man-pages: upgrading to 6.06 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *man-pages* to *6.06* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-man-pages-upgrade-6.05.01-6.06.patch

[OE-core] [AUH] vulkan-samples: upgrading to 478890b07a043ff9be07592dec358c96ce0c5277 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-samples* to *478890b07a043ff9be07592dec358c96ce0c5277* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade vulkan-samples

[OE-core] [AUH] libdnf: upgrading to 0.73.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libdnf* to *0.73.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade libdnf -V 0.73.0 -S

[OE-core] [AUH] icu: upgrading to 74-2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *icu* to *74-2* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade icu -V 74-2 NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] texinfo: upgrading to 7.1 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *texinfo* to *7.1* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade texinfo -V 7.1 NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] libbsd: upgrading to 0.12.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libbsd* to *0.12.1* has Succeeded. Next steps: - apply the patch: git am 0001-libbsd-upgrade-0.11.8-0.12.1.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] go-helloworld: upgrading to 32022caedd6a177a7717aa8680cbe179e1045935 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-helloworld* to *32022caedd6a177a7717aa8680cbe179e1045935* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade go-helloworld

[OE-core] [AUH] python3-lxml: upgrading to 5.1.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-lxml* to *5.1.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade python3-lxml -V 5.1.0 NOTE: Reconnecting to bitbake

[OE-core] [AUH] libtraceevent: upgrading to 1.8.2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libtraceevent* to *1.8.2* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libtraceevent failed. NOTE: Reconnecting to bitbake

[OE-core] [AUH] libpam: upgrading to 1.6.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *libpam* to *1.6.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe libpam failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] mc: upgrading to 4.8.31 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mc* to *4.8.31* has Succeeded. Next steps: - apply the patch: git am 0001-mc-upgrade-4.8.30-4.8.31.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] vulkan-tools: upgrading to 1.3.275.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.275.0* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] attr: upgrading to 2.5.2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *attr* to *2.5.2* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade attr -V 2.5.2 NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] rust: upgrading to 1.76.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] glslang: upgrading to 1.3.275.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *glslang* to *1.3.275.0* has Succeeded. Next steps: - apply the patch: git am 0001-glslang-upgrade-1.3.268.0-1.3.275.0.patch - check the changes to upstream patches and

[OE-core] [AUH] gtk+3: upgrading to 3.24.41 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.41* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe gtk+3 failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] spirv-headers: upgrading to 1.3.275.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *spirv-headers* to *1.3.275.0* has Succeeded. Next steps: - apply the patch: git am 0001-spirv-headers-upgrade-1.3.268.0-1.3.275.0.patch - check the changes to upstream

[OE-core] [AUH] lsof: upgrading to 4.99.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *lsof* to *4.99.3* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-lsof-upgrade-4.98.0-4.99.3.patch -

[OE-core] [AUH] orc: upgrading to 0.4.38 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *orc* to *0.4.38* has Succeeded. Next steps: - apply the patch: git am 0001-orc-upgrade-0.4.37-0.4.38.patch - check the changes to upstream patches and summarize them in the

[OE-core] [AUH] python3-ruamel-yaml: upgrading to 0.18.6 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-ruamel-yaml* to *0.18.6* has Succeeded. Next steps: - apply the patch: git am 0001-python3-ruamel-yaml-upgrade-0.17.35-0.18.6.patch - check the changes to upstream

[OE-core] [AUH] repo: upgrading to 2.42 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *repo* to *2.42* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-repo-upgrade-2.41-2.42.patch - check

[OE-core] [AUH] python3-build: upgrading to 1.1.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-build* to *1.1.1* has Succeeded. Next steps: - apply the patch: git am 0001-python3-build-upgrade-1.0.3-1.1.1.patch - check the changes to upstream patches and

[OE-core] [AUH] cargo: upgrading to 1.76.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *cargo* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe cargo failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] rust-llvm: upgrading to 1.76.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *rust-llvm* to *1.76.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe rust-llvm failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] meson: upgrading to 1.4.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *meson* to *1.4.0* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade meson -V 1.4.0 NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] mdadm: upgrading to 4.3 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *mdadm* to *4.3* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe mdadm failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] vala: upgrading to 0.56.14 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *vala* to *0.56.14* has Succeeded. Next steps: - apply the patch: git am 0001-vala-upgrade-0.56.13-0.56.14.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] gptfdisk: upgrading to 1.0.10 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gptfdisk* to *1.0.10* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe gptfdisk failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] tcl: upgrading to 8.6.14 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *tcl* to *8.6.14* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe tcl failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] python3-hypothesis: upgrading to 6.98.15 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-hypothesis* to *6.98.15* has Succeeded. Next steps: - apply the patch: git am 0001-python3-hypothesis-upgrade-6.98.12-6.98.15.patch - check the changes to upstream

[OE-core] [AUH] ruby: upgrading to 3.3.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ruby* to *3.3.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe ruby failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] ttyrun: upgrading to 2.31.0 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ttyrun* to *2.31.0* has Succeeded. Next steps: - apply the patch: git am 0001-ttyrun-upgrade-2.30.0-2.31.0.patch - check the changes to upstream patches and summarize them

[OE-core] [AUH] gettext: upgrading to 0.22.5 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *gettext* to *0.22.5* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-gettext-upgrade-0.22.4-0.22.5.patch

[OE-core] [AUH] dpkg: upgrading to 1.22.5 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *dpkg* to *1.22.5* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe dpkg failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] librepo: upgrading to 1.17.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *librepo* to *1.17.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe librepo failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] go: upgrading to 1.22.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go* to *1.22.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go failed. NOTE: Reconnecting to bitbake server... Loading

[OE-core] [AUH] update-rc.d: upgrading to b8f950105010270a768aa12245d6abf166346015 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *update-rc.d* to *b8f950105010270a768aa12245d6abf166346015* has Succeeded. Next steps: - apply the patch: git am 0001-update-rc.d-upgrade-to-latest-revision.patch - check

[OE-core] [AUH] btrfs-tools: upgrading to 6.7.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.7.1* has Succeeded. Next steps: - apply the patch: git am 0001-btrfs-tools-upgrade-6.5.3-6.7.1.patch - check the changes to upstream patches and

[OE-core] [AUH] systemd-boot: upgrading to 255.4 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *systemd-boot* to *255.4* has Succeeded. Next steps: - apply the patch: git am 0001-systemd-boot-upgrade-255.1-255.4.patch - check the changes to upstream patches and

[OE-core] [AUH] ovmf: upgrading to edk2-stable202402 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202402* has Failed (devtool error). Detailed error information: The following devtool command failed: upgrade ovmf -V edk2-stable202402 -S

[OE-core] [AUH] glib-2.0: upgrading to 2.78.4 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *glib-2.0* to *2.78.4* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am 0001-glib-2.0-upgrade-2.78.3-2.78.4.patch

[OE-core] [AUH] glib-networking: upgrading to 2.78.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *glib-networking* to *2.78.1* has Succeeded. Next steps: - apply the patch: git am 0001-glib-networking-upgrade-2.78.0-2.78.1.patch - check the changes to upstream patches

[OE-core] [AUH] python3-dtschema: upgrading to 2024.2 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *python3-dtschema* to *2024.2* has Failed(do_compile). Detailed error information: do_compile failed Next steps: - apply the patch: git am

[OE-core] [AUH] go-runtime: upgrading to 1.22.0 FAILED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *go-runtime* to *1.22.0* has Failed (devtool error). Detailed error information: Running 'devtool upgrade' for recipe go-runtime failed. NOTE: Reconnecting to bitbake server...

[OE-core] [AUH] expat: upgrading to 2.6.1 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *expat* to *2.6.1* has Succeeded. Next steps: - apply the patch: git am 0001-expat-upgrade-2.6.0-2.6.1.patch - check the changes to upstream patches and summarize them in

[OE-core] [AUH] ell: upgrading to 0.63 SUCCEEDED

Hello, this email is a notification from the Auto Upgrade Helper that the automatic attempt to upgrade the recipe *ell* to *0.63* has Succeeded. Next steps: - apply the patch: git am 0001-ell-upgrade-0.62-0.63.patch - check the changes to upstream patches and summarize them in the commit

[OE-core] Easy way to talk to hashserv or prserv?

Hi Joshua and all, I'm going to test changes to the prserv server, to implement "passthrough" to another server. I can make tests by checking the impact of my changes on the build results, like checking the revision of generated packages. However, would there be an easy way to make a test

Re: [OE-core] [PATCH 2/2] no-gplv3: Tweak for packagemangement in core-image-full-cmdline

On Fri, Mar 1, 2024 at 1:35 AM Richard Purdie < richard.pur...@linuxfoundation.org> wrote: > If we enable package-management for core-image-full-cmdline we need the > workarounds > used for core-image-weston to ensure the oe-selftest license QA tests keep > working. > > Signed-off-by: Richard

[OE-core][PATCH] testimage: allow to set runqemu bootparams option

From: michal seben Allow to set runqemu bootparams option using TEST_EXTRABOOTPARAMS variable. This option can be used .e.g. to mask service only for testimage task. Signed-off-by: michal seben --- meta/classes-recipe/testimage.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)

Patchtest results for [OE-core][PATCH] testimage: allow to set runqemu bootparams option

Thank you for your submission. Patchtest identified one or more issues with the patch. Please see the log below for more information: --- Testing patch /home/patchtest/share/mboxes/testimage-allow-to-set-runqemu-bootparams-option.patch FAIL: test Signed-off-by presence: Mbox is missing

[OE-core][PATCH] testimage: allow to set runqemu bootparams option

From: michal seben Allow to set runqemu bootparams option using TEST_EXTRABOOTPARAMS variable. This option can be used .e.g. to mask service only for testimage task. --- meta/classes-recipe/testimage.bbclass | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

Re: [OE-core] [RFC OE-core][PATCH v2 6/7] go: upgrade 1.21.5 -> 1.21.7

On Wed, 2024-02-28 at 18:30 +, Jose Quaresma wrote: > Upgrade to latest 1.21.x release [1]: > > $ git --no-pager log --oneline go1.21.5..go1.21.7 > f29208030a (tag: go1.21.7) [release-branch.go1.21] go1.21.7 > 2fdad8af6d [release-branch.go1.21] cmd/internal/obj/arm64: fix frame pointer >

[OE-core] [PATCH 1/2] qemu: Replace workaround with proper usermode fix for shmat

We were using a workaround to avoid problems with the behaviour of shmat() calls in usermode qemu. Switch to patches from upstream which are in review but not merged yet. Update the mmap fixed/noreplace workaround for the changes. Signed-off-by: Richard Purdie ---

[OE-core] [PATCH 2/2] no-gplv3: Tweak for packagemangement in core-image-full-cmdline

If we enable package-management for core-image-full-cmdline we need the workarounds used for core-image-weston to ensure the oe-selftest license QA tests keep working. Signed-off-by: Richard Purdie --- meta/conf/distro/include/no-gplv3.inc | 2 ++ 1 file changed, 2 insertions(+) diff --git

Re: [OE-core] [PATCH 3/3] rust: reproducibility issue fix with v1.75

On Thu, 2024-02-29 at 08:32 -0800, Shinde, Yash via lists.openembedded.org wrote: > From: Yash Shinde > > With 1.75 rust release, the '.rustc' section of shared object libs > are embedded with absolute path names which is casuing > reproducibiluty issues. > This change will fix the path name