On Sun, 2023-06-11 at 17:16 +0200, Alexander Kanavin wrote:
> Doesn't += override the earlier ?=
It depends. If ?= is parsed first, += will append. If the ?= is parsed
after +=, the ?= will not happen as the variable has a value.
> (or ??=),
+= would override ??=
Cheers,
Richard
-=-=-=-=-=-
On Wed, Jun 14, 2023 at 11:32 PM 张家岭 wrote:
>
> Hi Khem,
>
> I noticed the issue you mentioned, I want to fix it , but I'm not
> sure how to reproduce it on my build machine .Please how can I debug
> this issue use the autobuilder.yoctoproject.org builders .
>
add meta-clang to your layers
It's in master too:
https://github.com/besser82/libxcrypt/commits/master
I don't know why github won't show that but using master is preferable
over develop.
4.4.35 will be provided by AUH in due time and taken into the next
batch; I don't chase shifting 'latest upstream versions' when making
and
I have modified the patch again, and the new patch does not need to modify the
upstream xz.
The link of the new patch:
openembedded-core@lists.openembedded.org | [meta-oe][PATCH V2] xz: add ptest
support (
https://lists.openembedded.org/g/openembedded-core/topic/meta_oe_patch_v2_xz_add/99334931
With this upgrade I get:
| checking whether MB_CUR_MAX is correct... configure: error: in
`/yocto/ross/build/tmp/work/cortexa57-poky-linux/coreutils/9.3-r0/build':
| configure: error: cannot run test program while cross compiling
Ross
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent
From: Mingli Yu
The qemu rpm can be split or not via customize PACKAGESPLITFUNCS and
there is no specific qemu emulation rpm installed when we choose split
the qemu rpms now.
To gurantee the basic usage, install the qemu emulation rpm which
corresponding to the target arch by default when split
[Edited Message Follows]
I have modified the patch again, and the new patch does not need to modify the
upstream xz.
The link of the new patch:
[meta-oe][PATCH V3] xz: add ptest support (openembedded.org) (
https://lists.openembedded.org/g/openembedded-core/message/182481 )
Du
-=-=-=-=-=-=-=-=
Hello Alex
I have modified the patch again, and the new patch does not need to modify the
upstream xz.
The link of the new patch:
https://lists.openembedded.org/g/openembedded-core/message/182481
Du
-邮件原件-
发件人: openembedded-core@lists.openembedded.org
代表 Alexander Kanavin
发送时间: 2023年6
Hi Richard,
On Thu, Jun 15, 2023 at 08:03:44AM +0100, Richard Purdie wrote:
> On Sun, 2023-06-11 at 17:16 +0200, Alexander Kanavin wrote:
> > Doesn't += override the earlier ?=
>
> It depends. If ?= is parsed first, += will append. If the ?= is parsed
> after +=, the ?= will not happen as the var
This didn’t happen in a-full so can you check wh ere the difference is?
Alex
On Thu 15. Jun 2023 at 10.14, Ross Burton wrote:
> With this upgrade I get:
>
> | checking whether MB_CUR_MAX is correct... configure: error: in
> `/yocto/ross/build/tmp/work/cortexa57-poky-linux/coreutils/9.3-r0/build
Upstream-Status: Backport from
https://github.com/openssl/openssl/commit/9e209944b35cf82368071f160a744b6178f9b098
Signed-off-by: Hitendra Prajapati
---
.../openssl/openssl/CVE-2023-2650.patch | 122 ++
.../openssl/openssl_1.1.1t.bb | 1 +
2 files changed,
On Thu, 2023-06-15 at 11:34 +0300, Mikko Rapeli wrote:
> Hi Richard,
>
> On Thu, Jun 15, 2023 at 08:03:44AM +0100, Richard Purdie wrote:
> > On Sun, 2023-06-11 at 17:16 +0200, Alexander Kanavin wrote:
> > > Doesn't += override the earlier ?=
> >
> > It depends. If ?= is parsed first, += will appe
This is a follow-up of 76e5fcb2 that also allow users to chose
the package manager using OEQA_REPRODUCIBLE_TEST_PACKAGE
Signed-off-by: Jose Quaresma
---
meta/lib/oeqa/selftest/cases/reproducible.py | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/ca
From: Alberto Planas
openSUSE RPMs are compressing the RPM payload using zstd, that
correspond to the magic ID 0x28, 0xb5, 0x2f.
This patch update the script to the last version from the rpm project,
and add support to this compression format, and extract the cpio payload
using the "unzstd" bina
From: Alberto Planas
rpm2cpio.sh can make calls to unzstd to uncompress the RPM payload that
conform the cpio file.
zstd is already part of HOSTTOOLS, as a link to the system installed
zstd.
This patch add unzstd in HOSTOOLS list as a non-optional binary, so is
available to rpm2cpio.sh when it
This is a suggestion to replace the management of sysusers.d in the build.
sysusers.d is a set of configuration files to declare system users and groups
supposed to be created at boot when they do not exist.
Until now, we have a rootfs post command that checks those configuration and
creates miss
The configuration in sysusers.d used to be parsed to create users/groups at
build time instead at runtime. This was leading to several conflicts with
users/groups defined in base-passwd recipe and specific definitions in recipes
inheriting the useradd class. Some of those conflicts raised unseen er
The default sysusers basic.conf.in file sets the root home directory to `/root`
and does not permit its configuration. Replace the file delivered by systemd so
the root home directory matches the `ROOT_HOME` variable.
Signed-off-by: Louis Rannou
---
meta/recipes-core/systemd/systemd/basic.conf.i
The wheel group is not declared while it can be used to access the systemd
journal and to configure printers in CUPS. It can also be used for su and sudo
permissions.
So far it was created later in the rootfs postcommand systemd_create_users.
Signed-off-by: Louis Rannou
---
.../base-passwd/0007
On Thu, Jun 15, 2023 at 2:59 AM Richard Purdie
wrote:
>
> On Wed, 2023-06-14 at 23:16 -0400, bruce.ashfi...@gmail.com wrote:
> > From: Bruce Ashfield
> >
> > The commit in question appeared as -stable backport in 6.1.28, which is
> > where we started to see intermittent boot hangs on x86.
> >
> >
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
2f3918bc53fb Linux 6.1.33
c3fcfe8931e1 ext4: enable the lazy init thread when remounting read/write
84683a2cf5ed selftests: mptcp: join: avoid using 'cmp --bytes'
fbb6db561dd4
From: Ross Burton
There is a missing comma in an AC_TRY_RUN call which means it has no
fallback for cross-compilation, so if the host doesn't have a French
locale then AC_TRY_RUN fails.
Signed-off-by: Ross Burton
---
.../coreutils/stdlib-mb-cur-max.patch | 33 +++
meta/
From: Deepthi Hemraj
Below commits on glibc-2.37 stable branch are updated.
3593050c27 (HEAD -> release/2.37/master, origin/release/2.37/master) io: Fix
F_GETLK, F_SETLK, and F_SETLKW for powerpc64
e2974d26ce io: Fix record locking contants on 32 bit arch with 64 bit default
time_t 0e3e9dbb0e D
Regression testing is done and below are the test results.
*Before glibc update*
Summary of test results:
210 FAIL
4380 PASS
38 UNSUPPORTED
16 XFAIL
2 XPASS
*After glibc update*
Summary of test results:
194 FAIL
4401 PASS
38 UNSUPPORTED
16 XFAIL
2 XPASS
*Diff:*
16 FAIL
21 PASS
0 UNSUPPORTED
0 XF
On Mon, 2023-06-12 at 13:57 +0200, Andrej Valek via
lists.openembedded.org wrote:
> - Replace CVE_CHECK_IGNORE with CVE_STATUS + [CVE_STATUS_DETAIL] +
> [CVE_STATUS_DESCRIPTION] to be more flexible. CVE_STATUS should
> contain flag for each CVE with accepted values "Ignored", "Patched"
> or "Unpatc
On Thu, 2023-06-15 at 12:54 +0200, Alberto Planas via
lists.openembedded.org wrote:
> From: Alberto Planas
>
> rpm2cpio.sh can make calls to unzstd to uncompress the RPM payload that
> conform the cpio file.
>
> zstd is already part of HOSTTOOLS, as a link to the system installed
> zstd.
>
> Th
> From: Richard Purdie
> Couldn't we just use zstd -d in the script? They're always the same
> binary anyway as far as I understand it...
Yes, this should work. I decided to include the second patch to avoid changing
the rpm2cpio.sh code, that is a verbatim copy of the upstream script (minus th
Backport initramfs fixes from master/Kirkstone for building FIT images.
This allows embedding an initramfs either as an entry in the FIT image,
or embedded along with the kernel.
Backporting patch #1 required some adaptation to the Dunfell branch.
Testing done:
generate a FIT image with INITRAMFS
From: Abdellatif El Khlifi
This commit adds Initramfs bundle support to the FIT image in addition
to u-boot boot script capability.
These new features are selectable.
In case of Initramfs, the kernel is configured to be bundled with the rootfs
in the same binary (ie: zImage-initramfs-.bin). Whe
From: Andrej Valek
Even if initramfs_bundle_path was used, a wrong compression was reflected
in output its template file. Use linux.bin as universal kernel image.
The linux.bin file covers both cases because it's beying created from
vmlinux.
We know, that vmlinux is created inside compressed dir
On Thu, 2023-06-15 at 12:58 +, Alberto Planas Dominguez wrote:
> > From: Richard Purdie
>
> > Couldn't we just use zstd -d in the script? They're always the same
> > binary anyway as far as I understand it...
>
> Yes, this should work. I decided to include the second patch to avoid
> changin
On Sun, Jun 4, 2023 at 10:34 PM Martin Jansa wrote:
> > It might be useful to delay backporting this for a bit longer (and I'll
> soon confirm if 3.10 was already affected or not).
>
> I can confirm that 3.10 is also affected.
>
> I did build with
> https://git.openembedded.org/openembedded-core-
On 14 Jun 2023, at 10:28, Alexander Kanavin via lists.openembedded.org
wrote:
>
> Drop all patches, as issues are all fixed upstream.
>
> License-Update: clarification that GPL applies to all executables
> (not just test), formatting.
This drops the pkgconfig file into /lib/pkgconfig, which do
Well, after typing all of that I've realized that it might be related to:
https://github.com/NixOS/patchelf/issues/244
as we had similar issue before:
https://git.openembedded.org/openembedded-core/commit/?id=cccd4bcaf381c2729adc000381bd89906003e72a
On Thu, Jun 15, 2023 at 5:06 PM Martin Jansa vi
On 15 Jun 2023, at 16:10, Ross Burton via lists.openembedded.org
wrote:
>
> On 14 Jun 2023, at 10:28, Alexander Kanavin via lists.openembedded.org
> wrote:
>>
>> Drop all patches, as issues are all fixed upstream.
>>
>> License-Update: clarification that GPL applies to all executables
>> (no
On Thu, 15 Jun 2023 at 17:25, Ross Burton wrote:
> > This drops the pkgconfig file into /lib/pkgconfig, which doesn’t look right.
>
> This is because the recipe sets libdir=$base_libdir, for historical reasons
> that we can ignore[1]. Delete that line.
>
> [1] pcmciautils also puts stuff into /b
Nothing really surprising here, except we should note that launcher-logind is
being depreciated so some thought on how that is dealt with will need to occur.
Eilís 'pidge' Ní Fhlannagáin (3):
wayland-utils: upgrade 1.1.0 -> 1.2.0
weston: Upgrade 11.0.1 -> 12.0.1
xwayland: Upgrade 23.1.1 ->
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin
---
.../xwayland/{xwayland_23.1.1.bb => xwayland_23.1.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-graphics/xwayland/{xwayland_23.1.1.bb =>
xwayland_23.1.2.bb} (95%)
diff --git a/meta/recipes-graphics/xwayla
Tracking https://gitlab.freedesktop.org/wayland/weston/-/issues/488
we're keeping -Ddeprecated-launcher-logind but plans should be made to
remove this/work around.
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin
---
.../wayland/{weston_11.0.1.bb => weston_12.0.1.bb} | 10 +++---
1 file chang
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin
---
...ayland-info-Fix-build-without-libdrm.patch | 42 ---
...-utils_1.1.0.bb => wayland-utils_1.2.0.bb} | 3 +-
2 files changed, 1 insertion(+), 44 deletions(-)
delete mode 100644
meta/recipes-graphics/wayland/files/0001-wayland-inf
There's already:
PACKAGECONFIG[launcher-libseat] =
"-Dlauncher-libseat=true,-Dlauncher-libseat=false,seatd" used in
sysvinit builds,
and oe-core has the seatd recipe. So this could simply become a hard
dependency later on.
Alex
On Thu, 15 Jun 2023 at 21:23, Eilís 'pidge' Ní Fhlannagáin
wrote:
>
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Steve Sakoman
> Sent: den 14 juni 2023 16:05
> To: openembedded-core@lists.openembedded.org
> Subject: [OE-core][dunfell 3/5] systemd-systemctl: fix instance template
> WantedBy
On Thu, 2023-06-15 at 20:40 +, Peter Kjellerstedt wrote:
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org > c...@lists.openembedded.org> On Behalf Of Steve Sakoman
> > Sent: den 14 juni 2023 16:05
> > To: openembedded-core@lists.openembedded.org
> > Subject: [O
ip tuntap provides the functionality that we obtained from tunctl. We only
needed tunctl when ifconfig was more available than ip. That isn't the case
now so we can drop tunctl and all the hoops we need to jump through to build
and provide it.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/self
The IFCONFIG variable is really the path to ip and hasn't been
ifconfig for a long time. Rename the variable to something less
confusing.
Signed-off-by: Richard Purdie
---
scripts/runqemu-ifdown | 12 ++--
scripts/runqemu-ifup | 16
2 files changed, 14 insertions(+), 1
From: Randolph Sapp
I know my text editor is going to get angry at me if this continues.
Signed-off-by: Randolph Sapp
Signed-off-by: Richard Purdie
---
meta/recipes-graphics/wayland/weston-init.bb | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/meta/recipes-grap
From: Randolph Sapp
Add profile script to point users capable of interacting with the global
socket to it by default.
Signed-off-by: Randolph Sapp
Signed-off-by: Richard Purdie
---
meta/recipes-graphics/wayland/weston-init.bb | 3 +++
.../wayland/weston-init/weston-socket.sh | 20 +
From: Randolph Sapp
Just as sysvinit scripts shouldn't be present in a distro using systemd,
systemd scripts shouldn't be present in a system not using systemd.
Signed-off-by: Randolph Sapp
Signed-off-by: Richard Purdie
---
meta/recipes-graphics/wayland/weston-init.bb | 29 ---
From: Randolph Sapp
Backport all the weston-init QOL updates. Getting closer to the point
where we can actually drop our distro specific weston-init bbappend. May
submit a few more QOL patches sooner or later to completely drop it.
Ming Liu (1):
weston-init: introduce xwayland PACKAGECONFIG
R
From: Ming Liu
Some BSPs dont support xwayland in weston, this is easier for them to
control that.
Signed-off-by: Ming Liu
Signed-off-by: Richard Purdie
---
meta/recipes-graphics/wayland/weston-init.bb | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-graph
From: Randolph Sapp
Add the render group explicitly here to make sure it exists for the
useradd command.
Signed-off-by: Randolph Sapp
Signed-off-by: Alexandre Belloni
---
meta/recipes-graphics/wayland/weston-init.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/reci
From: ssuesens
set xwayland support in weston.init file to true
Signed-off-by: ssuesens
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
---
meta/recipes-graphics/wayland/weston-init.bb | 4
1 file changed, 4 insertions(+)
diff --git a/meta/recipes-graphics/wayland/weston
From: Randolph Sapp
The weston user must be in the render group in order to access render
device nodes for standard user-space graphics.
Signed-off-by: Randolph Sapp
Signed-off-by: Alexandre Belloni
---
meta/recipes-graphics/wayland/weston-init.bb | 2 +-
1 file changed, 1 insertion(+), 1 del
From: Randolph Sapp
Add the weston user to the wayland group so all users accessing the
global weston socket in /run all share a group.
Signed-off-by: Randolph Sapp
Signed-off-by: Alexandre Belloni
---
meta/recipes-graphics/wayland/weston-init.bb | 2 +-
1 file changed, 1 insertion(+), 1 dele
> -Original Message-
> From: openembedded-core@lists.openembedded.org c...@lists.openembedded.org> On Behalf Of Richard Purdie
> Sent: den 15 juni 2023 11:05
> To: Mikko Rapeli
> Cc: Alexander Kanavin ;
> alexis.loth...@bootlin.com; Openembedded-core@lists.openembedded.org;
> Thomas Petaz
On Thu, Jun 15, 2023 at 10:41 AM Peter Kjellerstedt
wrote:
>
> > -Original Message-
> > From: openembedded-core@lists.openembedded.org > c...@lists.openembedded.org> On Behalf Of Steve Sakoman
> > Sent: den 14 juni 2023 16:05
> > To: openembedded-core@lists.openembedded.org
> > Subject: [
Hello,
Which ptest are you trying to fix?
I got:
https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5023/steps/13/logs/stdio
https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5207/steps/12/logs/stdio
{'glib-2.0': ['glib/file.test']}
On 14/06/2023 11:28:36+0200, Ale
On 16/06/2023 00:27:00+0200, Alexandre Belloni wrote:
> Hello,
>
> Which ptest are you trying to fix?
>
> I got:
> https://autobuilder.yoctoproject.org/typhoon/#/builders/82/builds/5023/steps/13/logs/stdio
> https://autobuilder.yoctoproject.org/typhoon/#/builders/81/builds/5207/steps/12/logs/stdi
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kbd* to *2.6.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-kbd-upgrade-2.5.1-2.6.0.patch
- check the changes to upstream patches and summarize them in the comm
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *coreutils* to *9.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-coreutils-upgrade-9.1-9.3.patch
- check the changes to upstream patches and summarize them in t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *253.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-systemd-boot-upgrade-253.3-253.5.patch
- check the changes to upstream patches and summari
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gdb* to *13.2* has Succeeded.
Next steps:
- apply the patch: git am 0001-gdb-upgrade-13.1-13.2.patch
- check the changes to upstream patches and summarize them in the commit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lua* to *5.4.6* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe lua failed.
NOTE: Starting bitbake server...
WARNING: Host distribution
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.3.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.3-6.3.1.patch
- check the changes to upstream patches and summarize t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxcrypt-compat* to *4.4.35*
has Succeeded.
Next steps:
- apply the patch: git am 0001-libxcrypt-compat-upgrade-4.4.33-4.4.35.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux-libuuid* to *2.39*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-util-linux-libuuid-upgrade-2.3
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gcc-source-13.1.1* to
*14-20230611* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gcc-source-13.1.1 -V 14-20230611
NOTE: St
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *jquery* to *3.7.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-jquery-upgrade-3.6.3-3.7.0.patch
- ch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *1.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-1.1.0-1.1.1.patch
- check the changes to upstream patches and summarize them in the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxml2* to *2.11.4* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libxml2 failed.
NOTE: Starting bitbake server...
WARNING: Host dis
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202305*
has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe ovmf failed.
NOTE: Starting bitbake server...
NOTE: Reconn
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-flit-core* to *3.9.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-flit-core-upgrade-3.8.0-3.9.0.patch
- check the changes to upstream patches a
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-iso8601* to *2.0.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-iso8601-upgrade-1.1.0-2.0.0.patch
- check the changes to upstream patches and s
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pygments* to *2.15.1*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-pygments-upgrade-2.14.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux* to *2.39* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-util-linux-upgrade-2.38.1-2.39.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.8.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.8.1-4.8.2.patch
- check the changes to upstream patches and summarize them in t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography* to
*41.0.1* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3-cryptography failed.
NOTE: Starting bitbake s
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libmodulemd* to *2.15.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libmodulemd-upgrade-2.14.0-2.15.0.patch
- check the changes to upstream patches and summar
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography-vectors*
to *41.0.1* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-python3-cryptogra
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *git* to *2.41.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-git-upgrade-2.39.3-2.41.0.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *squashfs-tools* to *4.6.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-squashfs-tools-upgrade-4.5.1-4.6.1.patch
- check the changes to upstream patches and sum
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pytest* to *7.3.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pytest-upgrade-7.3.1-7.3.2.patch
- check the changes to upstream patches and sum
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.78.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.75.7-6.78.2.patch
- check the changes to upstream pat
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-importlib-metadata*
to *6.6.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-importlib-metadata-upgrade-6.2.0-6.6.0.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-certifi* to
*2023.5.7* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-certifi-upgrade-2022.12.7-2023.5.7.patch
- check the changes to upstream pa
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gawk* to *5.2.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gawk-upgrade-5.2.1-5.2.2.patch
- check the changes to upstream patches and summarize them in the c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *16.0.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-llvm-upgrade-16.0.5-16.0.6.patch
- check the changes to upstream patches and summarize them in th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*67.8.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3* to *3.11.4* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe python3 failed.
NOTE: Starting bitbake server...
WARNING: Host dis
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatchling* to
*1.18.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.17.0-1.18.0.patch
- check the changes to upstream patche
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kmscube* to
*0be1681d09e77330e02b8d4708e47a04585f4b16* has Succeeded.
Next steps:
- apply the patch: git am 0001-kmscube-upgrade-to-latest-revision.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-typing-extensions* to
*4.6.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-typing-extensions-upgrade-4.6.2-4.6.3.patch
- check the changes to u
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pyasn1* to *0.5.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pyasn1-upgrade-0.4.8-0.5.0.patch
- check the changes to upstream patches and sum
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *parted* to *3.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-parted-upgrade-3.5-3.6.patch
- check the changes to upstream patches and summarize them in the com
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-urllib3* to *2.0.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-urllib3-upgrade-2.0.2-2.0.3.patch
- check the changes to upstream patches and s
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-docutils* to *0.20.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-docutils-upgrade-0.19-0.20.1.patch
- check the changes to upstream patches an
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-validation-layers* to
*1.3.250.0* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe vulkan-validation-layers failed.
NOTE: Startin
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mmc-utils* to
*6d593efc3cd00e4debd0ffc5806246390dc66242* has Succeeded.
Next steps:
- apply the patch: git am 0001-mmc-utils-upgrade-to-latest-revision.patch
- check the cha
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-markupsafe* to
*2.1.3* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-markupsafe-upgrade-2.1.2-2.1.3.patch
- check the changes to upstream patches
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffutils* to *3.10* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe diffutils failed.
NOTE: Starting bitbake server...
NOTE: Reconnect
1 - 100 of 136 matches
Mail list logo
