Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnutls* to *3.7.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gnutls-upgrade-3.7.1-3.7.2.patch
- check the changes to upstream patches and summarize them in t
Recipe upgrade statistics:
* Failed (devtool error): 10
ovmf, edk2-stable202105, Ricardo Neri
util-linux-libuuid, 2.37, Chen Qi
util-linux, 2.37, Chen Qi
elfutils, 0.185, Zang Ruochen
gnu-config, 20210522-new-commits-available, Robert Yang
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *176* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-175-176.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 *puzzles* to
*8f3413c31ffd43c4ebde40894ac1b2f7cdf222c3* has Succeeded.
Next steps:
- apply the patch: git am 0001-puzzles-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 *libcap* to *2.50* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libcap 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 *alsa-utils* to *1.2.5* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-alsa-utils-upgrade-1.2.4-1.2.5.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *less* to *589* has Succeeded.
Next steps:
- apply the patch: git am 0001-less-upgrade-586-589.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 *alsa-ucm-conf* to *1.2.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-alsa-ucm-conf-upgrade-1.2.4-1.2.5.patch
- check the changes to upstream patches and summa
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *alsa-topology-conf* to
*1.2.5* has Succeeded.
Next steps:
- apply the patch: git am 0001-alsa-topology-conf-upgrade-1.2.4-1.2.5.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 *adwaita-icon-theme* to
*40.1.1* has Failed(other errors).
Detailed error information:
Failed(unknown error)
Traceback (most recent call last):
File
"/home/pokybuild/yocto-worker
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libinput* to *1.18.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libinput-upgrade-1.17.3-1.18.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 *python3-importlib-metadata*
to *4.4.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-importlib-metadata-upgrade-4.3.0-4.4.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-magic* to *0.4.23*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-magic-upgrade-0.4.22-0.4.23.patch
- check the changes to upstream patches and su
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-helloworld* to
*09c3a5e06b5dbcbe35b7c0861f91088f47c02ac4* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade go-helloworld -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-samples* to
*b7e55e8fcfa9fd4a8f395360873e7bbafa3705e5* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-samples
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-libarchive-c* to
*3.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-libarchive-c-upgrade-3.0-3.1.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-hypothesis* to
*6.13.11* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.13.7-6.13.11.patch
- check the changes to upstream p
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *perl* to *5.34.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe perl 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 *util-linux-libuuid* to *2.37*
has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe util-linux-libuuid failed.
NOTE: Starting bitbake server.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *erofs-utils* to *20191016*
has Succeeded.
Next steps:
- apply the patch: git am 0001-erofs-utils-upgrade-1.2.1-20191016.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 *mtools* to *4.0.29* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mtools-upgrade-4.0.27-4.0.29.patch
- check the changes to upstream patches and summarize them i
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnu-config* to
*4550d2f15b3a7ce2451c1f29500b9339430c877f* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gnu-config -S
4550
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cmake* to *3.20.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cmake-upgrade-3.20.2-3.20.3.patch
- c
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *elfutils* to *0.185* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe elfutils 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 *m4* to *1.4.19* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe m4 failed.
NOTE: Starting bitbake server...
NOTE: Reconnecting to bitba
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ovmf* to *edk2-stable202105*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade ovmf -V edk2-stable202105 -S
e1999b264f1f9d7230
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *util-linux* to *2.37* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe util-linux failed.
NOTE: Starting bitbake server...
NOTE: Reconne
Thanks Alistair
All three patches look good in my testing on beaglev
Acked-by: Khem Raj
On Wed, Jun 2, 2021 at 4:21 PM Alistair Francis
wrote:
>
> Disable FW_PIC to fix the error message:
>
> opensbi-0.9-r0 do_package_qa: QA Issue: File
> /share/opensbi/lp64/generic/firmware/fw_jump.elf in pa
Signed-off-by: Alistair Francis
---
meta/classes/uboot-config.bbclass | 4
meta/recipes-bsp/u-boot/u-boot.inc | 7 ++-
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/meta/classes/uboot-config.bbclass
b/meta/classes/uboot-config.bbclass
index 3bba02828b..6444f58437 10064
Signed-off-by: Alistair Francis
---
meta/recipes-bsp/opensbi/opensbi-payloads.inc | 15 ++-
meta/recipes-bsp/opensbi/opensbi_0.9.bb | 1 +
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/meta/recipes-bsp/opensbi/opensbi-payloads.inc
b/meta/recipes-bsp/opensbi/op
Disable FW_PIC to fix the error message:
opensbi-0.9-r0 do_package_qa: QA Issue: File
/share/opensbi/lp64/generic/firmware/fw_jump.elf in package opensbi doesn't
have GNU_HASH (didn't pass LDFLAGS?)
This is seen in newer versions of OpenSBI that enable FW_PIC by default.
Signed-off-by: Alistai
On Wed, 2021-06-02 at 16:34 +0200, Michael Opdenacker wrote:
> Hi Richard,
>
> On 6/2/21 3:27 PM, Richard Purdie wrote:
> > --- a/meta/recipes-core/expat/expat_2.2.10.bb
> > +++ b/meta/recipes-core/expat/expat_2.2.10.bb
> > @@ -25,3 +25,5 @@ do_install_ptest_class-target() {
> > }
> >
> >
> >
During today's release three tags (2020-04.8-dunfell, 2020-04.8, and
yocto-3.1.8) were made against the HEAD of the master branch instead of the
correct commit on the dunfell branch. The incorrect tags have been deleted and
replaced with the correct tags. A git force pull may be required to brin
Hello,
I've been seeing some errors in first boot of devices, based on
dunfell, where the ldconfig.service fails as:
... ldconfig[138]: /sbin/ldconfig: Renaming of /etc/ld.so.cache~ to
/etc/ld.so.cache failed: No such file or directory
... systemd[1]: ldconfig.service: Main process exited, code=e
On 6/2/21 8:32 AM, Jacob Kroon via lists.openembedded.org wrote:
Hi,
I'm using Fedora 34 and OE-Core/Bitbake/layers from git master as of
today, with reproducible builds. Sometimes when rebuilding my image I
see sudden changes in file permissions (jumping back and forth) in the
buildhistory o
Hi Richard,
On 6/2/21 3:27 PM, Richard Purdie wrote:
> --- a/meta/recipes-core/expat/expat_2.2.10.bb
> +++ b/meta/recipes-core/expat/expat_2.2.10.bb
> @@ -25,3 +25,5 @@ do_install_ptest_class-target() {
> }
>
> BBCLASSEXTEND += "native nativesdk"
> +
> +CVE_PRODUCT = "expat libexpat"
Oops, t
From: Nikolay Papenkov
License-Update: Corrected license information
flex package is under two licenses:
- "BSD-3-Clause" is provided in top-level COPYING file; the license
actually include third obligation (without the actual "3" numbering)
- "LGPL-2.0+" is explained by src/gettext.h
Signed-
From: Ross Burton
By default RPM uses the number of cores as the number of threads to use,
which can result in quite antisocial memory usage.
As we control the macros for compression anyway, we can pass XZ_THREADS
to limit the number of threads if needed.
Signed-off-by: Ross Burton
Signed-off-
This test is flawed since multiple parts of the system can write to the log
and we obtain different numbers of log messages depending on factors we
can't control.
Drop the log testing component of the test.
[YOCTO #12465]
Signed-off-by: Richard Purdie
---
meta/lib/oeqa/runtime/cases/rpm.py | 9
From: Steve Sakoman
Upstream database uses both "expat" and "libexpat" to report CVEs
Signed-off-by: Steve Sakoman
Signed-off-by: Richard Purdie
---
meta/recipes-core/expat/expat_2.2.10.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/expat/expat_2.2.10.bb
b/meta/re
From: Changqing Li
The git repo for pkg-config was changed, so update the
SRC_URI accordingly with the new link.
Signed-off-by: Changqing Li
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/pkgconfig/pkgconfig_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/m
Add a new lttng file to one of the tests to avoid test failures.
Also add a dependency on grep since standalone testing revealed test
failures without this. Normally this was added by other dependencies
in the ptest images so we didn't see this.
Signed-off-by: Richard Purdie
---
.../{lttng-tool
From: Trevor Gamblin
Backport and modify the patch for CVE-2021-22890 from curl 7.76 to make
it apply cleanly on 7.75.
CVE: CVE-2021-22890
Signed-off-by: Trevor Gamblin
Signed-off-by: Richard Purdie
---
...-argument-to-Curl_ssl_get-addsession.patch | 517 ++
meta/recipes-supp
From: Trevor Gamblin
Backport and modify the patch for CVE-2021-22876 from curl 7.76 to
make it apply cleanly on 7.75.
CVE: CVE-2021-22876
Signed-off-by: Trevor Gamblin
Signed-off-by: Richard Purdie
---
...redentials-from-the-auto-referer-hea.patch | 152 ++
meta/recipes-supp
From: Sakib Sajal
CVE's affect ESP (NCR53C90) part of chip STP2000 (Master I/O).
On Sparc32 it is the NCR89C100 part of the chip.
On Macintosh Quadra it is NCR53C96.
Both are not supported by yocto.
Signed-off-by: Sakib Sajal
Signed-off-by: Richard Purdie
---
meta/recipes-devtools/qemu/qemu.i
Signed-off-by: Richard Purdie
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
.../bind-ensure-searching-for-json-headers-searches-sysr.patch | 0
.../bind/{bind-9.16.13 => bind-9.16.15}/bind9
From: Trevor Gamblin
Signed-off-by: Trevor Gamblin
Signed-off-by: Richard Purdie
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
.../bind-ensure-searching-for-json-headers-searches-sysr.patch | 0
..
We use the SUSE mirror of xinetd. The CVE fix was added to the main repo
after the latest release but is included in the version from the SUSE repo.
Signed-off-by: Richard Purdie
---
meta/recipes-extended/xinetd/xinetd_2.3.15.4.bb | 3 +++
1 file changed, 3 insertions(+)
diff --git a/meta/recip
From: Alexander Kanavin
Signed-off-by: Alexander Kanavin
Signed-off-by: Richard Purdie
---
.../0001-avoid-start-failure-with-bind-user.patch | 0
.../0001-named-lwresd-V-and-start-log-hide-build-options.patch | 0
.../bind-ensure-searching-for-json-headers-searches-sysr.patch |
49 matches
Mail list logo
