util-linux ptest requires the scsi_debug module to perform eject/mount
tests. This will conditionally add scsi_debug module when ptest is in
DISTRO_FEATURES.
This doesn't include linux-yocto-tiny because the resulting image will
be too big and do_image would complain about this.
[YOCTO #13301]
These patches will allow the use of scsi-debug kernel module for
eject/mount related tests of the util-linux package.
The following changes since commit e00d88475d0ed7b161f5f58dd13bc9a72e3efdf9:
bluez: fix test case failures with GCC 9 (2019-06-12 21:08:52 +0100)
are available in the Git
The util-linux's ptest uses the SCSI_DEBUG kernel module to create
virtual SCSI disks. The automount feature of udevd will try to mount
these disks by default. Because udevd controls the mount of the disks,
the eject/mount tests will fail or be skipped. This change will stop
udevd before executing
From: Mingli Yu
Signed-off-by: Mingli Yu
---
.../dbus/{dbus-test_1.12.14.bb => dbus-test_1.12.16.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/dbus/{dbus-test_1.12.14.bb => dbus-test_1.12.16.bb}
(95%)
diff --git
From: Mingli Yu
Security fixes:
CVE-2019-12749
Signed-off-by: Mingli Yu
---
meta/recipes-core/dbus/{dbus_1.12.14.bb => dbus_1.12.16.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-core/dbus/{dbus_1.12.14.bb => dbus_1.12.16.bb} (97%)
diff --git
On 6/12/19 10:52 PM, Jonathan Rajotte-Julien wrote:
> Hi,
>
>>> Please don't base distributions on -rc tags. They are not meant for this.
>>>
>>> We always integrate support for newer kernel versions instrumentation back
>>> into our current stable release. So as soon as 5.2 final comes out, we
On 6/12/19 8:36 PM, Richard Purdie wrote:
> On Wed, 2019-06-12 at 19:12 +0800, zhe...@windriver.com wrote:
>> From: He Zhe
>>
>> The git based recipe is for those who want to build lttng-modules with
>> bleeding
>> edge kernel, to avoid regularly backporting patches from upstream.
>>
>> Note
From: Kai Kang
Add bison-native to DEPENDS of qemu and qemu-system-native to fix
compile warning:
| BISON dtc-parser.tab.c
| make[1]: bison: Command not found
Signed-off-by: Kai Kang
---
meta/recipes-devtools/qemu/qemu-system-native_4.0.0.bb | 2 +-
AArch64 images are not self-decompressing, thus usually much larger.
Boot times can be reduced by compressing them in FIT and uImages.
Signed-off-by: Laurent Bonnans
---
meta/classes/kernel-uboot.bbclass | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi, Alex
I refered to the previous patches. Should the Upstream-Status be “Submitted” ?
Best regards
Lei
From: Alexander Kanavin [mailto:alex.kana...@gmail.com]
Sent: Thursday, June 13, 2019 8:45 PM
To: Burton, Ross
Cc: Lei, Maohui/雷 茂慧; Hong Liu; OE-core
Subject: Re: [OE-core] [PATCH]
Hi, Ross
Thank you. I got it. I will submit v2 patch.
Best regards
Lei
> -Original Message-
> From: Burton, Ross [mailto:ross.bur...@intel.com]
> Sent: Thursday, June 13, 2019 5:24 PM
> To: Lei, Maohui
> Cc: OE-core; Hong Liu
> Subject: Re: [OE-core] [PATCH] openssl: Fix a build bug on
== Series Details ==
Series: bitbake: cooker: list all nonexistent bblayer directories
Revision: 1
URL : https://patchwork.openembedded.org/series/18148/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
This is how it'll look like:
ERROR: Unable to start bitbake server (None)
ERROR: Server log for this session
(/home/sashko/projects/yocto/open-embedded/build/bitbake-cookerdaemon.log):
--- Starting bitbake server pid 7414 at 2019-06-14 01:35:10.070371 ---
ERROR: The following layer directories do
Check existence of all the bblayer direcotories at once and print them
all, so if there are multiple nonexistent directories, user does not
have to correct bblayers.conf and restart bitbake multiple times.
[YOCTO #11647]
Signed-off-by: Oleksandr Kravchuk
---
bitbake/lib/bb/cookerdata.py | 16
From: Oleksandr Kravchuk
PyPi packages are now hosted at files.pythonhosted.org.
[YOCTO #13243]
Signed-off-by: Oleksandr Kravchuk
---
meta/lib/oeqa/selftest/cases/devtool.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/selftest/cases/devtool.py
- Drop 0001-opkg-build-do-not-set-mtime-on-data.tar.X.patch
- Drop 0001-opkg-list-fields-fix-to-print-the-fields-again.patch
Signed-off-by: Alejandro del Castillo
---
...build-do-not-set-mtime-on-data.tar.X.patch | 33 ---
...fields-fix-to-print-the-fields-again.patch | 41
- Drop 0001-libopkg-add-add-ignore-recommends-option.patch
- Drop 0001-opkg-add-target-for-testsuite-installation.patch
- Drop 0001-regress-issue72.py-resolve-paths-before-comparision.patch
Signed-off-by: Alejandro del Castillo
---
...pkg-add-add-ignore-recommends-option.patch | 259
Alejandro del Castillo (2):
opkg: upgrade to version 0.4.1
opkg-utils: upgrade to version 0.4.1
...build-do-not-set-mtime-on-data.tar.X.patch | 33 ---
...fields-fix-to-print-the-fields-again.patch | 41 ---
...pkg-utils_0.4.0.bb => opkg-utils_0.4.1.bb} | 6 +-
Sure, follow-up patch is fine with me.
On Thu, Jun 13, 2019 at 8:38 PM Marco Felsch
wrote:
> Hi Martin,
>
> On 19-06-13 20:17, Martin Jansa wrote:
> > Looks like nice cleanup, but is someone still using llvm 3.2 or older?
>
> I don't know but I learned to avoid breaking changes.
>
> > With
Hi Martin,
On 19-06-13 20:17, Martin Jansa wrote:
> Looks like nice cleanup, but is someone still using llvm 3.2 or older?
I don't know but I learned to avoid breaking changes.
> With PACKAGECONFIG for almost each gallium driver it might be easier to get
> rid
> of GALLIUMDRIVERS_LLVM33,
Looks like nice cleanup, but is someone still using llvm 3.2 or older?
With PACKAGECONFIG for almost each gallium driver it might be easier to get
rid
of GALLIUMDRIVERS_LLVM33, GALLIUMDRIVERS_LLVM33_ENABLED, GALLIUMDRIVERS_LLVM
variables and use just GALLIUMDRIVERS.
In worst case scenario people
On 19-06-13 18:00, Patchwork wrote:
> == Series Details ==
>
> Series: kernel: install modules.builtin.modinfo file
> Revision: 1
> URL : https://patchwork.openembedded.org/series/18144/
> State : failure
Sorry for the noise, didn't recognized that it is already fixed.
Regards,
Marco
> ==
== Series Details ==
Series: kernel: install modules.builtin.modinfo file
Revision: 1
URL : https://patchwork.openembedded.org/series/18144/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
With kernel 5.2 a file is created which stores informations about the
builtin modules, for more information see [1]. Without this patch a Q/A
issue will be thrown.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/ \
linux.git/commit/Documentation/kbuild/ \
Just as for the swrast target it isn't a good solution to enable the
target per default since we are compiling for embedded targets most of
the time. Make this target optional for all hardware targets except
qemu to save resources.
Signed-off-by: Marco Felsch
---
v3:
- rebased on current
Most of the time we are compiling for embedded targets which have
dedicated hardware combinations. Enabling swrast by default isn't a good
solution for such devices because if the hardware render node has an
issue or doesn't support a special format/request Mesa will fallback to
the software
Also if the patch is already submitted, the status should not be Pending.
Alex
On Thu, 13 Jun 2019 at 11:23, Burton, Ross wrote:
> On Thu, 13 Jun 2019 at 09:48, Lei Maohui wrote:
> >
> > From: Hong Liu
> >
> > Fix bug as following on aarch64BE:
> >
> > Error: operand 1 must be an integer
On 6/13/19 6:07 PM, Burton, Ross wrote:
Are you going to fix all of the other recipes? Very few recipes let
you run the tests from an arbitrary directory, and assume that you're
in the test directory already.
Only focus on this recipe, my original task is to resolve 2. Fix
large-subopt.in1
Are you going to fix all of the other recipes? Very few recipes let
you run the tests from an arbitrary directory, and assume that you're
in the test directory already.
Ross
On Thu, 13 Jun 2019 at 09:08, Hongxu Jia wrote:
>
> 1. Run run-ptest at arbitrary path
>
> 2. Fix large-subopt.in1 not
On Thu, 13 Jun 2019 at 09:48, Lei Maohui wrote:
>
> From: Hong Liu
>
> Fix bug as following on aarch64BE:
>
> Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
>
> Upstream-Status: Pending [https://github.com/openssl/openssl/pull/9151]
This line ^^^
> Signed-off-by: Lei
Sorry, I was failing to read the patch of the patch. :)
Ross
On Thu, 13 Jun 2019 at 02:57, Lei, Maohui wrote:
>
> Hi Ross
>
> > You do more than fix a spelling mistake in that commit. Please
> > explain the other changes.
>
> I'm sorry, I don't understand. I just fixed "acount" to "account". I
== Series Details ==
Series: openssl: Fix a build bug on aarch64BE. (rev3)
Revision: 3
URL : https://patchwork.openembedded.org/series/18134/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
From: Hong Liu
Fix bug as following on aarch64BE:
Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
Upstream-Status: Pending [https://github.com/openssl/openssl/pull/9151]
Signed-off-by: Lei Maohui
---
...01-Fix-build-error-for-aarch64-big-endian.patch | 41
HI, Burton:
Thanks for the comments, will do a V3.
the best,
thank you
Burton, Ross 於 2019年6月12日 週三 下午5:47寫道：
> I didn't make myself clear. To reduce the amount of moving parts and
> changes I propose:
>
> 1) libx11 and libx11-diet are untouched
> 2) New recipe libx11-compose-data which just
== Series Details ==
Series: openssl: Fix a build bug on aarch64BE. (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/18134/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
From: Martin Jansa
* bc can be provided by busybox as well (e.g. if you have your own
defconfig and forget to explicitly disable it:
...
*
* Miscellaneous Utilities
*
adjtimex (4.7 kb) (ADJTIMEX) [N/y/?] n
bbconfig (9.7 kb) (BBCONFIG) [N/y/?] n
bc (45 kb) (BC) [Y/n/?] (NEW) dc
Fix bug as following on aarch64BE:
Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
Upstream-Status: Pending [https://github.com/openssl/openssl/pull/9151]
Signed-off-by: Lei Maohui
---
...01-Fix-build-error-for-aarch64-big-endian.patch | 41 ++
1. Run run-ptest at arbitrary path
2. Fix large-subopt.in1 not found
...
|diff: /lib32-diffutils/3.7-r0/build/../diffutils-3.7/tests/large-subopt.in1:
No such file or directory
|diff: /lib32-diffutils/3.7-r0/build/../diffutils-3.7/tests/large-subopt.in2:
No such file or directory
...
== Series Details ==
Series: openssl: Fix a build bug on aarch64BE.
Revision: 1
URL : https://patchwork.openembedded.org/series/18134/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Fix bug as following on aarch64BE:
Error: operand 1 must be an integer register -- `rev v31.16b,v31.16b'
Upstream-Status: Pending [https://github.com/openssl/openssl/pull/9151]
Signed-off-by: Lei Maohui
---
...01-Fix-build-error-for-aarch64-big-endian.patch | 41 ++
From: Chee Yang Lee
Allow plugin bootimg-efi to configure with multiple initrd
through source parameter.
Uses ; to separate each initrd.
e.g:
--sourceparams="loader=${EFI_PROVIDER},initrd=initrd1;initrd2"
Signed-off-by: Chee Yang Lee
---
scripts/lib/wic/plugins/source/bootimg-efi.py | 24
Building `systemd-resolve` from systemd 242 with OpenSSL 1.1.1c and enabling
DNS over TLS ends up calling abort (on 32 bit armhf):
Program terminated with signal SIGABRT, Aborted.
#0 __libc_do_syscall () at libc-do-syscall.S:49
49libc-do-syscall.S: No such file or directory.
(gdb)
42 matches
Mail list logo
