On 2/15/24 at 22:05, Patchtest wrote:
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/1-2-patchtest-Fix-grammar-in-log-output.patch
FAIL: test commit message
lets drop this patch, I think it needs some submodule syncing but I
will let upstream do it.
On Thu, Feb 15, 2024 at 1:23 PM Richard Purdie
wrote:
>
> On Wed, 2024-02-14 at 12:47 -0800, Khem Raj wrote:
> > This gets the needed fixes for llvm-18 based builds
> > spdlog musl patches has been
I’m
On Thu, Feb 15, 2024 at 5:12 PM Khem Raj wrote:
> On Thu, Feb 15, 2024 at 1:29 PM Richard Purdie
> wrote:
> >
> > Unfortunately the new openssh version has an ICE on mips. This looks
> similar to:
> >
> > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
> >
On 2/15/2024 7:43 PM, Steve Sakoman wrote:
On Thu, Feb 15, 2024 at 3:20 PM Ryan Eatmon wrote:
With this patch in place we are seeing a breakage on our kernel builds.
This patch was cherry picked from master, but the next patch on this
file in master removes the LOCALVERSION setting...
On Thu, Feb 15, 2024 at 3:20 PM Ryan Eatmon wrote:
>
>
> With this patch in place we are seeing a breakage on our kernel builds.
> This patch was cherry picked from master, but the next patch on this
> file in master removes the LOCALVERSION setting...
>
>
With this patch in place we are seeing a breakage on our kernel builds.
This patch was cherry picked from master, but the next patch on this
file in master removes the LOCALVERSION setting...
On Thu, Feb 15, 2024 at 1:29 PM Richard Purdie
wrote:
>
> Unfortunately the new openssh version has an ICE on mips. This looks similar
> to:
>
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
>
> Given how long these have been open,
From: Richard Purdie
The package task references WORKDIR at it's top level and we can't
easily make the timestamp for that determnistic due to writes to files
there and in other subdirs. We could try and force it to a specific value
but it is easier to just remove it from the package task, we
I found out that this backport is applicable to dunfell.
This increased sstate reuse.
Richard Purdie (1):
sstatesig: Allow exclusion of the root directory for do_package
meta/lib/oe/sstatesig.py | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.25.1
-=-=-=-=-=-=-=-=-=-=-=-
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> When launching the debug configuration, the source files from the
> debug
> rootfs were openened in the editor instead of the local workspace
> files.
> We add an exception to properly map them to the file being developed
> and
>
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> By default, the cpptools VSCode extension will use the host's headers
> and flags for linting. This results in a lot of include errors and
> misleading definitions. Even though this generic configuration
> doesn't
> include all
On Thu, 2024-02-15 at 18:04 +0100, Enguerrand de Ribaucourt wrote:
> An exception was raised because we did not have the topdir attribute
> which was used in fallback mode (non cmake/meson recipes).
>
> Already in the merge queue in Adrian's latest patches.
> ---
> scripts/lib/devtool/ide_sdk.py
There is a new official bitbake plugin:
https://marketplace.visualstudio.com/items?itemName=yocto-project.yocto-bitbake
This plugin automatically updates the .vscode/settings.json file.
Having the settings.json file in git and a plugin which modifies this
file is not ideal. It can lead to anoying
Provide a reasonable default configuration for VSCode and the
yocto.bitbake extension.
The generated default configuration is generic and minimal. It's mostly
supposed to prevent VSCode from OOM exceptions if the build directory is
in the scope of the indexer plugins of VSCode.
But it also
Changes in comparison to v3:
- Add more plugin settings as suggested by Enguerrand
https://lists.openembedded.org/g/openembedded-core/message/195505
Changes in comparison to v2:
- Do not integrate with the oe-setup-build or templating infrastrucutre.
Provide a minimalistic script which is
> -Original Message-
> From: openembedded-core@lists.openembedded.org
> On Behalf Of Richard Purdie
> Sent: den 15 februari 2024 18:11
> To: Enguerrand de Ribaucourt ;
> openembedded-core@lists.openembedded.org
> Cc: adrian.freiho...@gmail.com; ross.bur...@arm.com;
>
With these and 3 more patches sent to the bitbake-devel group oe-selftest
looks already much better:
oe-selftest -a
Required tests failed (successes=502, skipped=6, failures=7, errors=3)
eSDK.oeSDKExtSelfTest.test_image_generation_binary_feeds: ERROR
From: Adrian Freihofer
All the regexes throw a warning like this:
WARNING: scripts/lib/recipetool/create_buildsys.py:140:
SyntaxWarning: invalid escape sequence '\s'
proj_re = re.compile('project\s*\(([^)]*)\)', re.IGNORECASE)
Python 3 interprets string literals as Unicode strings,
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
From: Adrian Freihofer
Python 3 interprets string literals as Unicode strings, and therefore
\s is treated as an escaped Unicode character which is not correct.
Declaring the RegEx pattern as a raw string instead of unicode is
required for Python 3.
Signed-off-by: Adrian Freihofer
From: Ross Burton
recipetool's pyproject.toml parsing needs tomllib (python 3.11+) or
tomli (not a hard dependency), so is prone to failing depending on the
host configuration.
Downgrade the Meson release used for the checks to 0.52.1, which was the
last release before moving to pyproject.toml.
From: Adrian Freihofer
On hosts with git defaulting to main branch the following exception
occures:
File .../buildhistory.py", line 99, in test_compare_dict_blobs_default
blob1 = self.repo.heads.master.commit.tree.blobs[0]
^^
File
From: Ross Burton
Add support for qmp sockets and defaults to unix:qmp.sock if unspecified
Signed-off-by: Ross Burton
Signed-off-by: Eilís 'pidge' Ní Fhlannagáin
Signed-off-by: Richard Purdie
Backported from master: 380631797f0d63124a8c21efa93ab672dbd79283
Qemu throws many warnings without
From: Adrian Freihofer
test_recipetool_create_github and test_recipetool_create_github_tarball
fail because the old meson version used by these tests cases does not
run on Python 3.12. The issue is in the dependencies.py which comes with
meson:
ERROR:
From: Adrian Freihofer
assertEquals is deprecated since Python 2.7:
https://docs.python.org/2/library/unittest.html#deprecated-aliases
It throws errors at least on Python 3.12. Replace it by assertEqual.
Signed-off-by: Adrian Freihofer
Signed-off-by: Richard Purdie
Backported from master:
From: Chris Laplante
'imp' was deprecated in Python 3.4 and removed in 3.12. The
piece of importlib we use has been around since 3.3.
Signed-off-by: Chris Laplante
Signed-off-by: Alexandre Belloni
Signed-off-by: Richard Purdie
Cherry-picked from master:
From: Ross Burton
SafeConfigParser was renamed to ConfigParser in 3.2, and the
SafeConfigParser alias will be removed in 3.12.
Signed-off-by: Ross Burton
Signed-off-by: Alexandre Belloni
Cherry-picked from master: 71b3e7f71727137b4b996cc4160c9cc1581824b8
Signed-off-by: Adrian Freihofer
---
From: Trevor Gamblin
When invoking runqemu with Python 3.12, the following warning is
encountered:
|SyntaxWarning: invalid escape sequence '\.'
This is because the interpreter scans the string before it is processed
by the regex module, and it interprets the backslash as part of an
escape
On Thu, Feb 15, 2024 at 11:43 AM Tim Orling wrote:
> This version deprecates the very PEP-517 build backend we depend upon for
> the python_poetry_core bbclass.
> We do not want to take this so late in the release cycle, nor do we want
> to add all the dependencies required to build the full
This version deprecates "poetry.core.masonry.builder", but we detect
"poetry.core.masonry.api" in recipetool and nothing has broken our
build of wheels.
Thanks to Ross for noticing that the
"from poetry.core.masonry.builders.wheel import WheelBuilder"
is not a massive change in practice.
A missing space when using :append would lead to run-on URIs if there
was no whitespace at the end of the original SRC_URI.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
On Thu, 2024-02-15 at 21:39 +, Simone Weiß wrote:
> From: Simone Weiß
>
> Add more information to log messages when a test case fails.
> Still keep it short and mostly reference the documentation. Reasson is that
> documentation should already contain the needed information, do not duplicate
From: Simone Weiß
Add more information to log messages when a test case fails.
Still keep it short and mostly reference the documentation. Reasson is that
documentation should already contain the needed information, do not duplicate
it here, so we also do not need to update here should the
There's no need to use regex for extracting the Message-ID field from
the patch email and mangle it by removing the angle brackets in the
process. Pull it directly from the mbox so that Patchtest's replies have
even fewer differences when compared to other replies. Also add a TODO
so that it's
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
Unfortunately the new openssh version has an ICE on mips. This looks similar to:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104817
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104820
Given how long these have been open, workaround the issue by disabling the
compiler
hardening options on mips.
On Wed, 2024-02-14 at 12:47 -0800, Khem Raj wrote:
> This gets the needed fixes for llvm-18 based builds
> spdlog musl patches has been merged in the updated version module
> 32bit backport is also available in this version
>
> Signed-off-by: Khem Raj
Breaks with multilib:
Hi Alejandro,
On Thu, 2024-02-15 at 12:10 -0700, Alejandro Enedino Hernandez
Samaniego wrote:
> On 2/6/24 03:27, Richard Purdie wrote:
> >
> > On Thu, 2024-02-01 at 02:56 +, Maanya Goenka wrote:
> > > From: Maanya Goenka
> > >
> > > Add usrmerge to DISTRO_FEATURES_FILTER_NATIVESDK (and
>
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/1-2-patchtest-Fix-grammar-in-log-output.patch
FAIL: test commit message presence: Please include a commit message
Project has made changes to the site structure: https://tukaani.org/
| The XZ projects were moved to their own website on xz.tukaani.org in
| January 2024. The old links will be kept working via redirections.
While old release tarballs are still being accesible on the site via
redirects, new
Add a -d/--debug option to patchtest-send-results so that the contents
of the constructed raw email can be checked without actually sending
anything to the list or patch author.
Signed-off-by: Trevor Gamblin
---
scripts/patchtest-send-results | 17 +++--
1 file changed, 11
Signed-off-by: Trevor Gamblin
---
scripts/patchtest | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/scripts/patchtest b/scripts/patchtest
index 8c9a73e1dba..d0dc6e8fac5 100755
--- a/scripts/patchtest
+++ b/scripts/patchtest
@@ -162,7 +162,7 @@ def run(patch, logfile=None):
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/xz-upgrade-5.4.5---5.4.6.patch
FAIL: test lic files chksum modified not mentioned: LIC_FILES_CHKSUM changed
Project has made changes to the site structure: https://tukaani.org/
| The XZ projects were moved to their own website on xz.tukaani.org in
| January 2024. The old links will be kept working via redirections.
While old release tarballs are still being accesible on the site via
redirects, new
This version deprecates the very PEP-517 build backend we depend upon for
the python_poetry_core bbclass.
We do not want to take this so late in the release cycle, nor do we want to
add all the dependencies required to build the full poetry.
https://github.com/python-poetry/poetry-core/pull/692
On 2/6/24 03:27, Richard Purdie wrote:
On Thu, 2024-02-01 at 02:56 +, Maanya Goenka wrote:
From: Maanya Goenka
Add usrmerge to DISTRO_FEATURES_FILTER_NATIVESDK (and
DISTRO_FEATURES_FILTER_NATIVE for consistency),
since we have come across cases where the distro feature would be required
Refresh local patch.
Changelog:
https://github.com/madler/zlib/releases/tag/v1.3.1
Signed-off-by: Denys Dmytriyenko
---
...configure-Pass-LDFLAGS-to-link-tests.patch | 22 +--
.../zlib/{zlib_1.3.bb => zlib_1.3.1.bb} | 2 +-
2 files changed, 11 insertions(+), 13
On Thu, Feb 15, 2024 at 2:29 AM Sadineni, Harish via
lists.openembedded.org
wrote:
>
> Hi all,
>
>
> We are analysing the test failures reported by the autobilder at
> https://autobuilder.yocto.io/pub/non-release/20240204-3/testresults/qemux86-64-tc/testresults.json
> The autobuilder result
Hi Baruch,
That's a good question.
Bruce, if we need a new kernel feature (squashfs), the only way would be
first to contribute it to https://git.yoctoproject.org/yocto-kernel-cache/ ?
Or there's another way to enable a specific kernel configuration in a
selftest?
Slava
On 14.02.2024 07:54,
On AB runs of reproducible-meta-oe/Repro meta-oe/meta-oe,
"waf --version" does not seem to contain the version but an error
message with "RuntimeWarning: " [0].
Since the actual output is not saved anywhere, it is quite hard to
debug.
This patch detects the problematic case and send it to the
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *numactl* to *2.0.18* has
Succeeded.
Next steps:
- apply the patch: git am 0001-numactl-upgrade-2.0.17-2.0.18.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 *gstreamer1.0-python* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-python-upgrade-1.22.9-1.22.10.patch
- check the changes to
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libproxy* to *0.5.4* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libproxy-upgrade-0.5.3-0.5.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 *libusb1* to *1.0.27* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-libusb1-upgrade-1.0.26-1.0.27.patch
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libgit2* to *1.7.2* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libgit2-upgrade-1.7.1-1.7.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 *gst-devtools* to *1.22.10*
has Succeeded.
Next steps:
- apply the patch: git am 0001-gst-devtools-upgrade-1.22.9-1.22.10.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 *gstreamer1.0-rtsp-server* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-rtsp-server-upgrade-1.22.9-1.22.10.patch
- check the changes
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *libpng* to *1.6.42* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade libpng -V 1.6.42
NOTE: Reconnecting to bitbake server...
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
(devtool error).
Detailed error information:
The following devtool command failed: upgrade icu -V 74-2
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 *sqlite3* to *3.45.1* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade sqlite3 -V 3.45.1
NOTE: Reconnecting to bitbake
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gstreamer1.0-omx* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am 0001-gstreamer1.0-omx-upgrade-1.22.9-1.22.10.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
*7a93ae5d3c90cb5d1d8d775a8cd9d30bc745f658* 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 *gstreamer1.0* to *1.22.10*
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 *libsdl2* to *2.30.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsdl2-upgrade-2.28.5-2.30.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 *xprop* to *1.2.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xprop-upgrade-1.2.6-1.2.7.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 *lttng-ust* to *2.13.7* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe lttng-ust 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 *libpciaccess* to *0.18* 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 *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 *glslang* to *1.3.275.0* has
Succeeded.
Next steps:
- apply the patch: git am 0001-glslang-upgrade-1.3.268.0-1.3.275.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 *makedepend* to *1.0.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-makedepend-upgrade-1.0.8-1.0.9.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-utility-libraries* to
*1.3.275.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 *taglib* to *2.0* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-taglib-upgrade-1.13.1-2.0.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *gtk+3* to *3.24.41* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe gtk+3 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 *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 *shaderc* to *2023.8* has
Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe shaderc 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 *spirv-headers* to *1.3.275.0*
has Succeeded.
Next steps:
- apply the patch: git am
0001-spirv-headers-upgrade-1.3.268.0-1.3.275.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 *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 *diffoscope* to *257* has
Succeeded.
Next steps:
- apply the patch: git am 0001-diffoscope-upgrade-253-257.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 *shadow* to *4.15.0* has
Failed (devtool error).
Detailed error information:
The following devtool command failed: upgrade shadow -V 4.15.0
NOTE: Reconnecting to bitbake server...
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *vulkan-tools* to *1.3.275.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.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-enchant2-upgrade-2.6.5-2.6.7.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 *libxext* to *1.3.6* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxext-upgrade-1.3.5-1.3.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 *ed* to *1.20.1* has Succeeded.
Next steps:
- apply the patch: git am 0001-ed-upgrade-1.20-1.20.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 *mesa* to *24.0.1* has Failed
(devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe mesa 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 *tzdata* to *2024a* has
Failed(do_compile).
Detailed error information:
do_compile failed
Next steps:
- apply the patch: git am 0001-tzdata-upgrade-2023d-2024a.patch
-
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *piglit* to
*b9374d2c59e665bf60950af898003ed17bf98370* 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 *vulkan-samples* to
*04091a428b76f234d47b8ce72cb4f3693e2fbcd1* has Failed (devtool error).
Detailed error information:
Running 'devtool upgrade' for recipe vulkan-samples failed.
Hello,
this email is a notification from the Auto Upgrade Helper
that the automatic attempt to upgrade the recipe *xkbcomp* to *1.4.7* has
Succeeded.
Next steps:
- apply the patch: git am 0001-xkbcomp-upgrade-1.4.6-1.4.7.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 *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 *libxvmc* to *1.0.14* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libxvmc-upgrade-1.0.13-1.0.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 *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 *minicom* to *2.9* has
Succeeded.
Next steps:
- apply the patch: git am 0001-minicom-upgrade-2.8-2.9.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 *libsecret* to *0.21.3* has
Succeeded.
Next steps:
- apply the patch: git am 0001-libsecret-upgrade-0.21.2-0.21.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 *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 *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 *mc* to *4.8.31* has Succeeded.
Next steps:
- apply the patch: git am 0001-mc-upgrade-4.8.30-4.8.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 *gstreamer1.0-plugins-ugly* to
*1.22.10* has Succeeded.
Next steps:
- apply the patch: git am
0001-gstreamer1.0-plugins-ugly-upgrade-1.22.9-1.22.10.patch
- check the
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 *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
1 - 100 of 194 matches
Mail list logo
