The database update has been done on the original file. In case of
network connection issues, temporary outage of the NVD server or
a similar situation, the function could exit with incomplete data
in the database. This patch solves the issue by performing the update
on a copy of the database. It
Move cleanup of the database after a failed download to a separate
function. This will be useful when we have more actions to do in
that situation.
Signed-off-by: Marta Rybczynska
---
meta/recipes-core/meta/cve-update-db-native.bb | 17 ++---
1 file changed, 10 insertions(+), 7
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vte* to *0.70.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-vte-upgrade-0.70.1-0.70.2.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 *piglit* to
*e300648a805d62101de341232d99bfec1cce78c5* has Succeeded.
Next steps:
- apply the patch: git am 0001-piglit-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 *linux-firmware* to *20221214*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20221109-20221214.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 *puzzles* to
*14c025d192579961d1ade51f2a322bd765aef0e5* has Succeeded.
Next steps:
- apply the patch: git am 0001-puzzles-upgrade-to-latest-revision.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libva-utils* to *2.17.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libva-utils failed.
NOTE: Starting bitbake server...
WARNING:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lsof* to *4.96.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lsof-upgrade-4.96.4-4.96.5.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 *pango* to *1.50.12* has
Succeeded.
Next steps:
- apply the patch: git am 0001-pango-upgrade-1.50.11-1.50.12.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 *libksba* to *1.6.3* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libksba failed.
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnupg* to *2.4.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gnupg failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsolv* to *0.7.23* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsolv-upgrade-0.7.22-0.7.23.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 *ethtool* to *6.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-ethtool-upgrade-6.0-6.1.patch
- check
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
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpsl* to *0.21.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libpsl-upgrade-0.21.1-0.21.2.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 *libsdl2* to *2.26.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsdl2-upgrade-2.26.0-2.26.1.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 *logrotate* to *3.21.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-logrotate-upgrade-3.20.1-3.21.0.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 *xwayland* to *22.1.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xwayland-upgrade-22.1.5-22.1.7.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 *xcb-util* to *0.4.1* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade xcb-util -V 0.4.1
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tiff* to *4.5.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe tiff failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xserver-xorg* to *21.1.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xserver-xorg-upgrade-21.1.4-21.1.6.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 *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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kexec-tools* to *2.0.26* has
Succeeded.
Next steps:
- apply the patch: git am 0001-kexec-tools-upgrade-2.0.25-2.0.26.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 *strace* to *6.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-strace-upgrade-6.0-6.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 *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
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...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gcr3* to *4.0.0* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade gcr3 -V 4.0.0
NOTE: Starting bitbake server...
NOTE:
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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pyrsistent* to
*0.19.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pyrsistent-upgrade-0.19.2-0.19.3.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 *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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.36* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gtk+3 -V 3.24.36
NOTE: Starting bitbake server...
NOTE:
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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *man-pages* to *6.02* has
Succeeded.
Next steps:
- apply the patch: git am 0001-man-pages-upgrade-6.01-6.02.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-numpy* to *1.24.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-numpy-upgrade-1.23.4-1.24.1.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 *repo* to *2.31* has Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.29.9-2.31.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 *python3-pathspec* to *0.10.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pathspec-upgrade-0.10.1-0.10.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 *python3-importlib-metadata*
to *5.2.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-importlib-metadata-upgrade-5.0.0-5.2.0.patch
- check the changes
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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-hatch-vcs* to *0.3.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatch-vcs-upgrade-0.2.0-0.3.0.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 *python3-pytz* to *2022.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pytz-upgrade-2022.6-2022.7.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 *python3-setuptools-scm* to
*7.1.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-scm-upgrade-7.0.5-7.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-jsonschema* to
*4.17.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-jsonschema-upgrade-4.17.0-4.17.3.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 *python3-hypothesis* to
*6.61.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.57.1-6.61.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 *python3-lxml* to *4.9.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-lxml-upgrade-4.9.1-4.9.2.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 *python3-certifi* to
*2022.12.7* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-certifi-upgrade-2022.9.24-2022.12.7.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 *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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-attrs* to *22.2.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-attrs-upgrade-22.1.0-22.2.0.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 *python3-hatchling* to
*1.12.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-hatchling-upgrade-1.11.1-1.12.1.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 *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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-dtschema* to
*2022.12* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-dtschema-upgrade-2022.11-2022.12.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 *python3-pycairo* to *1.23.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pycairo-upgrade-1.21.0-1.23.0.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 *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
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
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *jquery* to *3.6.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-jquery-upgrade-3.6.2-3.6.3.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *nasm* to *2.16.01* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe nasm failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-git* to *3.1.30* has
Succeeded.
Next steps:
- apply the patch: git am 0001-python3-git-upgrade-3.1.29-3.1.30.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 *librepo* to *1.15.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-librepo-upgrade-1.14.5-1.15.1.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 *meson* to *1.0.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-0.64.0-1.0.0.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 *libpcap* to *1.10.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libpcap-upgrade-1.10.1-1.10.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 *btrfs-tools* to *6.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-btrfs-tools-upgrade-6.0.2-6.1.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 *libtest-fatal-perl* to
*0.017* has Succeeded.
Next steps:
- apply the patch: git am 0001-libtest-fatal-perl-upgrade-0.016-0.017.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 *file* to *5.44* has Succeeded.
Next steps:
- apply the patch: git am 0001-file-upgrade-5.43-5.44.patch
- check the changes to upstream patches and summarize them in the
glibc got an official C.UTF-8 in 2.35, but we don't appear to install
it by default... if I add "c" to IMAGE_LINGUAS then it gets installed,
but it feels like this ought to be default? Or even stronger and have
it separate from IMAGE_LINGUAS so even if that's set to "" you still
get it?
I tripped
From: Jagadeesh Krishnanjanappa
The QB_DEFAULT_KERNEL is set to pick bundled initramfs kernel image
if the Linux kernel image is generated with INITRAMFS_IMAGE_BUNDLE="1".
This makes runqemu to automatically pick bundled initramfs kernel image
instead of explicitly mentioning bundled initramfs
From: Robert Andersson
By default GOCACHE is set to $HOME/.cache.
Same issue for all other go recipes had been fixed by commit 9a6d208b:
[ go: avoid host contamination by GOCACHE ]
but that commit missed go-crosssdk recipe.
Signed-off-by: Robert Andersson
Signed-off-by: Ming Liu
From: Peter Marko
Commit 0533edac277080e1bd130c14df0cbac61ba01a0c broke
bitbake parsing when bitbake is executed from directory with existing
.gitmodules
and the recipe in externalsrc does not have .gitmodules
The check needs to search for .gitmodules in sources path, not cwd.
iParsing
From: Ross Burton
The /proc/pressure support in buildstats is creating directories in the
buildstats tree called reduced_proc_pressure, which confuses the parsing
logic as that cannot be parsed as a name-epoc-version-revision tuple.
Explicitly skip this directory to solve the problem.
From: Chen Qi
bc is needed for compiling kernel modules, more specifially
whenr running `make scripts prepare'.
In linux-yocto.inc, we have bc-native in DEPENDS. But we will
need nativesdk-bc in case we compile a kernel module inside
SDK.
Signed-off-by: Chen Qi
Signed-off-by: Alexandre
From: Joshua Watt
Make the license more accurate by specifying the specific variant of BSD
license instead of the generic one. This helps with SPDX license
attribution as "BSD" is not a valid SPDX license.
(From OE-Core rev: ff27ea21d7c14086335da5c3e2fac353e44438da)
Signed-off-by: Joshua Watt
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
851c2b5fb793 Linux 5.4.228
ff484a9ba449 ASoC: ops: Correct bounds check for second channel on SX
controls
7d4aa0929963 can: mcba_usb: Fix termination command argument
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit 2394a481db1b41ad4581e22ba901ac76fa7b3dcd)
Signed-off-by: Steve Sakoman
---
meta/recipes-extended/timezone/timezone.inc | 7 +++
1 file changed, 3 insertions(+), 4
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
4d2a309b5c28 Linux 5.4.225
b612f924f296 ntfs: check overflow when iterating ATTR_RECORDs
0e2ce0954b39 ntfs: fix out-of-bounds read in ntfs_attr_find()
266bd5306286 ntfs: fix
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
771a8acbb841 Linux 5.4.224
3e0c1ab197eb ipc: remove memcg accounting for sops objects in
do_semtimedop()
a16415c8f156 wifi: brcmfmac: Fix potential buffer overflow in
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
b70bfeb98635 Linux 5.4.221
6bb8769326c4 mm: /proc/pid/smaps_rollup: fix no vma's null-deref
a351077e589d hv_netvsc: Fix race between VF offering and VF association
message from
From: Minjae Kim
Avoid out-of-range access to packet buffer
Upstream-Status:
Backport[https://github.com/ppp-project/ppp/commit/a75fb7b198eed50d769c80c36629f38346882cbf]
Signed-off-by:Minjae Kim
Signed-off-by: Steve Sakoman
---
.../ppp/ppp/CVE-2022-4603.patch | 50
From: Quentin Schulz
Upstream went with something slightly different so let's update the
patch so we don't have to carry a patch that isn't going to be merged.
This patch is part of snapshot 1.17.6.
Cc: Quentin Schulz
Signed-off-by: Quentin Schulz
Signed-off-by: Richard Purdie
(cherry
From: Vivek Kumbhar
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/qemu/qemu.inc | 1 +
.../qemu/qemu/CVE-2021-3507.patch | 87 +++
2 files changed, 88 insertions(+)
create mode 100644
From: Vivek Kumbhar
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
.../xorg-lib/libx11/CVE-2022-3555.patch | 38 +++
.../recipes-graphics/xorg-lib/libx11_1.6.9.bb | 1 +
2 files changed, 39 insertions(+)
create mode 100644
From: Vivek Kumbhar
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
.../rsync/files/CVE-2022-29154.patch | 334 ++
meta/recipes-devtools/rsync/rsync_3.1.3.bb| 1 +
2 files changed, 335 insertions(+)
create mode 100644
From: Vivek Kumbhar
Signed-off-by: Vivek Kumbhar
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/go/go-1.14.inc | 1 +
.../go/go-1.14/CVE-2022-41717.patch | 75 +++
2 files changed, 76 insertions(+)
create mode 100644
From: Hitendra Prajapati
Upstream-Status: Backport from
https://git.savannah.gnu.org/cgit/grub.git/commit/?id=6fe755c5c07bb386fda58306bfd19e4a1c974c53
Signed-off-by: Hitendra Prajapati
Signed-off-by: Steve Sakoman
---
.../grub/files/CVE-2022-28735.patch | 271 ++
Please review this set of patches for dunfell and have comments back by
end of day Tuesday.
Passed a-full on autobuilder:
https://autobuilder.yoctoproject.org/typhoon/#/builders/83/builds/4715
The following changes since commit cc8ec63310f9a936371ea1070cb257c926808755:
oeqa/selftest/tinfoil:
From: Richard Purdie
When running oe-selftest and seeing the end of a running log, it is
extremely helpful to know if there have been failures or not to save
looking at the rest of the log. Add the number of failures to the summary
line so that people monitoring builds have an easier time before
From: Randy MacLeod
This test is failing on the arm workers only so skip there until the issue
can be worked on and resolved. The bug #14311 will remain open for tracking.
Signed-off-by: Randy MacLeod
Signed-off-by: Richard Purdie
(cherry picked from commit
From: Jagadeesh Krishnanjanappa
The QB_DEFAULT_KERNEL is set to pick bundled initramfs kernel image
if the Linux kernel image is generated with INITRAMFS_IMAGE_BUNDLE="1".
This makes runqemu to automatically pick bundled initramfs kernel image
instead of explicitly mentioning bundled initramfs
From: Alexander Kanavin
'devtool modify' writes additional settings to workspace .bbappend so that this
can be handled correctly, but 'devtool upgrade' does not. This adds the missing
settings.
In particular, local files should not anymore mysteriously disappear from
SRC_URIs on upgrades.
From: Ovidiu Panait
Currently, allyesconfig test runs for x86_64 fail with:
ERROR: linux-yocto-5.19.17+gitAUTOINC+0cba9aa404_aaf4490d18-r0 do_package:
QA Issue: linux-yocto: Files/directories were installed but not shipped in any
package:
/lib/modules/5.19.17/kernel/drivers/nvdimm
With
From: Martin Jansa
* switch from tar.gz to tar, because the tar.gz archives upstream are regular
tar as well now
https://www.w3.org/XML/Test/ still has 3 separate URLs for .zip, .tar
and .tar.gz, but both tar links return the same file:
xmlts20080827.tar: POSIX tar archive (GNU)
From: Joshua Watt
Adds an option to make the SPDX more human-readable (at the expense of a
larger files)
Signed-off-by: Joshua Watt
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
(cherry picked from commit 4799594b26f77ed259dc661bf077519b338390c8)
Signed-off-by: Steve Sakoman
From: Ross Burton
This patch was upstreamed in 6b09a8bc, 1.5.5 onwards.
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
(cherry picked from commit 99b6e1ecb18d595e7b66344de882c1e1db6f35c3)
Signed-off-by: Steve Sakoman
---
...atch_common.h-define-also-EGL_NO_X11.patch | 27
From: Robert Andersson
By default GOCACHE is set to $HOME/.cache.
Same issue for all other go recipes had been fixed by commit 9a6d208b:
[ go: avoid host contamination by GOCACHE ]
but that commit missed go-crosssdk recipe.
Signed-off-by: Robert Andersson
Signed-off-by: Ming Liu
From: Alejandro Hernandez Samaniego
Since qemuboot is part of IMAGE_CLASSES via qemu.inc it is being
inherited before we set the QB_FOO variables.
Since our variables have conditional definitions and at that point
they've already been defined by qemuboot, we can no longer define
them in our
From: Xiangyu Chen
It appears that rngd is not needed as of linux-5.6 and later[1]
and should not be installed by default since the purpose of rngd
is to provide additional trusted sources of entropy.
We did some testing on real hardware, the result seems to support that
we no longer need rngd
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit 402254a5f841520b132508c21465111d33b6eb1a)
Signed-off-by: Steve Sakoman
---
...001-Remove-dependency-on-libcapstone.patch | 36 ---
.../ruby/{ruby_3.1.2.bb =>
From: Wang Mingyu
Changelog:
===
systemclock waiting fixes for certain 32-bit platforms/libcs
alphacombine: robustness improvements for corner case scenarios
avfvideosrc: Report latency when doing screen capture
d3d11videosink: various thread-safety and stability fixes
decklink: fix
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit 2394a481db1b41ad4581e22ba901ac76fa7b3dcd)
Signed-off-by: Steve Sakoman
---
meta/recipes-extended/timezone/timezone.inc | 7 +++
1 file changed, 3 insertions(+), 4
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit d88ff809b2e78ee49d5da42bb08ff5244e6101af)
Signed-off-by: Steve Sakoman
---
meta/recipes-devtools/ruby/ruby.inc | 39
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Alexandre Belloni
(cherry picked from commit ff12622451f1f8580f928c6771cd82daa632071c)
Signed-off-by: Steve Sakoman
---
.../0001-detect-gold-as-GNU-linker-too.patch | 14 -
From: Wang Mingyu
Changelog:
==
* Changed the error handler of oversized chunks (i.e. larger than
PNG_USER_CHUNK_MALLOC_MAX) from png_chunk_error to png_benign_error.
* Fixed a buffer overflow error in contrib/tools/pngfix.
* Fixed a memory leak (CVE-2019-6129) in
From: Bruce Ashfield
Updating to the latest korg -stable release that comprises
the following commits:
a2428a8dcb4f Linux 5.10.160
54c15f67cb72 ASoC: ops: Correct bounds check for second channel on SX
controls
74b139c63f07 nvme-pci: clear the prp2 field when not used
1 - 100 of 117 matches
Mail list logo
