this can be tricky for many apps depend on it subtly might fail. Perhaps
doing an extended world build with this might be good.
On 2/16/24 3:40 AM, Anuj Mittal wrote:
Signed-off-by: Anuj Mittal
---
...self-exe-for-swig-swiglib-on-non-Win32-plat.patch | 10 ++
On 16/02/2024 09:26:18-0500, Trevor Gamblin wrote:
>
> On 2024-02-16 08:57, Patchtest wrote:
> > Thank you for your submission. Patchtest identified one
> > or more issues with the patch. Please see the log below for
> > more information:
> Alright, so it's still not working properly. Short of
Please ignore this, v2 is already sent...
On Fri, 2024-02-16 at 21:00 +, simone.p.we...@posteo.com wrote:
> From: Simone Weiß
>
> Do not only log that there has been an issue but add WARNING before for
> local
> runs. Hopefully this helps to avoid that people reading the log to
> quickly
From: Simone Weiß
Do not only log that there has been an issue but add WARNING before for local
runs. Hopefully this helps to avoid that people reading the log to quickly miss
issues.
Fixes [YOCTO #15389]
Signed-off-by: Simone Weiß
---
v2:
Fix commit message.
scripts/patchtest | 4 ++--
1
From: Simone Weiß
Do not only log that there has been an issue but add WARNING before for local
runs. Hopefully this helps to avoid that people reading the log to quickly miss
issues.
Fixes [YOCTO #15389]
Signed-off-by: Simone Weiß
sfdf
Signed-off-by: Simone Weiß
---
scripts/patchtest | 4
On Fri, 2024-02-16 at 11:43 -0500, Trevor Gamblin wrote:
>
> On 2024-02-16 11:19, Simone Weiß wrote:
> > On Thu, 2024-02-15 at 22:10 +, Richard Purdie wrote:
> > > On Thu, 2024-02-15 at 21:39 +, Simone Weiß wrote:
> > > > From: Simone Weiß
> > > >
> > > > Add more information to log
From: Bruce Ashfield
Data pulled from: https://github.com/nluedtke/linux_kernel_cves
1/1 [
Author: Nicholas Luedtke
Email: nicholas.lued...@uwalumni.com
Subject: Update 9Feb24
Date: Fri, 9 Feb 2024 18:02:45 -0500
]
Signed-off-by: Bruce Ashfield
---
From: Bruce Ashfield
Integrating the following commit(s) to linux-yocto/.:
1/1 [
Author: Khem Raj
Email: raj.k...@gmail.com
Subject: qemuriscv32/qemuriscv64: Enable Goldfish RTC
Date: Fri, 16 Feb 2024 01:05:51 -0800
This is required for the qemu based riscv system to set
From: Bruce Ashfield
Updating linux-yocto/6.6 to the latest korg -stable release that comprises
the following commits:
eb3e299184cc Linux 6.6.16
bd8740928aac pds_core: Prevent health thread from running during
reset/remove
7110e98840ee drm/amdgpu: Fix missing error code in
From: Bruce Ashfield
Richard,
Here's the v6.6 changes separated out into a smaller pull request
that we can test for the upcoming feature freeze.
Cheers,
Bruce
The following changes since commit 33255c6af06bcb288dc7075f19f9036e4a9c8d81:
llvm: Upgrade to LLVM-18 RC2 (2024-02-16 15:14:26
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/6-7-patch.bbclass-Make-use-of-oe.patch.GitApplyTree.commitIgnored.patch
FAIL: test max line length: Patch line too
Brings following fixes.
* 553c7f61b74 x86: Display -msse-check= default as none
* 4f7d1d2d5ec PowerPC: Add support for Power11 options
* 3c1f1c35784 x86-64: Add R_X86_64_CODE_6_GOTTPOFF
* c426c8e307a x86/APX: VROUND{P,S}{S,D} encodings require AVX512{F,VL}
* 78f9e9faaa4 PR31208, strip can break
The old way of keeping track of the filenames for the patches that
correspond to the commits was to add a special comment line to the end
of the commit message, e.g., "%% original patch: ", using a
temporary git hook. This method had some drawbacks, e.g.:
* It caused problems if one wanted to
Makes it a little bit easier when reading the code.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index
If a commit is marked with "%% ignore" it means it is used by devtool to
keep track of changes to the source code that are not the result of
running do_patch(). These changes need to actually be ignored when
extracting the patches as they typically make no sense as actual patches
in a recipe.
This makes use of the oe.patch.GitApplyTree.commitIgnored() function to
create commits that shall be ignored by `devtool finish`.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/__init__.py | 4 +---
scripts/lib/devtool/standard.py | 6 +-
2 files changed, 2 insertions(+), 8
This makes use of the oe.patch.GitApplyTree.commitIgnored() function to
create commits that shall be ignored by `devtool finish`.
Signed-off-by: Peter Kjellerstedt
---
meta/classes-global/patch.bbclass | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
This function can be used to create a commit that devtool will ignore
when creating/updating the patches.
Signed-off-by: Peter Kjellerstedt
---
meta/lib/oe/patch.py | 10 ++
1 file changed, 10 insertions(+)
diff --git a/meta/lib/oe/patch.py b/meta/lib/oe/patch.py
index
Also correct the comment describing what is happening.
Signed-off-by: Peter Kjellerstedt
---
scripts/lib/devtool/standard.py | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/lib/devtool/standard.py
index
Brings following fixes.
* 553c7f61b74 x86: Display -msse-check= default as none
* 4f7d1d2d5ec PowerPC: Add support for Power11 options
* 3c1f1c35784 x86-64: Add R_X86_64_CODE_6_GOTTPOFF
* c426c8e307a x86/APX: VROUND{P,S}{S,D} encodings require AVX512{F,VL}
* 78f9e9faaa4 PR31208, strip can break
On Fri, Feb 16, 2024 at 1:07 PM Richard Purdie
wrote:
>
> On Fri, 2024-02-16 at 18:29 +0100, Konrad Weihmann wrote:
> > I disagree with the proposed change, as this is unconditional, even
> > though the commit message claims otherwise.
> > It would be better to have it limited to qemuriscv as the
On Fri, 2024-02-16 at 18:29 +0100, Konrad Weihmann wrote:
> I disagree with the proposed change, as this is unconditional, even
> though the commit message claims otherwise.
> It would be better to have it limited to qemuriscv as the commit
> message
> proposes.
>
> Fun fact: I can't find this
Hi all,
I disagree with the proposed change, as this is unconditional, even
though the commit message claims otherwise.
It would be better to have it limited to qemuriscv as the commit message
proposes.
Fun fact: I can't find this message on the web interface of
Version 1.0.1
~~
Released: 2023-12-16
Bugfixes:
* Fix lib name for Qt5 link target
* meson: Pass -D_DARWIN_C_SOURCE on darwin
* Fix macOS build
* stemmer: Resolve potential issue where stemmer may never be initialized
* cli: Don't fail what-provides if components were found
*
On Fri, 2024-02-16 at 11:43 -0500, Trevor Gamblin wrote:
>
> On 2024-02-16 11:19, Simone Weiß wrote:
> > On Thu, 2024-02-15 at 22:10 +, Richard Purdie wrote:
> > > On Thu, 2024-02-15 at 21:39 +, Simone Weiß wrote:
> > > > From: Simone Weiß
> > > >
> > > > Add more information to log
On 2024-02-16 11:19, Simone Weiß wrote:
On Thu, 2024-02-15 at 22:10 +, Richard Purdie wrote:
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.
On Fri, 2024-02-16 at 16:24 +, André Draszik wrote:
> Hi,
>
> When git is configured with safe.bareRepository=explicit [1], various pieces
> here just fail. LWN has an article about the problem that this configuration
> option addresses and why it is useful in [2].
This went to the wrong
When git is configured with safe.bareRepository=explicit [1], the
bitbake git fetcher fails miserably. LWN has an article about the
problem that this configuration option addresses and why it is useful
in [2].
It also seems that it is being rolled out in some environments as a
default for users.
Hi,
When git is configured with safe.bareRepository=explicit [1], various pieces
here just fail. LWN has an article about the problem that this configuration
option addresses and why it is useful in [2].
To test, simply run
git config --global safe.bareRepository explicit
to add
When git is configured with safe.bareRepository=explicit [1], the
bitbake selftests fail miserably. LWN has an article about the
problem that this configuration option addresses and why it is useful
in [2].
It also seems that it is being rolled out in some environments as a
default for users.
In
When git is configured with safe.bareRepository=explicit [1], the
git-make-shallow fails miserably. LWN has an article about the
problem that this configuration option addresses and why it is useful
in [2].
It also seems that it is being rolled out in some environments as a
default for users.
In
On Thu, 2024-02-15 at 22:10 +, Richard Purdie wrote:
> 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
> >
tests/test_funcs.py test_unknown test case is failing with
pytest 8. Skip it for now until upstream has a fix.
https://github.com/python-attrs/attrs/issues/1233
Signed-off-by: Tim Orling
---
Tested with core-image-ptest-python3-attrs on qemux86-64.
From: Wang Mingyu
Changelog:
=
#11842: Properly escape the reason of a skip mark when writing JUnit XML files.
#11861: Avoid microsecond exceeds 1_000_000 when using log-date-format with
%f specifier, which might cause the test suite to crash.
Signed-off-by: Wang Mingyu
The python3-pytest upgrade to 8.0.0 caused a failure in python3-attrs.
https://github.com/python-attrs/attrs/issues/1233
Tim Orling (1):
python3-attrs: skip test failing with pytest-8
Wang Mingyu (1):
python3-pytest: upgrade 7.4.4 -> 8.0.0
...funcs-skip-test_unknown-for-pytest-8.patch | 30
On Fri, 2024-02-16 at 08:49 -0500, Bruce Ashfield wrote:
> On Fri, Feb 16, 2024 at 8:12 AM Richard Purdie
> wrote:
> >
> > Fix:
> >
> > kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File
> > /lib/modules/6.6.15-yocto-
> > standard/build/include/generated/.compat_vdso-offsets.h.cmd in
> >
From: Ross Burton
When cross compiling we have a sysroot, so by telling Meson where it is
explicitly it can do the right thing.
Currently this means it just sets PKG_CONFIG_SYSROOT_DIR to the value
that we already set it to, but in the future this can be used to stop
Meson looking directly in
On 2024-02-16 08:57, Patchtest wrote:
Thank you for your submission. Patchtest identified one
or more issues with the patch. Please see the log below for
more information:
Alright, so it's still not working properly. Short of changing the
subject line, I'm not sure what else can be done on our
Hi,
I use the archiver-class.
In local.conf I added the following:
INHERIT += "archiver"
ARCHIVER_MODE[src] = "original"
But in the tmp/deploy/sources folder, some packages are not included. E.g.
openssl.
But openssl is part of my image and it is included in the license.manifest file.
Does
On Fri, 16 Feb 2024 at 14:33, Richard Purdie
wrote:
> Whilst I agree that would be nice, I have no knowledge in that area, no
> available time and nobody else seems to have that either. Not sure what
> we can do in that case :(
I'd hope pressure on product-making users to do this update can
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/2-5-meta-lib-bblayers-buildconf.py-add-support-for-configuration-summaries.patch
FAIL: test commit message
On Fri, Feb 16, 2024 at 10:46 AM André Draszik wrote:
>
> Given file names like
>
> 6.4.do_fetch.sigdata.821b6c62f9f2bd8b7e1378656b8319697a21f6f6e4a351f98dc325a18ef7ed0f,
> I'm pretty sure we want to match the dot here, not any character.
>
> Fixes: 2fa1b25d7485 ("sstate-cache-management:
On Fri, 2024-02-16 at 09:11 +0100, Andreas Helbech Kleist wrote:
> On Thu, 2024-02-15 at 19:45 -0600, Ryan Eatmon via
> lists.openembedded.org wrote:
> >
> > On 2/15/2024 7:43 PM, Steve Sakoman wrote:
> > > On Thu, Feb 15, 2024 at 3:20 PM Ryan Eatmon wrote:
> > > >
> > > >
> > > > With this
On Fri, Feb 16, 2024 at 8:12 AM Richard Purdie
wrote:
>
> Fix:
>
> kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File
> /lib/modules/6.6.15-yocto-standard/build/include/generated/.compat_vdso-offsets.h.cmd
> in package kernel-devsrc contains reference to TMPDIR [buildpaths]
>
Did this just
Avoid:
u-boot-1_2024.01-r0 do_package_qa: QA Issue: File
/boot/u-boot-qemuriscv64-2024.01-r0.elf in package u-boot contains reference to
TMPDIR [buildpaths]
by ensuring the compiler has the prefix mapping options passed in to it
to correctly remap the source paths and avoid the warning.
On Fri, 2024-02-16 at 13:12 +, Jose Quaresma wrote:
>
>
> Richard Purdie escreveu (sexta,
> 16/02/2024 à(s) 11:34):
> > On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
> > > * We are now a week from feature freeze for 5.0, our next LTS
> > > release
> >
> > For better or worse
Richard Purdie escreveu (sexta,
16/02/2024 à(s) 11:34):
> On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
> > * We are now a week from feature freeze for 5.0, our next LTS
> > release
>
> For better or worse but probably not entirely surprisingly, there are
> quite a few things that we
Fix:
kernel-devsrc-1.0-r0 do_package_qa: QA Issue: File
/lib/modules/6.6.15-yocto-standard/build/include/generated/.compat_vdso-offsets.h.cmd
in package kernel-devsrc contains reference to TMPDIR [buildpaths]
by adding to the list of files we do this with. Also drop the
conditional since rm -f
On 2024-02-16 04:35, Alexander Kanavin wrote:
Just wanted to note that sadly patchtest replies still aren't
threaded. What are regular mail clients doing that patchtest does not?
Patchwork's docs say
(https://patchwork.readthedocs.io/en/latest/usage/overview/#comments):
|Comments are
Signed-off-by: Alexander Kanavin
---
meta/lib/bblayers/buildconf.py | 12 +---
meta/lib/oeqa/selftest/cases/bblayers.py | 2 +-
2 files changed, 10 insertions(+), 4 deletions(-)
diff --git a/meta/lib/bblayers/buildconf.py b/meta/lib/bblayers/buildconf.py
index
They are handled exactly same as conf-notes.txt.
Signed-off-by: Alexander Kanavin
---
scripts/oe-setup-builddir | 10 ++
1 file changed, 10 insertions(+)
diff --git a/scripts/oe-setup-builddir b/scripts/oe-setup-builddir
index 678aeac4be5..dcb384c33a6 100755
---
This is beneficial for setting up builds, as this list can be used
to determine reliably where the actual layers are, and discover
available configurations from them.
Also adjust the selftest to check the presence of that file rather
than any specific layer in a hardcoded location.
Sample output
This is another piece of the puzzle in setting up builds from nothing
without having to write custom scripts or use external tools.
After layers have been fetched and placed into their respective locations by
oe-setup-layers, one would surely want to proceed to the actual build, and
here's how:
Existing conf-notes.txt is not adequate in situations where the user
needs to select a config template from several, or get an overview of them and
is interested only in a brief explanation of what the template is for,
but not extended multi-paragraph instructions for how to use it.
Such
Signed-off-by: Anuj Mittal
---
...ct-has-a-different-signature-on-musl.patch | 3 +-
...ools_1.22.9.bb => gst-devtools_1.22.10.bb} | 2 +-
22.9.bb => gstreamer1.0-libav_1.22.10.bb} | 2 +-
..._1.22.9.bb => gstreamer1.0-omx_1.22.10.bb} | 2 +-
...ialized-warnings-when-compiling-with.patch
Backport an upstream patch to remove Python exception handler which is
deprecated and also removed from swig.
https://github.com/swig/swig/commit/736c052d7de3685be9d5c4aecee6b36273e8c319
Signed-off-by: Anuj Mittal
---
.../files/fix-issues-with-swig-4-2.patch | 32 +++
From: Upgrade Helper
Signed-off-by: Anuj Mittal
---
...ct-has-a-different-signature-on-musl.patch | 3 +-
...ools_1.22.9.bb => gst-devtools_1.22.10.bb} | 2 +-
22.9.bb => gstreamer1.0-libav_1.22.10.bb} | 2 +-
..._1.22.9.bb => gstreamer1.0-omx_1.22.10.bb} | 2 +-
Signed-off-by: Anuj Mittal
---
...self-exe-for-swig-swiglib-on-non-Win32-plat.patch | 10 ++
...configure-use-pkg-config-for-pcre-detection.patch | 6 +++---
meta/recipes-devtools/swig/swig/determinism.patch| 12 +++-
.../swig/{swig_4.1.1.bb => swig_4.2.0.bb}| 2
Signed-off-by: Anuj Mittal
---
.../stress-ng/{stress-ng_0.17.04.bb => stress-ng_0.17.05.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-extended/stress-ng/{stress-ng_0.17.04.bb =>
stress-ng_0.17.05.bb} (94%)
diff --git
Signed-off-by: Anuj Mittal
---
meta/recipes-devtools/orc/{orc_0.4.36.bb => orc_0.4.37.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/orc/{orc_0.4.36.bb => orc_0.4.37.bb} (92%)
diff --git a/meta/recipes-devtools/orc/orc_0.4.36.bb
Signed-off-by: Anuj Mittal
---
.../sqlite/{sqlite3_3.44.2.bb => sqlite3_3.45.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-support/sqlite/{sqlite3_3.44.2.bb => sqlite3_3.45.1.bb}
(62%)
diff --git a/meta/recipes-support/sqlite/sqlite3_3.44.2.bb
This includes a fix to include complete library version. Release notes:
https://github.com/libproxy/libproxy/releases/tag/0.5.4
Signed-off-by: Anuj Mittal
---
.../libproxy/{libproxy_0.5.3.bb => libproxy_0.5.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename
Drop patches that have been merged upstream and available in this
version.
Signed-off-by: Anuj Mittal
---
...ix-minicom-h-v-return-value-is-not-0.patch | 33 ---
.../minicom/allow.to.disable.lockdev.patch| 30 -
.../{minicom_2.8.bb => minicom_2.9.bb}|
Signed-off-by: Anuj Mittal
---
.../enchant/{enchant2_2.6.5.bb => enchant2_2.6.7.bb}| 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-support/enchant/{enchant2_2.6.5.bb => enchant2_2.6.7.bb}
(91%)
diff --git a/meta/recipes-support/enchant/enchant2_2.6.5.bb
On Tue, 2024-02-13 at 08:50 -0700, Stephen Jolley wrote:
> * We are now a week from feature freeze for 5.0, our next LTS
> release
For better or worse but probably not entirely surprisingly, there are
quite a few things that we may want to try and fit in. I've listed them
just so everyone knows
On Thu, 15 Feb 2024 at 16:00, Richard Purdie
wrote:
> I know this feedback is long delayed so my apologies for that.
>
> I think I'm ok with the idea of this but I believe the naming isn't
> quite right.
>
> "notes" does suggest something longer, so that is fine. My worry is
> that in the
From: Ross Burton
Drop the clang/VFP patch, merged in 00116b6.
Drop the FILES for ${libdir}/libffi-${PV}, this file isn't installed.
License-Update: Copyright year updated to 2024.
Signed-off-by: Ross Burton
---
...m-sysv-reverted-clang-VFP-mitigation.patch | 102 --
Given file names like
6.4.do_fetch.sigdata.821b6c62f9f2bd8b7e1378656b8319697a21f6f6e4a351f98dc325a18ef7ed0f,
I'm pretty sure we want to match the dot here, not any character.
Fixes: 2fa1b25d7485 ("sstate-cache-management: Rewrite in python") in oe-core
Fixes: b723fcaac52f
=
Version 1.4.3
=
- AdwAboutWindow
- Don't pre-select the first section on the Legal page
- AdwHeaderBar
- Fix visibility after changing :show-back-button
- AdwPreferencesWindow
- Fix :visible-page and :visible-page-name docs
- AdwViewSwitcherBar
- Fix a warning
From: Fabien Mahot
When ldconfig-native reads an ELF file, it computes an offset from a LOAD
segment, to point on DT NEEDED entries of dynstr section.
Without this patch, ldconfig-native uses only the first LOAD segment, even if
the offset is incorrect.
This patch adds conditions to compute the
Just wanted to note that sadly patchtest replies still aren't
threaded. What are regular mail clients doing that patchtest does not?
Alex
On Thu, 15 Feb 2024 at 22:37, Trevor Gamblin wrote:
>
> There's no need to use regex for extracting the Message-ID field from
> the patch email and mangle it
On Thu, 2024-02-15 at 19:45 -0600, Ryan Eatmon via
lists.openembedded.org wrote:
>
> 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
72 matches
Mail list logo
