The tzdata.bb by default pulls in all possible timezone data packages which
increases size of the final root filesystem considerably.
The customer would like to have extra timezones configurable so that only
tzdata-core is chosen by default and rest of the zones are optional.
This change would
From: Chen Qi
The DynamicUser needs libnss-systemd to be installed to function
well. The tweaks to nsswitch.conf should be conditional on PACKAGECONFIG
values.
Signed-off-by: Chen Qi
---
meta/recipes-core/systemd/systemd_254.4.bb | 30 +-
1 file changed, 23 insertions(+),
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/5-5-v3-image-add-check_image_max_size-as-post-function-to-check-file-size-against-IMAGE_FILE_MAXSIZE.patch
FAIL:
If defined, this variable value overrides the size of btrfs partition file
created by mkfs.
Otherwise previous logic based on ROOTFS_SIZE variable is used.
It should be set when the final file size would not be above a specific value
due to fixed
partitionning for example.
Signed-off-by:
Trigger an error if the final size is above IMAGE_FILE_MAXSIZE value. Which is
relevant if the
partition size is fixed and the user wants to be sure that the image can be
entirely installed
into its partition.
If the variable is not set, no error is trigger. It works for all filesystems.
If defined, this variable value overrides the size of f2fs partition file
created by mkfs.
Otherwise previous logic based on ROOTFS_SIZE variable is used.
It should be set when the final file size would not be above a specific value
due to fixed
partitionning for example.
Signed-off-by:
If defined, this variable value overrides the size of ext* partition file
created by mkfs.
Otherwise previous logic based on ROOTFS_SIZE variable is used.
It should be set when the final file size would not be above a specific value
due to fixed
partitionning for example.
Signed-off-by:
It returns 0 if the variable is not set for this filesystem.
In case of fixed partitionning where the rootfs partition can't exceed an
amount of bytes, there is currently no automatic and no generic way to have
this requirement met in any case.
Until now, ROOTFS_SIZE value got from
Details are described in the first patch.
Difference from v2:
* Added working and failing tests in
meta/lib/oeqa/selftest/cases/imagefeatures.py
* Split commit to send documentation to right mailing list
Difference from v1:
* Added documentation for IMAGE_FILE_MAXSIZE variable
* Added Python
Rework the script for sending results to use send_raw_email and specify
the 'In-Reply-To' field so that patchtest replies to the emails, rather
than sending them standalone to the submitter and mailing list.
Signed-off-by: Trevor Gamblin
---
Note that this patch is a reworded version of a
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/patchtest-shorten-test-result-outputs.patch
FAIL: test CVE presence in commit message: A CVE tag should be
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
---
Testing patch
/home/patchtest/share/mboxes/patchtest-shorten-test-result-outputs.patch
FAIL: test CVE presence in commit message: A CVE tag should be
On Wed, 1 Nov 2023 at 16:45, wrote:
> I think these differences between SDK and bitbake environment are no
> longer required and they have been problematic. I would try to make the
> bitbake environment usable like the eSDK environment was without trying
> to replicate all the details of the eSDK
On Wed, 2023-11-01 at 16:19 +0100, Alexander Kanavin via
lists.openembedded.org wrote:
> On Wed, 1 Nov 2023 at 15:18, wrote:
> > We are currently experimenting with replacing the eSDK installer
> > with
> > the bitbake build environment for our users. Part of this
> > transformation is, of
Hi Richard, hi Alex
On Mon, 2023-10-30 at 14:07 +, Richard Purdie wrote:
> On Mon, 2023-10-30 at 14:50 +0100, Alexander Kanavin wrote:
> > On Thu, 14 Sept 2023 at 14:56, Richard Purdie
> > wrote:
> > > There are design elements to this work. We need to work out how
> > > we can
> > > make
On Wed, 1 Nov 2023 at 15:18, wrote:
> We are currently experimenting with replacing the eSDK installer with
> the bitbake build environment for our users. Part of this
> transformation is, of course, the shared sstate-cache, for which this
> discussion seems quite relevant. The workflow we are
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libnotify* to *0.8.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libnotify-upgrade-0.8.2-0.8.3.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-poetry-core* to
*1.8.1* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-poetry-core -V 1.8.1
NOTE: Starting
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *icu* to *74-1* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-icu-upgrade-73-2-74-1.patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gpgme* to *1.23.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-gpgme-upgrade-1.22.0-1.23.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-gitdb* to *4.0.11*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-gitdb-upgrade-4.0.10-4.0.11.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 *vulkan-samples* to
*8a9376c6afd45eab6b95b65e5d5d7bad7699b5cb* 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 *libsoup* to *3.4.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsoup-upgrade-3.4.2-3.4.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 *msmtp* to *1.8.25* has
Succeeded.
Next steps:
- apply the patch: git am 0001-msmtp-upgrade-1.8.24-1.8.25.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
*35f796542ee5d7e775643f526973aa75f483bf20* 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 *xserver-xorg* to *21.1.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xserver-xorg-upgrade-21.1.8-21.1.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 *xwayland* to *23.2.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xwayland-upgrade-23.2.1-23.2.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 *man-db* to *2.12.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe man-db 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 *p11-kit* to *0.25.2* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-p11-kit-upgrade-0.25.0-0.25.2.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *linux-firmware* to *20231030*
has Succeeded.
Next steps:
- apply the patch: git am
0001-linux-firmware-upgrade-20230804-20231030.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 *vulkan-tools* to *1.3.268.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 *epiphany* to *45.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-epiphany-upgrade-44.6-45.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *debianutils* to *5.14* has
Succeeded.
Next steps:
- apply the patch: git am 0001-debianutils-upgrade-5.13-5.14.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 *virglrenderer* to *1.0.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 *enchant2* to *2.6.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-enchant2-upgrade-2.6.1-2.6.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 *hwlatdetect* to *2.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-hwlatdetect-upgrade-2.5-2.6.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 *vulkan-validation-layers* to
*1.3.268.0* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe vulkan-validation-layers failed.
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *mpg123* to *1.32.3* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-mpg123-upgrade-1.31.3-1.32.3.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libxrandr* to *1.5.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxrandr-upgrade-1.5.3-1.5.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 *cargo* to *1.73.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe cargo 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
*python3-sphinxcontrib-htmlhelp* to *2.0.4* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-sphinxcontrib-htmlhelp
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rt-tests* to *2.6* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rt-tests 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 *vulkan-headers* to
*1.3.268.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-vulkan-headers-upgrade-1.3.261.1-1.3.268.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 *librsvg* to *2.57.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-librsvg-upgrade-2.56.3-2.57.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *harfbuzz* to *8.2.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-harfbuzz-upgrade-8.2.1-8.2.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 *json-glib* to *1.8.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-json-glib-upgrade-1.6.6-1.8.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 *python3-wheel* to *0.41.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-wheel-upgrade-0.41.2-0.41.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 *vulkan-loader* to *1.3.268.0*
has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade vulkan-loader -V 1.3.268.0 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *shaderc* to *2023.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-shaderc-upgrade-2023.6-2023.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 *piglit* to
*5760ed1f60b39574d8e3ee01d95127074865bf18* 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 *libjpeg-turbo* to *3.0.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libjpeg-turbo-upgrade-3.0.0-3.0.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 *glslang* to *1.3.268.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 *cups* to *2.4.7* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-cups-upgrade-2.4.6-2.4.7.patch
- check
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *kmscube* to
*96d63eb59e34c647cda1cbb489265f8c536ae055* 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 *texinfo* to *7.1* has Failed
(devtool error).
Detailed error information:
The following devtool command failed: upgrade texinfo -V 7.1
NOTE: Starting bitbake server...
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *lighttpd* to *1.4.73* has
Succeeded.
Next steps:
- apply the patch: git am 0001-lighttpd-upgrade-1.4.72-1.4.73.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 *libdrm* to *2.4.117* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libdrm-upgrade-2.4.116-2.4.117.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 *shadow* to *4.14.2* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe shadow 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 *go-helloworld* to
*1d6d2400d4027025cb8edc86a139c9c581d672f7* 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 *vte* to *0.74.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe vte 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 *valgrind* to *3.22.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-valgrind-upgrade-3.21.0-3.22.0.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *cairo* to *1.18.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe cairo 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 *libxkbcommon* to *1.6.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 *libstd-rs* to *1.73.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe libstd-rs 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 *spirv-headers* to *1.3.268.0*
has Succeeded.
Next steps:
- apply the patch: git am
0001-spirv-headers-upgrade-1.3.261.1-1.3.268.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 *webkitgtk* to *2.42.1* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe webkitgtk 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 *bmap-tools* to *3.7* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade bmap-tools -V 3.7 -S
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *rust-llvm* to *1.73.0* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust-llvm 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 *iptables* to *1.8.10* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe iptables 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 *rust* to *1.73.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rust 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 *nghttp2* to *1.58.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-nghttp2-upgrade-1.57.0-1.58.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 *python3-wcwidth* to *0.2.9*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-wcwidth-upgrade-0.2.8-0.2.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
*python3-sphinxcontrib-serializinghtml* to *1.1.9* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libical* to *3.0.17* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libical-upgrade-3.0.16-3.0.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
*python3-sphinxcontrib-devhelp* to *1.0.5* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-sphinxcontrib-devhelp -V
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-setuptools-scm* to
*8.0.4* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-setuptools-scm -V 8.0.4
NOTE:
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-beartype* to *0.16.4*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-beartype-upgrade-0.16.2-0.16.4.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* to *3.12.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3 -V 3.12.0
NOTE: Starting bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libnewt* to *0.52.24* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libnewt-upgrade-0.52.23-0.52.24.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 *libtirpc* to *1.3.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libtirpc-upgrade-1.3.3-1.3.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-pyrsistent* to
*0.20.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-pyrsistent-upgrade-0.19.3-0.20.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 *cronie* to *1.7.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-cronie-upgrade-1.6.1-1.7.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 *gsettings-desktop-schemas* to
*45.0* has Succeeded.
Next steps:
- apply the patch: git am
0001-gsettings-desktop-schemas-upgrade-44.0-45.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 *waffle* to *1.8.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe waffle 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 *python3-setuptools-rust* to
*1.8.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-setuptools-rust-upgrade-1.7.0-1.8.1.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-markdown* to *3.5.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-markdown-upgrade-3.5-3.5.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 *spirv-tools* to *1.3.268.0*
has Succeeded.
Next steps:
- apply the patch: git am 0001-spirv-tools-upgrade-1.3.261.1-1.3.268.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-hypothesis* to
*6.88.1* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-hypothesis-upgrade-6.87.4-6.88.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 *libnsl2* to *2.0.1* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libnsl2-upgrade-2.0.0-2.0.1.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 *dhcpcd* to *10.0.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-dhcpcd-upgrade-10.0.3-10.0.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-sphinxcontrib-applehelp* to *1.0.7* has Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade python3-sphinxcontrib-applehelp
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-trove-classifiers* to
*2023.10.18* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-trove-classifiers-upgrade-2023.9.19-2023.10..patch
- check the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *python3-cryptography* to
*41.0.5* 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 *python3-subunit* to *1.4.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-subunit-upgrade-1.4.2-1.4.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 *python3-pytest* to *7.4.3*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pytest-upgrade-7.4.2-7.4.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 *rpm* to *4.19.0* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe rpm 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-ruamel-yaml* to
*0.18.3* has Succeeded.
Next steps:
- apply the patch: git am
0001-python3-ruamel-yaml-upgrade-0.17.35-0.18.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-pycairo* to *1.25.1*
has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-pycairo-upgrade-1.25.0-1.25.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 *libtest-warnings-perl* to
*0.032* has Succeeded.
Next steps:
- apply the patch: git am
0001-libtest-warnings-perl-upgrade-0.031-0.032.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-spdx-tools* to
*0.8.2* has Succeeded.
Next steps:
- apply the patch: git am 0001-python3-spdx-tools-upgrade-0.8.1-0.8.2.patch
- check the changes to upstream
1 - 100 of 157 matches
Mail list logo
