ChangeLog:
https://salsa.debian.org/dpkg-team/dpkg/-/raw/1.21.x/debian/changelog
* Add new dependency libmd
* Update SRC_URI
* Refresh patch
* Drop backport patch
Signed-off-by: Yi Zhao
---
meta/recipes-devtools/dpkg/dpkg.inc | 4 +-
...ive-Prevent-directory-traversal-for-.patch | 3
[Edited Message Follows]
Hi,
https://github.com/openembedded/openembedded-core/commit/5fbb4ca8da4f4f1ea426275c45634802dcb5a575
This patch caused something terrible wrong behavior, because
".../work-shared//kernel-source/" directory is totally empty and the
complete Linux kernel source is missi
Hi,
https://github.com/openembedded/openembedded-core/commit/5fbb4ca8da4f4f1ea426275c45634802dcb5a575
This patch caused something terrible wrong behavior, because
".../work-shared//kernel-source/" directory is totally empty and the
complete Linux kernel source is missing if INHERIT += "archiver
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/v4-1-2-selftest-add-Upstream-Status-to-.patch-files.patch
FAIL: test commit message presence: Please include a comm
Signed-off-by: Martin Jansa
---
v4: use Inappropriate [Test artefact] everywhere as requested
add Upstream-Status to *.patch.expected as well to fix
devtool.DevtoolUpdateTests.test_devtool_update_recipe_with_gitignore
devtool.DevtoolUpdateTests.test_devtool_update_recipe_long_filename
* it's enabled for patches in oe-core for very long time and I was using
it for many other layers as well, so most layers should be in good
shape
* it's also possible to disable it for individual layer as shown
by oe-core in:
https://git.openembedded.org/openembedded-core/commit/meta/clas
On Wed, Jun 5, 2024 at 2:52 AM Jonas Gorski via lists.openembedded.org
wrote:
>
> There are two types of soft FPU options for arm, soft and softfp, and if
> using the latter the wrong dynamic loader will be used.
>
> E.g. go will link against ld-linux-armhf.so.3, but libc6 will only ship
> a ld-li
On Tue, 2024-06-04 at 11:03 +0200, Martin Jansa via
lists.openembedded.org wrote:
> * these were reported in:
> https://lists.openembedded.org/g/openembedded-core/message/200282
>
> Signed-off-by: Martin Jansa
devtool selftest still isn't quite working with this:
https://valkyrie.yoctoproject
On 2024-06-05 11:49 a.m., Steve Sakoman wrote:
I had no issues applying the patch when taken from patchworks,
Huh, that's odd.
Thunderbird and my email delivery chain doesn't usually mangle patches.
Looking at:
https://patchwork.yoctoproject.org/project/oe-core/patch/20240605143945.405558-1-de
On Wed, Jun 5, 2024 at 8:42 AM Randy MacLeod
wrote:
>
> On 2024-06-05 10:56 a.m., Hemraj, Deepthi via lists.openembedded.org wrote:
>
> Regression testing was done and below are the test results:
> After update (v13.3)
>
> === gcc Summary ===
>
> # of expected passes248620
> # of unexp
On 2024-06-05 10:56 a.m., Hemraj, Deepthi via lists.openembedded.org wrote:
Regression testing was done and below are the test results:
*After update (v13.3)*
=== gcc Summary ===
# of expected passes 248620
# of unexpected failures 9
# of expected failures 2484
# of u
Regression testing was done and below are the test results:
*After update (v13.3)*
=== gcc Summary ===
# of expected passes 248620
# of unexpected failures 9
# of expected failures 2484
# of unresolved testcases 25028
# of unsupported tests 4145
*Before upda
v2 of the patch: fixed the commit message which was referencing the wrong
test-name.
On Wed, Jun 5, 2024 at 3:17 PM wrote:
> From: Etienne Cordonnier
>
> test_systemd_coredump_minidebuginfo was getting skipped in CI, because the
> minidebuginfo feature isn't enabled per default in any image at
From: Etienne Cordonnier
test_systemd_coredump_minidebuginfo was getting skipped in CI, because the
minidebuginfo feature isn't enabled per default in any image at the moment.
Add this selftest so that test_systemd_coredump_minidebuginfo gets executed in
CI.
Signed-off-by: Etienne Cordonnier
-
Hi, please ignore this email. I was on the wrong branch.
On Wed, Jun 5, 2024 at 3:08 PM Etienne Cordonnier via lists.openembedded.org
wrote:
> From: Richard Purdie
>
> Signed-off-by: Richard Purdie
> Signed-off-by: Etienne Cordonnier
> ---
> meta/recipes-core/images/build-appliance-image_15.
From: Etienne Cordonnier
test_minidebuginfo_qemu was getting skipped in CI, because the feature isn't
enabled per default in any image at the moment.
Add this selftest so that test_minidebuginfo_qemu gets executed in CI.
Signed-off-by: Etienne Cordonnier
---
meta/lib/oeqa/selftest/cases/minid
From: Richard Purdie
Signed-off-by: Richard Purdie
Signed-off-by: Etienne Cordonnier
---
meta/recipes-core/images/build-appliance-image_15.0.0.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/images/build-appliance-image_15.0.0.bb
b/meta/recipes-core/im
On Wed, 5 Jun 2024 at 14:25, Quentin Schulz wrote:
> Additionally, Intel Vulkan driver forces libclc dependency if intel-clc
> option is not "system" (so either "enabled" or "disabled" or "auto"),
> since commit b52e25d3a8eee702ff5d21e4cdb9a4dc0736282a.
>
> Moreover, Intel Iris Gallium driver for
Hi Alex, Markus,
On 6/5/24 1:35 PM, Alexander Kanavin wrote:
I think we could ask Markus to look at this update to 24.1, as he's
done work with libclc dependency previously (and authored the patch
for it, which should preferably be dropped).
Yeah, I'm hitting a lot of issues right now :/
I
I think we could ask Markus to look at this update to 24.1, as he's
done work with libclc dependency previously (and authored the patch
for it, which should preferably be dropped).
Alex
On Tue, 4 Jun 2024 at 12:13, Alexander Kanavin via
lists.openembedded.org
wrote:
>
> I don't think you need
Hi Richard,
I'm assuming you meant "How about we add runtime coverage to the selftest"
(it got autocorrected to "How are we all runtime coverage to the selftest").
I'll have a look at adding this to selftest to ensure that the test is
executed, however for context you had suggested another solutio
There are two types of soft FPU options for arm, soft and softfp, and if
using the latter the wrong dynamic loader will be used.
E.g. go will link against ld-linux-armhf.so.3, but libc6 will only ship
a ld-linux.so.3, so go programs will fail to start.
Fix this by instead checking for TARGET_FPU
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/scarthgap-run-postinsts.service-Removed---no-reload-to-fix-reload-warning-when-users-execute-systemctl-in-the-first-
From: Lei Maohui
This warning is because after systemd has been upgraded to 255, reloading units
operation is needed even when "enable/disable" units by systemctl.
(From OE-Core rev: 28a7064403f2433ef3cb4d52b03dd73437f2d665)
Signed-off-by: Lei Maohui
Signed-off-by: Alexandre Belloni
Signed-o
Thanks for getting to the root of the issue.
Alex
On Wed 5. Jun 2024 at 9.47, Khem Raj via lists.openembedded.org wrote:
> On Mon, Jun 3, 2024 at 9:56 PM Khem Raj wrote:
> >
> > On Mon, Jun 3, 2024 at 10:49 AM Khem Raj wrote:
> > >
> > > On Mon, Jun 3, 2024 at 9:35 AM Richard Purdie
> > > w
25 matches
Mail list logo
