On Fri, 2024-03-15 at 11:05 +0800, leimaohui via lists.openembedded.org
wrote:
> From: Lei Maohui
>
> - Fix conflict of finclude/math-vector-fortran.h error when enable
> multilib on
> aarch64.
> - Because multilib header doesn't work well for fortran compiler, a
> compile
> error will occur
On 3 Mar 2024, at 17:53, Dhairya Nagodra via lists.openembedded.org
wrote:
>
> From: Dhairya Nagodra
>
> - There are times when exluding a package that inherits a particular
> class/classes may be desired.
> - This provides the framework for that via the variable:
>
On Fri, Mar 15, 2024 at 7:37 AM Ross Burton wrote:
>
> From: Ross Burton
>
> There's no need to run the output of runtests.pl through a sed to get
> automake-style output, as you can pass -am to get this formatting.
>
> Don't run timing dependent tests, as the ptests can run on loaded
> systems.
Hello,
with ubuntu-20.04 based builders I get problems like
| DEBUG: Executing shell function do_image_tar
| tar: ./home/.../.bashrc: Unknown file type; file ignored
| tar: Exiting with failure status due to previous errors
| WARNING: exit code 1 from a shell command.
| NOTE: recipe
Includes a fix for CVE-2024-28757.
Signed-off-by: Richard Purdie
---
meta/recipes-core/expat/{expat_2.6.1.bb => expat_2.6.2.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-core/expat/{expat_2.6.1.bb => expat_2.6.2.bb} (92%)
diff --git
With newer glibc versions, pthread was merged into the main library so there is
no longer any need to link with -lpthread. On newer systems this means that
linker
flag is dropped from places like pkgconfig .pc files. If uninative then uses
this
newer library on an older system, the flag is
From: Ross Burton
The install task uses a recursive find to check that it can only find
one wheel, but then does a non-recursive glob to install. This can
lead to false-failures if PEP517_WHEEL_PATH points at a directory with
subdirectories.
Solve this mismatch by making the find non-recusive.
From: Ross Burton
There's no need to explicitly set PYPI_ARCHIVE_NAME and S when
PYPI_PACKAGE is set correctly.
Signed-off-by: Ross Burton
---
.../python/python3-jsonschema-specifications_2023.12.1.bb | 6 ++
meta/recipes-devtools/python/python3-poetry-core_1.9.0.bb | 4 ++--
From: Ross Burton
This variable is only used when constructing a SRC_URI and some recipes
think that it's the correct value to assign if the PyPi package name
isn't the same as the recipe name, when PYPI_PACKAGE is actually all
that needs to be set.
Also document the variables we expect the
From: Ross Burton
There's no need to run the output of runtests.pl through a sed to get
automake-style output, as you can pass -am to get this formatting.
Don't run timing dependent tests, as the ptests can run on loaded
systems.
Add a dependency on the en_US locale because some of the tests
From: Ross Burton
We often see multiple curl tests fail during ptest runs, the actual test
varies but the output is like this:
FAIL: 337: protoc!
There was no content at all in the file log/3/server.input.
Server glitch? Total curl failure? Returned: 28
Error code 28 is
From: Ross Burton
First, libcheck has the ability to increase all test timeouts by an arbitrary
multiplier. Because we run our tests on loaded build machines,
increase all timeouts by 10x to reduce the chance of load causing failures.
Second, use GST_CHECKS_IGNORE to list test cases that should
On 7 Mar 2024, at 20:08, Emil Kronborg via lists.openembedded.org
wrote:
>
> Socket activation is prone to DoS (denial of service) because too many
> connections will permanently deactivate sshd.socket [1]. Also, since
> socket units do not allow setting Restart, accepting new connections can
>
Fails at build time:
ERROR: expat-2.2.9-r0 do_patch: Applying patch 'CVE-2024-28757.patch'
on target directory
'/home/steve/builds/poky-contrib-dunfell/build/tmp/work/core2-64-poky-linux/expat/2.2.9-r0/git/expat'
Command Error: 'quilt --quiltrc
On Fri, Mar 15, 2024 at 7:29 AM Richard Purdie
wrote:
>
> With newer glibc versions, pthread was merged into the main library so there
> is
> no longer any need to link with -lpthread. On newer systems this means that
> linker
> flag is dropped from places like pkgconfig .pc files. If uninative
Greetings,
If you contributed new features to the upcoming release, or if you are
interested in figuring out what's new in 5.0, that would be great if you
could help us by submitting bits of release notes about them too.
If you are familiar with the Sphinx / ReStructured Text format, you can
From: Soumya Sambu
Upgrade to latest 1.22.x release [1]:
$git log --oneline go1.22.0..go1.22.1
db6097f8cb (tag: go1.22.1, origin/release-branch.go1.22)
[release-branch.go1.22] go1.22.1
041a47712e [release-branch.go1.22] net/textproto, mime/multipart: avoid
unbounded read in MIME header
From: Mingli Yu
Add --system parameter for useradd to avoid intruducing .bashrc
and .profile under home dir to fix the below error.
$ bitbake core-image-weston
| DEBUG: Executing python function set_image_size
| DEBUG: 352679.60 = 271292 * 1.30
| DEBUG: 455079.60 =
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *waffle* to *1.8.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe waffle failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *texinfo* to *7.1* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade texinfo -V 7.1
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *shadow* to *4.15.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-shadow-upgrade-4.14.2-4.15.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *stress-ng* to *0.17.06* has
Succeeded.
Next steps:
- apply the patch: git am 0001-stress-ng-upgrade-0.17.05-0.17.06.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 *gtk4* to *4.14.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-gtk4-upgrade-4.12.5-4.14.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-libav* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk-doc* to *1.34.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gtk-doc-upgrade-1.33.2-1.34.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 *kmod* to *32* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-kmod-upgrade-31-32.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libsdl2* to *2.30.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsdl2-upgrade-2.30.0-2.30.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 *shaderc* to *2024.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-shaderc-upgrade-2023.8-2024.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 *vulkan-samples* to
*0d0cf9b90541d349ceb49682d063d27a8c2432de* 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 *npth* to *1.7* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe npth failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *icu* to *74-2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-icu-upgrade-74-1-74-2.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.21.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libva-utils -V 2.21.0 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20240312*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20240220-20240312.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 *libtraceevent* to *1.8.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libtraceevent failed.
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*537831d483f987d49b9d1b45fd50d9cab005d46a* 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 *librsvg* to *2.57.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-librsvg-upgrade-2.57.1-2.57.2.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-bad* to
*1.24.0* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gstreamer1.0-plugins-bad failed.
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mkfontscale* to *1.2.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mkfontscale-upgrade-1.2.2-1.2.3.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 *encodings* to *1.1.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-encodings-upgrade-1.0.7-1.1.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 *xauth* to *1.1.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xauth-upgrade-1.1.2-1.1.3.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 *mesa* to *24.0.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-mesa-upgrade-24.0.2-24.0.3.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 *gstreamer1.0-plugins-ugly* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xev* to *1.2.6* has Succeeded.
Next steps:
- apply the patch: git am 0001-xev-upgrade-1.2.5-1.2.6.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 *gstreamer1.0-rtsp-server* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-good* to
*1.24.0* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade gstreamer1.0-plugins-good -V
1.24.0
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-python* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-runtime* to *1.22.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mmc-utils* to
*e1281d4de9166b7254ba30bb58f9191fc2c9e7fb* has Succeeded.
Next steps:
- apply the patch: git am 0001-mmc-utils-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-pyopenssl* to
*24.1.0* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pyopenssl-upgrade-24.0.0-24.1.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 *createrepo-c* to *1.1.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-createrepo-c-upgrade-1.0.4-1.1.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 *rpm* to *4.19.1.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rpm failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cargo* to *1.76.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe cargo failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust-llvm* to *1.76.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust-llvm failed.
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *tcl* to *8.6.14* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe tcl failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *dpkg* to *1.22.6* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe dpkg failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ofono* to *2.5* has Succeeded.
Next steps:
- apply the patch: git am 0001-ofono-upgrade-2.4-2.5.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 *meson* to *1.4.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-meson-upgrade-1.3.1-1.4.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 *ovmf* to *edk2-stable202402*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade ovmf -V edk2-stable202402 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *llvm* to *18.1.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-llvm-upgrade-18.1.0-18.1.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 *python3-cython* to *3.0.9*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-cython-upgrade-3.0.8-3.0.9.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 *gptfdisk* to *1.0.10* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gptfdisk failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libcomps* to *0.1.21* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libcomps-upgrade-0.1.20-0.1.21.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-libarchive-c* to
*5.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-libarchive-c-upgrade-5.0-5.1.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-lxml* to *5.1.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-lxml -V 5.1.0
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go* to *1.22.1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-go-upgrade-1.22.0-1.22.1.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-markdown* to *3.6*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-markdown-upgrade-3.5.2-3.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 *python3-pyelftools* to *0.31*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pyelftools-upgrade-0.30-0.31.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 *gst-devtools* to *1.24.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *diffoscope* to *260* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-259-260.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 *gstreamer1.0* to *1.24.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gstreamer1.0 failed.
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-plugins-base* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gnupg* to *2.4.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gnupg-upgrade-2.4.4-2.4.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 *gstreamer1.0-vaapi* to
*1.24.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *debianutils* to *5.17* has
Succeeded.
Next steps:
- apply the patch: git am 0001-debianutils-upgrade-5.16-5.17.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 *libpng* to *1.6.43* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libpng-upgrade-1.6.42-1.6.43.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 *attr* to *2.5.2* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade attr -V 2.5.2
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-trove-classifiers* to
*2024.3.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-trove-classifiers-upgrade-2024.2.23-2024.3.3.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-pygobject* to
*3.48.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pygobject-upgrade-3.46.0-3.48.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 *repo* to *2.44* has Succeeded.
Next steps:
- apply the patch: git am 0001-repo-upgrade-2.42-2.44.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-packaging* to *24.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-packaging-upgrade-23.2-24.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-wheel* to *0.43.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-wheel-upgrade-0.42.0-0.43.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 *libstd-rs* to *1.76.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libstd-rs failed.
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *go-helloworld* to
*32022caedd6a177a7717aa8680cbe179e1045935* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade go-helloworld
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust* to *1.76.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *wget* to *1.24.5* has
Succeeded.
Next steps:
- apply the patch: git am 0001-wget-upgrade-1.21.4-1.24.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 *mdadm* to *4.3* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe mdadm failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *ruby* to *3.3.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe ruby failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libadwaita* to *1.4.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libadwaita-upgrade-1.4.3-1.4.4.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 *gobject-introspection* to
*1.80.0* has Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lighttpd* to *1.4.75* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lighttpd-upgrade-1.4.74-1.4.75.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 *lzip* to *1.24.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lzip-upgrade-1.24-1.24.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 *libpam* to *1.6.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libpam failed.
NOTE: Reconnecting to bitbake server...
Loading
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vala* to *0.56.16* has
Succeeded.
Next steps:
- apply the patch: git am 0001-vala-upgrade-0.56.15-0.56.16.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 *psmisc* to *23.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-psmisc-upgrade-23.6-23.7.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 *libassuan* to *2.5.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libassuan-upgrade-2.5.6-2.5.7.patch
- check the changes to upstream patches and summarize
On 15 Mar 2024, at 08:12, Michael Opdenacker via lists.openembedded.org
wrote:
>
> Greetings,
>
> If you contributed new features to the upcoming release, or if you are
> interested in figuring out what's new in 5.0, that would be great if you
> could help us by submitting bits of release
On Wed, Feb 28, 2024 at 2:39 PM Richard Purdie <
richard.pur...@linuxfoundation.org> wrote:
> The llvm github repo appears to see a lot of churn on branches we're not
> interested in and is in general huge and unreliable to clone.
>
> Switch to shallow clones to improve the user experience.
>
From: Randolph Sapp
Add a link from libbz2.so.1.0 to libbz2.so.${PV} for compatibility with
other distributions.
A handfull of distributions are still using the "Makefile-libbz2_so" to
generate libbz2 and bzip2-shared. This creates a library with a soname
of "libbz2.so.1.0". This library link
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *bluez5* to *5.73* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-bluez5-upgrade-5.72-5.73.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *iproute2* to *6.8.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-iproute2-upgrade-6.7.0-6.8.0.patch
1 - 100 of 106 matches
Mail list logo
