>
>
> +From afa85b75607649f3a89cb4d17cf3f003738d3576 Mon Sep 17 00:00:00 2001
> +From: Hitendra Prajapati
> +Date: Fri, 2 Dec 2022 11:22:39 +0530
> +Subject: [PATCH] CVE-2022-36227
> +
> +Upstream-Status: Backport [
> https://github.com/libarchive/libarchive/commit/bff38efe8c110469c5080d387bec62a6
On Fri, Dec 2, 2022 at 5:32 AM Hitendra Prajapati
wrote:
> Hi team,
>
> Why this issue is unattended ?? Any issue in merged ??
>
Steve replied to you shortly after your e-mail, maybe you haven't seen this
reply?
https://lists.openembedded.org/g/openembedded-core/message/173079
-=-=-=-=-=-=-=-=
I see the same fixes with correct Author in .patch files (please don't
change the Author when you're just backporting a patch from someone else)
queued from someone else in kirkstone-nut branch:
https://git.openembedded.org/openembedded-core-contrib/commit/?h=stable/kirkstone-nut&id=518bea85c9496d7
Upstream-Status: Backport from
https://github.com/libarchive/libarchive/commit/bff38efe8c110469c5080d387bec62a6ca15b1a5
Signed-off-by: Hitendra Prajapati
---
.../libarchive/CVE-2022-36227.patch | 41 +++
.../libarchive/libarchive_3.6.1.bb| 4 +-
2 files ch
Am Do, 1. Dez 2022 um 11:44:16 -0800 schrieb Khem Raj
:
build for qemuriscv32 to find out.
mesa 22.3.0 did compile for qemuriscv32 without errors
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174222):
https://lists.openembedded.org/g/openembe
Hi team,
Why this issue is unattended ?? Any issue in merged ??
Please look at this issue, Which fixed for Go package .
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174221):
https://lists.openembedded.org/g/openembedded-core/message/174221
Mute
Hi team,
Why this issue is unattended ?? Any issue in merged ??
Please look at this issue, Which fixed for Go package .
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174220):
https://lists.openembedded.org/g/openembedded-core/message/174220
Mut
Hi Steve/Team ,
Any update or issue with this patches ?? Why it is not picked or merged ?
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174219):
https://lists.openembedded.org/g/openembedded-core/message/174219
Mute This Topic: https://lists.opene
From: Wang Mingyu
Changelog:
==
* fixes:
* resize cancel did not work in some cases
* fix fileattr stream command format and add workaround when it cannot be
applied
* properly handle degraded raid56 reads
* fi defrag: fix verbosity, don't print file names by default
* rec
On Thu, Dec 1, 2022 at 3:20 PM Richard Purdie
wrote:
>
> On Thu, 2022-12-01 at 15:07 -0800, Khem Raj wrote:
> > On Thu, Dec 1, 2022 at 3:05 PM Alexandre Belloni
> > wrote:
> > >
> > > On 01/12/2022 19:12:50+, Richard Purdie wrote:
> > > > On Thu, 2022-12-01 at 11:02 -0800, Khem Raj wrote:
> >
On Thu, 2022-12-01 at 15:07 -0800, Khem Raj wrote:
> On Thu, Dec 1, 2022 at 3:05 PM Alexandre Belloni
> wrote:
> >
> > On 01/12/2022 19:12:50+, Richard Purdie wrote:
> > > On Thu, 2022-12-01 at 11:02 -0800, Khem Raj wrote:
> > > > pseudo overrides certain libc functions which are aliases when
On Thu, Dec 1, 2022 at 3:05 PM Alexandre Belloni
wrote:
>
> On 01/12/2022 19:12:50+, Richard Purdie wrote:
> > On Thu, 2022-12-01 at 11:02 -0800, Khem Raj wrote:
> > > pseudo overrides certain libc functions which are aliases when LFS64 is
> > > enabled. In anycase pseudo may not be much used
On 01/12/2022 19:12:50+, Richard Purdie wrote:
> On Thu, 2022-12-01 at 11:02 -0800, Khem Raj wrote:
> > pseudo overrides certain libc functions which are aliases when LFS64 is
> > enabled. In anycase pseudo may not be much used on 32bit systems anyway
> >
> > Signed-off-by: Khem Raj
> > ---
>
It is reported:
https://bugzilla.yoctoproject.org/show_bug.cgi?id=14979
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#174213):
https://lists.openembedded.org/g/openembedded-core/message/174213
Mute This Topic: https://lists.openembedded.org/mt/953
* The build error happens already at configure time:
| meson.build: ERROR: Problem encountered: DRI3 requested, but xshmfence not
found
Signed-off-by: Carlos Alberto Lopez Perez
---
meta/recipes-graphics/xwayland/xwayland_22.1.5.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --
On Thu, Dec 1, 2022 at 9:39 AM Markus Volk wrote:
>
> - remove deprecated xvmc PACKAGECONFIG
> - remove futex.h patch. Code has been reworked, still needed?
>
build for qemuriscv32 to find out.
> Note: mesa-22.3.0 will require libperfetto update to v28. Otherwise
> compilation will fail.
>
> Si
pseudo overrides certain libc functions which are aliases when LFS64 is
enabled. In anycase pseudo may not be of much use on 32bit systems
Signed-off-by: Khem Raj
---
v2: Add comment for this in recipe
meta/recipes-devtools/pseudo/pseudo_git.bb | 7 +++
1 file changed, 7 insertions(+)
diff
On Thu, 2022-12-01 at 11:02 -0800, Khem Raj wrote:
> pseudo overrides certain libc functions which are aliases when LFS64 is
> enabled. In anycase pseudo may not be much used on 32bit systems anyway
>
> Signed-off-by: Khem Raj
> ---
> meta/recipes-devtools/pseudo/pseudo_git.bb | 2 ++
> 1 file c
On Thu, 1 Dec 2022 at 20:02, Khem Raj wrote:
> +Upstream-Status: Pending
Please submit this and all other patches in this set upstream first.
Come on Khem, you should expect this response, and I should not have
to tell you.
Alex
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to t
Using -D_FILE_OFFSET_BITS=64 already makes the normal function behave
like 64bit variants. Moreover it makes them portable across libc
Signed-off-by: Khem Raj
---
...-to-enable-disable-largefile-support.patch | 57 +++
.../e2fsprogs/e2fsprogs_1.46.5.bb | 3 +-
2 file
pseudo overrides certain libc functions which are aliases when LFS64 is
enabled. In anycase pseudo may not be much used on 32bit systems anyway
Signed-off-by: Khem Raj
---
meta/recipes-devtools/pseudo/pseudo_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-devtools/pseud
Using -D_FILE_OFFSET_BITS=64 already makes the normal function behave
like 64bit variants. Moreover it makes them portable across libc
Signed-off-by: Khem Raj
---
...pwrite-pread-instead-of-64bit-versio.patch | 39 +++
.../xorg-lib/libpciaccess_0.17.bb | 2 +
2 files
Using -D_FILE_OFFSET_BITS=64 already makes the normal function behave
like 64bit variants. Moreover it makes them portable across libc
Signed-off-by: Khem Raj
---
...-ftruncate-stat-instead-of-64bit-equ.patch | 903 ++
.../btrfs-tools/btrfs-tools_6.0.1.bb | 1 +
2 file
Signed-off-by: Khem Raj
---
...FILE_OFFSET_BITS-to-enable-largefile.patch | 147 ++
meta/recipes-extended/mdadm/mdadm_4.2.bb | 1 +
2 files changed, 148 insertions(+)
create mode 100644
meta/recipes-extended/mdadm/files/0001-restripe.c-Use-_FILE_OFFSET_BITS-to-enable-larg
This ensures right flags are passed so enable it. Musl and decoupled
these APIs from _GNU_SOURCE and now are only available when
_LARGEFILE64_SOURCE macro is enabled
Signed-off-by: Khem Raj
---
...rtable-version-of-dirent-and-readdir.patch | 39 +++
meta/recipes-support/attr/acl_
It seems some layers want to subvert the intent of LAYERSERIES_COMPAT
so bitbake is going to have to become stricter about the values there.
To work with this, use LAYERSERIES_CORENAMES to generate the entries in
LAYERSERIES_COMPAT instead of the current magic LAYERSERIES_COMPAT_core
value which ma
We've seen two different regressions in this API since it is used by
layer-index but not be the core code. Add a test for it to try and
ensure we don't break it again.
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/selftest/cases/tinfoil.py | 14 ++
1 file changed, 14 insertions(+)
- remove deprecated xvmc PACKAGECONFIG
- remove futex.h patch. Code has been reworked, still needed?
Note: mesa-22.3.0 will require libperfetto update to v28. Otherwise compilation
will fail.
Signed-off-by: Markus Volk
---
...fine-__NR_futex-if-it-does-not-exist.patch | 34 ---
Includes fixes for CVE-2022-4141
https://nvd.nist.gov/vuln/detail/CVE-2022-4141
For a short list of important changes, see:
https://www.arp242.net/vimlog/
Signed-off-by: Zheng Qiu
---
meta/recipes-support/vim/vim.inc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/r
Am Do, 1. Dez 2022 um 16:12:04 +0100 schrieb Alexandre Belloni via
lists.openembedded.org
:
../gcr-4.0.0/docs/meson.build:1:0: ERROR: Program 'gi-docgen' not
found or not executable
Added a PACKAGECONFIG for iso-codes install and made sure i was able to
create doc for gcr
-=-=-=-=-=-=-=-=-
Signed-off-by: Markus Volk
---
.../graphene/graphene_1.10.8.bb | 22 +++
1 file changed, 22 insertions(+)
create mode 100644 meta/recipes-graphics/graphene/graphene_1.10.8.bb
diff --git a/meta/recipes-graphics/graphene/graphene_1.10.8.bb
b/meta/recipes-graphics/gr
Signed-off-by: Markus Volk
---
meta/conf/distro/include/maintainers.inc | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/conf/distro/include/maintainers.inc
b/meta/conf/distro/include/maintainers.inc
index 03db94824d..1426491791 100644
--- a/meta/conf/distro/include/maintainers.inc
++
Signed-off-by: Markus Volk
---
meta/recipes-gnome/gtk+/gtk4_4.8.2.bb | 129 ++
1 file changed, 129 insertions(+)
create mode 100644 meta/recipes-gnome/gtk+/gtk4_4.8.2.bb
diff --git a/meta/recipes-gnome/gtk+/gtk4_4.8.2.bb
b/meta/recipes-gnome/gtk+/gtk4_4.8.2.bb
new file
Please ignore this patch. The fix sent by Peter
https://lists.openembedded.org/g/openembedded-core/topic/95382667#174061
is better.
On Tue, 2022-11-29 at 17:26 +, Adrian Freihofer wrote:
> Hi
>
> As of today, Fedora 36 is considered a stable host distribution.
> However, without this patch e
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gobject-introspection* to
*1.74.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-gobject-introspection-upgrade-1.72.0-1.74.0.patch
- check the changes to upstre
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libinput* to *1.22.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libinput-upgrade-1.21.0-1.22.0.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*71eb7b6880c842da2c2414f2be9468e9fd95d525* has Succeeded.
Next steps:
- apply the patch: git am 0001-piglit-upgrade-to-latest-revision.patch
- check the changes t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxpm* to *3.5.14* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxpm -V 3.5.14
NOTE: Starting bitbake server...
NOTE: R
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemtap-uprobes* to *4.8*
has Succeeded.
Next steps:
- apply the patch: git am 0001-systemtap-uprobes-upgrade-4.7-4.8.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 *gcr* to *4.0.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gcr failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitb
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.35* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gtk+3 failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting t
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mpfr* to *4.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mpfr-upgrade-4.1.0-4.1.1.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 *diffoscope* to *227* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-224-227.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kmscube* to
*345111481d654b38a72b5c3629151dc74f7a82bc* 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 *wayland-protocols* to *1.31*
has Succeeded.
Next steps:
- apply the patch: git am 0001-wayland-protocols-upgrade-1.28-1.31.patch
- check the changes to upstream patches and
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.15.00* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.14.06-0.15.00.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 *python3-pathspec* to *0.10.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pathspec-upgrade-0.10.1-0.10.2.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 *libxdmcp* to *1.1.4* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxdmcp -V 1.1.4
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mesa* to *22.3.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe mesa failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to b
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ghostscript* to *10.0.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-ghostscript-upgrade-9.56.1-10.0.0.p
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*03cb22873adbfc20e118d60144208aa47ed7d087* has Failed(other errors).
Detailed error information:
'MACHINE=qemux86 bitbake vulkan-samples' failed
WARNING: Host di
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemtap* to *4.8* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-systemtap-upgrade-4.7-4.8.patch
- ch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libnewt* to *0.52.23* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libnewt failed.
NOTE: Starting bitbake server...
NOTE: Reconnecti
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *texinfo* to *7.0.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-texinfo-upgrade-7.0-7.0.1.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 *libxrandr* to *1.5.3* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libxrandr -V 1.5.3
NOTE: Starting bitbake server...
NOT
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *epiphany* to *43.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-epiphany-upgrade-42.4-43.0.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *repo* to *2.30* has Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.29.9-2.30.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 *shaderc* to *2022.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-shaderc-upgrade-2022.3-2022.4.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-urllib3* to *1.26.13*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-urllib3-upgrade-1.26.12-1.26.13.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 *tzdata* to *2022g* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2022d-2022g.patch
- ch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *swig* to *4.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-swig-upgrade-4.1.0-4.1.1.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 *python3-dbusmock* to *0.28.6*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-python3-dbusmock-upgrade-0.28.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-subunit* to *1.4.2*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-subunit-upgrade-1.4.1-1.4.2.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 *ruby* to *3.1.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-ruby-upgrade-3.1.2-3.1.3.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-mako* to *1.2.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-mako-upgrade-1.2.3-1.2.4.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 *tcl* to *8.6.13* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe tcl failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bit
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *acpica* to *20221022* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade acpica -V 20221022
NOTE: Starting bitbake server...
NOT
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-gitdb* to *4.0.10*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-gitdb-upgrade-4.0.9-4.0.10.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-importlib-metadata*
to *5.1.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-importlib-metadata-upgrade-5.0.0-5.1.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-cryptography-vectors*
to *38.0.4* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-cryptography-vectors-upgrade-38.0.3-38.0.4.patch
- check the cha
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *btrfs-tools* to *6.0.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.0.1-6.0.2.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools* to
*65.6.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-upgrade-65.5.1-65.6.3.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-pycryptodomex* to
*3.16.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pycryptodomex-upgrade-3.15.0-3.16.0.patch
- check the changes to upstre
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-numpy* to *1.24.0*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-numpy -V 1.24.0
NOTE: Starting bitbake ser
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-zipp* to *3.11.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-zipp-upgrade-3.10.0-3.11.0.patch
- check the changes to upstream patches and summ
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202211*
has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
0001-ovmf-upgrade-edk2-stable202208
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-poetry-core* to
*1.4.0* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-poetry-core -V 1.4.0
NOTE: Starting b
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hypothesis* to
*6.58.2* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.57.1-6.58.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-pycryptodome* to
*3.16.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pycryptodome-upgrade-3.15.0-3.16.0.patch
- check the changes to upstream
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd* to *252.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*f992bcc08219edb283d2ab31dd3871a4a0e8220e* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
f992
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ccache* to *4.7.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-ccache-upgrade-4.7.2-4.7.4.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 *cmake* to *3.25.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.24.2-3.25.1.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *patchelf* to *0.17.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-patchelf-upgrade-0.16.1-0.17.0.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *meson* to *0.64.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-0.64.0-0.64.1.patch
- check the changes to upstream patches and summarize them in
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxcrypt-compat* to *4.4.33*
has Succeeded.
Next steps:
- apply the patch: git am 0001-libxcrypt-compat-upgrade-4.4.30-4.4.33.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 *dropbear* to *2022.83* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dropbear-upgrade-2022.82-2022.83.patch
- check the changes to upstream patches and summarize
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *15.0.6* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: finish -f llvm
/home/pokybuild/yocto-worker/auh/build/build/poky/m
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *systemd-boot* to *252.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe systemd-boot failed.
NOTE: Starting bitbake server...
NOTE: Re
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *glib-2.0* to *2.74.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-glib-2.0-upgrade-2.74.1-2.74.2.patch
- check the changes to upstream patches and summarize th
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *pciutils* to *3.9.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pciutils-upgrade-3.8.0-3.9.0.patch
- check the changes to upstream patches and summarize them
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bind* to *9.18.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-bind-upgrade-9.18.8-9.18.9.patch
- check the changes to upstream patches and summarize them in th
From: Mike Crowe
In 526bdd88ccd758204452579333ba188e29270bde the imageType loop in
kernel_do_deploy was changed to use KERNEL_IMAGETYPE_FOR_MAKE rather
than KERNEL_IMAGETYPES. This broke the special handling for fitImage
immediately below because KERNEL_IMAGETYPE_FOR_MAKE never contains
fitImage.
From: Chen Qi
Currently, the KERNEL_DEBUG_TIMESTAMPS is not working as expected
at rebuild. That is, even if we set it to "1", the kernel build time
is not changed. The problem could be reproduced by the following steps.
1. bitbake core-image-minimal; start image and check `uname -a` output.
From: Wang Mingyu
Signed-off-by: Wang Mingyu
Signed-off-by: Alexandre Belloni
(cherry picked from commit 7e12fa1e6250fc358ba159a6b626458d871f7ccf)
Signed-off-by: Steve Sakoman
---
.../mobile-broadband-provider-info_git.bb | 4 ++--
1 file changed, 2 insertions(+), 2 deleti
From: Dmitry Baryshkov
License-Update: additional files
Signed-off-by: Dmitry Baryshkov
Signed-off-by: Alexandre Belloni
(cherry picked from commit 6940f297243a66bd58d6adee7d690bcee9b9ccb2)
Signed-off-by: Steve Sakoman
---
...{linux-firmware_20221012.bb => linux-firmware_20221109.bb} | 4 ++--
From: Alexander Kanavin
License-Update: copyright years, additional firmwares
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit 9f658c724b6635e5745f30b25601bcc51a004be4)
Signed-off-by: Steve Sakoman
---
...inux-firmware_20220913.bb => linux-firmware
From: Vivek Kumbhar
Upstream-Status: Backport
[https://gitlab.com/qemu-project/qemu/-/commit/1ab95af033a419e7a64e2d58e67dd96b20af5233]
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2021-20196.patch
From: Ross Burton
(From OE-Core rev: 1d2e131d9ba55626354264d454b2808e84751600)
Signed-off-by: Ross Burton
Signed-off-by: Steve Sakoman
(cherry picked from commit 23df4760ebc153c484d467e51b414910c570a6f8)
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
(cherry picked from commit 37
Please review this set of patches for dunfell and have comments back by
end of day Monday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4565
The following changes since commit 408bf1b4bb4f4ed126c17fb3676f9fa0513065ba:
sstate: Account for rese
1 - 100 of 170 matches
Mail list logo
