Add --disable-tests to EXTRA_OECONF as the tests are not usable in
ptest - they can only run in-situ - and fails to build when building
with -D_TIME_BITS=64 -D_FILE_OFFSET_BITS=64.
Signed-off-by: Ola x Nilsson
---
meta/recipes-core/kbd/kbd_2.5.1.bb | 1 +
1 file changed, 1 insertion(+)
diff --g
On Thu, Nov 24 2022, Richard Purdie wrote:
> On Thu, 2022-11-24 at 17:52 +0100, Ola x Nilsson wrote:
>> bison-native is required if any .y-file is changed, by patch or in
>> devtool. Otherwise the build will fail with
>
> The key point is that we don't patch any .y file out the box. I
> therefor
Hi Richard,
The AB is actually running 'all' tests.
The '--skip-tests (-R)' option means 'Run all (unhidden) tests except the ones
specified.', according to its help message. This is also its actual effect for
now. You can see there's an implicit 'run all tests' meaning in this option.
The '-T
From: Wang Mingyu
Signed-off-by: Wang Mingyu
---
.../{systemd-systemctl-native.bb => systemd-systemctl.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/systemd/{systemd-systemctl-native.bb =>
systemd-systemctl.bb} (90%)
diff --git a/meta/recipes-core
Alex, I think yhou missed this one.
../Randy
On 2022-11-04 14:47, Zheng Qiu wrote:
An earlier version of valgrind fixed the defunct processes bug, so those
tests that were skipped specifically for arm can pass now in master,
kirkstone, honister, hardknott, and dunfell.
Detailed test result wit
On Thu, 2022-11-24 at 17:52 +0100, Ola x Nilsson wrote:
> bison-native is required if any .y-file is changed, by patch or in
> devtool. Otherwise the build will fail with
The key point is that we don't patch any .y file out the box. I
therefore don't want to add this dependency.
If you do start
Backport patch to fix CVE-2022-2880.
Signed-off-by: Sakib Sajal
---
meta/recipes-devtools/go/go-1.17.13.inc | 1 +
...util-avoid-query-parameter-smuggling.patch | 178 ++
2 files changed, 179 insertions(+)
create mode 100644
meta/recipes-devtools/go/go-1.18/0001-net-htt
I can't see how anyone would be using this very old package function definition
since package.bbclass is always inherited in modern OE. All it seems to do
is waste CPU cycles. Drop it and it's associated EXPORT_FUNCTIONS entry.
Signed-off-by: Richard Purdie
---
meta/classes-global/base.bbclass |
bison-native is required if any .y-file is changed, by patch or in
devtool. Otherwise the build will fail with
/bin/bash /config/ylwrap /src/libkeymap/parser.y y.tab.c parser.c
y.tab.h `echo parser.c | sed -e s/cc$/hh/ -e s/cpp$/hpp/ -e s/cxx$/hxx/ -e
s/c++$/h++/ -e s/c$/h/` y.output pa
On Thu, 24 Nov 2022 at 14:44, Richard Purdie
wrote:
> Do we need special privileges to be able to run that?
No, you only need to build meta-ide-support as the scripts take nfsd
executable from sysroot of that (could be improved and available
directly from qemu's own sysroot).
Then it should simp
On Thu, 2022-11-24 at 14:35 +0100, Alexandre Belloni via
lists.openembedded.org wrote:
> On 24/11/2022 13:10:51+, Chen Qi wrote:
> > Hi Alexandre,
> >
> > The command line is: oe-selftest --skip-tests
> > distrodata.Distrodata.test_checkpkg
> > buildoptions.SourceMirroring.test_yocto_source_
On Thu, 2022-11-24 at 14:07 +0100, Alexander Kanavin wrote:
> On Tue, 22 Nov 2022 at 16:09, Richard Purdie
> wrote:
> > It would help, yes. If you do that it could be good to understand and
> > document which areas we do/don't have test coverage of some kind for as
> > we could then look at either
On 24/11/2022 13:10:51+, Chen Qi wrote:
> Hi Alexandre,
>
> The command line is: oe-selftest --skip-tests
> distrodata.Distrodata.test_checkpkg
> buildoptions.SourceMirroring.test_yocto_source_mirror reproducible -T machine
> -T toolchain-user -T toolchain-system -j 15
>
> The '--skip-test
Jason, can you please take a look if the changes here are ok?
And also help with the upstream submission, where upstream would like
to modify things?
https://github.com/unfs3/unfs3/pull/28
Also, what was the original use case for nfs in qemu? Is it still relevant?
Alex
On Wed, 23 Nov 2022 at 2
Hi Alexandre,
The command line is: oe-selftest --skip-tests
distrodata.Distrodata.test_checkpkg
buildoptions.SourceMirroring.test_yocto_source_mirror reproducible -T machine
-T toolchain-user -T toolchain-system -j 15
The '--skip-tests' option is the long format of '-R'.
Regards,
Qi
-Ori
On Tue, 22 Nov 2022 at 16:09, Richard Purdie
wrote:
> It would help, yes. If you do that it could be good to understand and
> document which areas we do/don't have test coverage of some kind for as
> we could then look at either adding it or dropping that support if it
> isn't used.
I sent a seco
On 24/11/2022 12:24:38+, Chen Qi wrote:
> Hi Alexandre,
>
> Yes, I'm aware of this behavior regression.
> With this patch, 'oe-selftest -R xxx' needs to be changed to 'oe-selftest -a
> -R xxx'.
>
Yes, my point is that there is no -R in the command line used by the AB
> I'm not sure if this
From: Vivek Kumbhar
Upstream-Status: Backport from
https://github.com/python/cpython/commit/eae692eed18892309bcc25a2c0f8980038305ea2
Signed-off-by: Vivek Kumbhar
---
.../python/python3/CVE-2022-42919.patch | 70 +++
.../recipes-devtools/python/python3_3.10.7.bb | 1 +
2
From: Vivek Kumbhar
Upstream-Status: Backport from
https://github.com/python/cpython/commit/eae692eed18892309bcc25a2c0f8980038305ea2
Signed-off-by: Vivek Kumbhar
---
.../python/python3/CVE-2022-42919.patch | 70 +++
.../recipes-devtools/python/python3_3.10.7.bb | 1 +
2
Hi Alexandre,
Yes, I'm aware of this behavior regression.
With this patch, 'oe-selftest -R xxx' needs to be changed to 'oe-selftest -a -R
xxx'.
I'm not sure if this is useful for other people. Because how people use
oe-selftest is unknown to me.
For me, I want to run something like 'oe-selftest
On Tue, 22 Nov 2022 at 16:21, Richard Purdie
wrote:
> I was going to say I was worried this introduces a reproducibility
> issue:
>
> https://autobuilder.yoctoproject.org/typhoon/#/builders/117/builds/1907
>
> however I see the failure we encountered is on the previous version :(
>
> Diffoscope f
Hello,
On 23/11/2022 18:55:28-0800, Chen Qi wrote:
> For now, there's no easy way to skip some specified tests when
> using 'oe-selftest -r'. This is because '-R' and '-r' are in the
> mutually exclusive group. Looking at the codes, the codes have already
> allowed running specified tests and skip
Distros can customize the location of OPKG data using OPKGLIBDIR. In
OE-Core commit 11f1956cf5d7 ("package_manager.py: define info_dir and
status_file when OPKGLIBDIR isn't the default"), a fix was applied to
correctly set the info_dir and status_file options relative to
OPKGLIBDIR.
However, as t
From: Mingli Yu
Add selinux PACKAGECONFIG logic in selinux layer[1] to conform
to yocto compliance.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=31325005e4409e08b7f68eed44a9c4086453e4dd
Signed-off-by: Mingli Yu
---
meta/recipes-extended/psmisc/psmisc.inc | 1 +
1 file changed, 1
From: Mingli Yu
Add selinux PACKAGECONFIG logic in selinux layer[1] to conform
to yocto compliance.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=31325005e4409e08b7f68eed44a9c4086453e4dd
Signed-off-by: Mingli Yu
---
meta/recipes-extended/cronie/cronie_1.6.1.bb | 1 +
1 file change
From: Mingli Yu
Add selinux PACKAGECONFIG logic in selinux layer[1] to conform
to yocto compliance.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=31325005e4409e08b7f68eed44a9c4086453e4dd
Signed-off-by: Mingli Yu
---
meta/recipes-core/util-linux/util-linux_2.38.1.bb | 1 +
1 file c
From: Mingli Yu
Add selinux and audit PACKAGECONFIG logic in selinux layer[1] to
conform to yocto compliance.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=31325005e4409e08b7f68eed44a9c4086453e4dd
Signed-off-by: Mingli Yu
---
meta/recipes-extended/sudo/sudo.inc | 2 ++
1 file chan
From: Mingli Yu
Add selinux PACKAGECONFIG logic in selinux layer[1] to conform
to yocto compliance.
[1]
https://git.yoctoproject.org/meta-selinux/commit/?id=31325005e4409e08b7f68eed44a9c4086453e4dd
Signed-off-by: Mingli Yu
---
meta/recipes-connectivity/iproute2/iproute2_6.0.0.bb | 1 +
1 fil
28 matches
Mail list logo
