Ok, thanks.
On Thu, Nov 7, 2019 at 8:50 PM Zhixiong Chi wrote:
>
>
>
> On 2019年11月08日 09:33, Khem Raj wrote:
> > On Wed, Nov 6, 2019 at 9:54 PM Zhixiong Chi
> > wrote:
> >> Since the Sun RPC is deprecated in glibc, the rpc header files
> >> are not provided any more, but it allows alternative
On 2019年11月08日 09:33, Khem Raj wrote:
On Wed, Nov 6, 2019 at 9:54 PM Zhixiong Chi wrote:
Since the Sun RPC is deprecated in glibc, the rpc header files
are not provided any more, but it allows alternative RPC
implementations, such as TIRPC or rpcsvc-proto, to be used.
So we create the
From: Chee Yang Lee
The Wic help returned to the user is unreadable.
Use a custom ArgumentParser to override argparse help message.
change help message as suggest in
https://bugzilla.yoctoproject.org/show_bug.cgi?id=12205
[YOCTO #12205]
changes applies to 'wic help', 'wic -h', 'wic --h' and
Get following patches
Detect recursive lock between yp_all() and do_ypcall()
Detect recursive NIS calls
Signed-off-by: Khem Raj
---
meta/recipes-extended/libnsl/libnsl2_git.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-extended/libnsl/libnsl2_git.bb
On Wed, Nov 6, 2019 at 9:54 PM Zhixiong Chi wrote:
>
> Since the Sun RPC is deprecated in glibc, the rpc header files
> are not provided any more, but it allows alternative RPC
> implementations, such as TIRPC or rpcsvc-proto, to be used.
>
> So we create the symbol link for rpc header files for
On Thu, Nov 7, 2019 at 12:55 PM Andreas Oberritter
wrote:
>
> Signed-off-by: Andreas Oberritter
> ---
> meta/recipes-core/systemd/systemd_243.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-core/systemd/systemd_243.bb
>
On Wed, Nov 6, 2019 at 11:33 PM Nathan Rossi wrote:
>
> On Thu, 7 Nov 2019 at 09:34, Adrian Bunk wrote:
> >
> > On Wed, Nov 06, 2019 at 10:18:18AM -0800, Alistair Francis wrote:
> > >...
> > > +TUNE_CCARGS_riscv64 .= "${@bb.utils.contains('TUNE_FEATURES',
> > > 'riscv64-f', ' -mabi=lp64d', '
Instead of depending on iasl-native, depend on ovmf-native as iasl was merged
into that recipe some time ago.
bc-native doesn't appear to be a build requirement anymore, and for clarity
merge two overridden DEPENDS into a single DEPENDS.
Signed-off-by: Ross Burton
---
This has been merged to master now, so mark as a backport.
Signed-off-by: Ross Burton
---
...01-Do-not-enforce-no-introspection-when-cross-building.patch | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
We already fetch the yearly CVE metadata and check that for updates before
downloading the full data, but we can speed up CVE checking further by only
checking the CVE metadata once an hour.
Signed-off-by: Ross Burton
---
meta/recipes-core/meta/cve-update-db-native.bb | 10 +-
1 file
The upstream tarballs now have a unified source license of Intel|BSD|GPLv2 and
the old BSD|GPLv2 tarballs are deprecated.
Add the Intel license to the license collection, update the LICENSE field, and
update the license checksum to actually point at a license fragment.
Signed-off-by: Ross Burton
The patch scanner works with patch files in the layer, not in the workdir, so it
doesn't need to unpack.
Signed-off-by: Ross Burton
---
meta/classes/cve-check.bbclass | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/meta/classes/cve-check.bbclass
This allows the eSDK w/o integrated builtools.
Enabled with: SDK_INCLUDE_BUILDTOOLS = '0'
qemux86-64 - core-image-minimal - eSDK sizes
Regular eSDK - 838 MB
Minimal eSDK - 34 MB
Min w/o bts - 11 MB
So it's a fairly significant drop in download size for the eSDK.
Mark Hatle (1):
If the host system is expected to have enough capabilities that the
buildtools-tarball is not required, we don't need to bundle it.
This can save some significant space, especially when using with a minimal
eSDK.
minimal eSDK - core-image-minimal-qemux86-64
with buildtools-tarball - 34 MB
Fix "systemd-pstore: Failed to log pstore entry: Invalid argument"
by backporting 1b3156edd291e0882d80a695d035dd30521345d1 from upstream.
Signed-off-by: Yongxin Liu
---
.../systemd/0001-pstore-fix-use-after-free.patch | 39 ++
meta/recipes-core/systemd/systemd_243.bb
== Series Details ==
Series: dhcp: Workaround busybox limitation in Linux dhclient-script
Revision: 1
URL : https://patchwork.openembedded.org/series/21031/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several
Busybox's implementation of chown and chmod doesn't provide a
"--reference" option used in the latest version of dhclient-script.
This change works around that limitation by using stat to read
ownership and permissions flags and simple chown/chmod calls
supported in both coreutils and busybox.
Pass `--checksum md5` and `--checksum sha256` to opkg-make-index.
Sha256 checksum enables more reliable install-time validation of IPKs.
This is particularly useful when installing from signed feeds --
I.e. feeds using signed Packages index files that deliver otherwise
unsigned IPKs. Such feeds
Enable nativesdk builds of gnupg and it's dependencies (libksba, npth,
and pinentry) to fix builds of nativesdk-opkg.
This is necessary on distribution which enable gpg signature
verification in opkg and also build SDK images that include opkg.
Signed-off-by: Haris Okanovic
---
gnupg-gpg is a minimal installation of gnupg with enough functionality
to verify signatures and manage keys. Use this package instead of full
gnupg to slim down opkg installations with "--enable-gpg".
Signed-off-by: Haris Okanovic
---
meta/recipes-devtools/opkg/opkg_0.4.1.bb | 5 -
1 file
Add minimal "gnupg-gpg" package containing just enough binaries to run
gpg and gpg-agent. Add dependency in normal "gnupg" package to preserve
old behavior.
Some applications like opkg don't need all functionality provided by
normal gnupg installations. This minimal package provides just enough
On Thu, 2019-11-07 at 15:41 +, André Draszik wrote:
> On Thu, 2019-11-07 at 14:08 +, Richard Purdie wrote:
> > On Thu, 2019-11-07 at 14:01 +, André Draszik wrote:
> > > On Thu, 2019-11-07 at 13:26 +0100, Alexander Kanavin wrote:
> > > > I would rather keep the option to disable
Signed-off-by: Andreas Oberritter
---
meta/recipes-core/systemd/systemd_243.bb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/recipes-core/systemd/systemd_243.bb
b/meta/recipes-core/systemd/systemd_243.bb
index 6e7f95693b..54fcc6a5d1 100644
---
Now that ldconfig may get installed from a feed, use it when it's
available on the target.
Signed-off-by: Andreas Oberritter
---
meta/classes/package.bbclass | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/meta/classes/package.bbclass b/meta/classes/package.bbclass
index
Only recommend its installation, if it's enabled in distro features.
Signed-off-by: Andreas Oberritter
---
meta/recipes-core/glibc/glibc-package.inc | 11 ---
1 file changed, 4 insertions(+), 7 deletions(-)
diff --git a/meta/recipes-core/glibc/glibc-package.inc
On Thu, 2019-11-07 at 14:34 -0600, Seebs wrote:
> On Thu, 7 Nov 2019 20:04:44 +
> Richard Purdie wrote:
>
> > Modern distros (e.g. fedora30) are starting to use the new statx()
> > syscall through the newly exposed glibc wrapper function in
> > software
> > like coreutils (e.g. the ls
On Thu, 7 Nov 2019 20:04:44 +
Richard Purdie wrote:
> Modern distros (e.g. fedora30) are starting to use the new statx()
> syscall through the newly exposed glibc wrapper function in software
> like coreutils (e.g. the ls command). Add support to intercept this
> to pseudo.
I think this
== Series Details ==
Series: Add statx glibc/syscall support
Revision: 1
URL : https://patchwork.openembedded.org/series/21022/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on
Modern distros (e.g. fedora30) are starting to use the new statx() syscall
through
the newly exposed glibc wrapper function in software like coreutils (e.g. the ls
command). Add support to intercept this to pseudo.
Signed-off-by: Richard Purdie
---
ports/linux/guts/statx.c | 48
Modern distros (e.g. fedora30) are starting to use the new statx() syscall
through
the newly exposed glibc wrapper function in software like coreutils (e.g. the ls
command). Add support to intercept this to pseudo.
Signed-off-by: Richard Purdie
---
.../pseudo/files/0001-Add-statx.patch
On Wed, 2019-11-06 at 20:12 -0500, Denys Dmytriyenko wrote:
> From: Denys Dmytriyenko
>
> Fix parentheses placement in the message from:
> Package version for package X went backwards which would break package feeds
> from (Y to Z)
> to this one:
> Package version for package X went backwards
Add "esp_extra_blocks" plugin parameter so that caller may change
ESP's free space from the default 100 blocks.
Signed-off-by: Haris Okanovic
---
scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Add "esp_label" plugin parameter so that caller may override default
ESP partition label 'EFIimg'.
Signed-off-by: Haris Okanovic
---
scripts/lib/wic/plugins/source/isoimage-isohybrid.py | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
Without this change, efibootmgr is unable to recover BootOrder if lost
during a previous write operation, e.g. exceeded storage capacity. This
is problematic using EFI to manage boot flow from Linux (E.g. via RAUC).
https://www.kernel.org/doc/Documentation/filesystems/efivarfs.txt
Signed-off-by:
OpenEmbedded is considering creating a mini-conference attached to
FOSDEM 2020 (https://fosdem.org/2020/), and we would like your help.
Please fill out this short, 10 question, survey to determine the
viability of such an effort.
https://www.surveymonkey.com/r/9QP76CL
Thank you,
The OpenEmbedded
On Thu, 2019-11-07 at 07:55 -0800, akuster808 wrote:
>
> On 11/7/19 7:03 AM, Richard Purdie wrote:
> > On Wed, 2019-11-06 at 13:46 -0800, akuster808 wrote:
> > > On 11/6/19 7:37 AM, Mikko Rapeli wrote:
> > > QA resources have been a donation from Intel and Windriver above
> > > their membership
Adds an option that can be used to copy the offending packages to a temp
directory for later evaluation. This is useful on the Autobuilder to
investigate failures.
Signed-off-by: Joshua Watt
---
meta/lib/oeqa/selftest/cases/reproducible.py | 20
1 file changed, 20
On 11/7/19 7:03 AM, Richard Purdie wrote:
> On Wed, 2019-11-06 at 13:46 -0800, akuster808 wrote:
>> On 11/6/19 7:37 AM, Mikko Rapeli wrote:
>> QA resources have been a donation from Intel and Windriver above
>> their membership fees. I don't fee right asking them to run QA.
>>> patches aiming
On Thu, 2019-11-07 at 14:08 +, Richard Purdie wrote:
> On Thu, 2019-11-07 at 14:01 +, André Draszik wrote:
> > On Thu, 2019-11-07 at 13:26 +0100, Alexander Kanavin wrote:
> > > I would rather keep the option to disable openssl, but simply
> > > switch it on by default
> >
> > Why
libevent produces several libraries that might or might not
be used in the end. We can prevent those potentially unused
libraries from being pulled into a file-system by splitting
the individual shared libraries into individual packages.
Because this recipe only provides shared libraries which
* Instead of overwriting the stamp name with 'dummy', handle
setscene promotion in the default case block
* Merge '*do_image_complete_setscene*' and '*do_image_qa_setscene*'
case handling
Signed-off-by: Jacob Kroon
---
meta/classes/rm_work.bbclass | 49 +++-
On Wed, 2019-11-06 at 13:46 -0800, akuster808 wrote:
> On 11/6/19 7:37 AM, Mikko Rapeli wrote:
> QA resources have been a donation from Intel and Windriver above
> their membership fees. I don't fee right asking them to run QA.
> > patches aiming at yocto 2.5 sumo. If not, would be really nice
When we try to build images for machine which is tuned for
cortex-a32, then libgcc-initial recipe fails to build with
below error message.
-- snip --
configure:3529: aarch64-poky-linux-gcc -mcpu=cortex-a32+crc
-fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
On Thu, Nov 07, 2019 at 12:13:51PM +, mikko.rap...@bmw.de wrote:
> Hi,
Hi Mikko,
> On Thu, Nov 07, 2019 at 01:13:32PM +0200, Adrian Bunk wrote:
> > On Wed, Nov 06, 2019 at 05:37:15PM +0200, Mikko Rapeli wrote:
> > > Hi,
> >
> > Hi Mikko,
> >
> > >...
> > > I use sumo and due to various
On Thu, 2019-11-07 at 14:01 +, André Draszik wrote:
> On Thu, 2019-11-07 at 13:26 +0100, Alexander Kanavin wrote:
> > I would rather keep the option to disable openssl, but simply
> > switch it on by default
>
> Why complicate things, what's the use-case? If libevent_openssl.so is
> not
>
On Thu, 2019-11-07 at 13:26 +0100, Alexander Kanavin wrote:
> I would rather keep the option to disable openssl, but simply switch it on by
> default
Why complicate things, what's the use-case? If libevent_openssl.so is not
used by anything, that library will not be pulled in, as it is a
harfbuzz binary package size increased from 624608 bytes in yocto 2.5 to
1365431 bytes in yocto 3.0. Most of the size increase is in the new
libharfbuzz-subset.so* library
https://harfbuzz.github.io/utilities.html#utilities-command-line-hbsubset
Split it to its own binary package which will be
On Thu, Nov 07, 2019 at 10:54:23AM +, Ross Burton wrote:
> On 07/11/2019 08:13, Mikko Rapeli wrote:
> > harfbuzz binary package size increased from 624608 bytes in yocto 2.5 to
> > 1365431 bytes in yocto 3.0. Most of the size increase is in the new
> > libharfbuzz-subset.so* library, which
== Series Details ==
Series: Fix libgcc-initial build issue for cortex-a32
Revision: 1
URL : https://patchwork.openembedded.org/series/21007/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
Hi,
On Thu, Nov 07, 2019 at 01:13:32PM +0200, Adrian Bunk wrote:
> On Wed, Nov 06, 2019 at 05:37:15PM +0200, Mikko Rapeli wrote:
> > Hi,
>
> Hi Mikko,
>
> >...
> > I use sumo and due to various reasons like BSP layers, binary
> > compatibility, contracts etc can't update to newer release
> > or
I would rather keep the option to disable openssl, but simply switch it on
by default.
Alex
On Thu, 7 Nov 2019 at 13:11, André Draszik wrote:
> The original commit describes the reason for disabling openssl
> so as to get 'more deterministic build[s]' and size-reduction:
> commit 6c36fde6ce2e
On Wed, Nov 06, 2019 at 05:37:15PM +0200, Mikko Rapeli wrote:
> Hi,
Hi Mikko,
>...
> I use sumo and due to various reasons like BSP layers, binary
> compatibility, contracts etc can't update to newer release
> or to master branch. I suspect I'm not alone.
I might end up with similar reasons,
When we try to build images for machine which is tuned for
cortex-a32, then libgcc-initial recipe fails to build with
below error message.
-- snip --
configure:3529: aarch64-poky-linux-gcc -mcpu=cortex-a32+crc
-fstack-protector-strong -D_FORTIFY_SOURCE=2 -Wformat -Wformat-security
On 07/11/2019 08:13, Mikko Rapeli wrote:
harfbuzz binary package size increased from 624608 bytes in yocto 2.5 to
1365431 bytes in yocto 3.0. Most of the size increase is in the new
libharfbuzz-subset.so* library, which based on the name seems to
duplicate parts of the libharfbuzz main library,
On Thu, 7 Nov 2019 at 07:59, wrote:
> Hi,
>
> On Wed, Nov 06, 2019 at 05:53:27PM +, Richard Purdie wrote:
> > On Wed, 2019-11-06 at 16:06 +, mikko.rap...@bmw.de wrote:
> > > Hi,
> > >
> > > On Wed, Nov 06, 2019 at 02:59:16PM +, Ryan Harkin wrote:
> > > > Hi Ross/Richard,
> > > >
> >
Add total passed, failed, and skipped statistic to test result.
Signed-off-by: Yeoh Ee Peng
---
scripts/lib/resulttool/report.py | 5 +
scripts/lib/resulttool/template/test_report_full_text.txt | 3 ++-
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git
Enable the option to add extra test environment data to the
configuration of each test result (as optional).
Example of optional test environment data include:
- custom packages included for runtime test
- detail machine specification used as target
- detail host
In case of debugging, report user need to acccess the raw
test result. Instead of going back to source file/directory/URL
to manually pull out the raw result, provide alternative
way to let report showing raw test results by providing
the result id (optional).
Signed-off-by: Yeoh Ee Peng
---
By default, report will use the store_map to generate the key
to reference each result set. In some situation when using store_map
with multiple set of tests sharing similar test configurations,
the report will only showing partial result set for results
that having identical result_id (use of
The original commit describes the reason for disabling openssl
so as to get 'more deterministic build[s]' and size-reduction:
commit 6c36fde6ce2e ("libevent: disable openssl by default"),
commit ad130b97a51a in poky.
Since the introduction of per-recipe sysroots, we always have
deterministic
Resulttool minor enhancements
- Enable report to use regression_map
- Enable report to output raw test results
- Enable report to print total test result statistic
- Enable store to add extra test environment config data
Yeoh Ee Peng (4):
scripts/resulttool/report: Enable report to use
On Wed, Nov 06, 2019 at 04:55:05PM -0800, Khem Raj wrote:
> On Wed, Nov 6, 2019 at 4:48 PM Alistair Francis
> wrote:
>...
> > -march is another can of worms that I was trying to avoid. I don't have
> > a good way of handling the ISA strings at the moment without some crazy
> > number of tune
Signed-off-by: Changhyeok Bae
---
.../ethtool/ethtool/avoid_parallel_tests.patch | 6 +++---
.../ethtool/{ethtool_5.2.bb => ethtool_5.3.bb} | 4 ++--
2 files changed, 5 insertions(+), 5 deletions(-)
rename meta/recipes-extended/ethtool/{ethtool_5.2.bb =>
Hi,
On Wed, Nov 06, 2019 at 01:46:09PM -0800, akuster808 wrote:
> Hello Mikko;
> I have collected other patches for sumo and built them locally but I
> have no way to inform Richard they pass an AB builds or automated
> testing for them to get into mainline sumo.
>
> I am placing them into
>
Signed-off-by: Changhyeok Bae
---
.../iproute2/{iproute2_5.2.0.bb => iproute2_5.3.0.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/iproute2/{iproute2_5.2.0.bb =>
iproute2_5.3.0.bb} (65%)
diff --git
On 2019-11-07 09:01, Richard Purdie wrote:
> On Wed, 2019-11-06 at 13:43 +, Stefan Agner wrote:
>> From: Stefan Agner
>>
>> Add Zstandard (or just Zstd) compression support. This allows to
>> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
>>
>> Signed-off-by: Stefan Agner
harfbuzz binary package size increased from 624608 bytes in yocto 2.5 to
1365431 bytes in yocto 3.0. Most of the size increase is in the new
libharfbuzz-subset.so* library, which based on the name seems to
duplicate parts of the libharfbuzz main library, though it
RDEPENDS on harfbuzz which is
Hi,
On Wed, Nov 06, 2019 at 05:53:27PM +, Richard Purdie wrote:
> On Wed, 2019-11-06 at 16:06 +, mikko.rap...@bmw.de wrote:
> > Hi,
> >
> > On Wed, Nov 06, 2019 at 02:59:16PM +, Ryan Harkin wrote:
> > > Hi Ross/Richard,
> > >
> > > I'd like this applied to Sumo also. Should I create
On Wed, 2019-11-06 at 13:43 +, Stefan Agner wrote:
> From: Stefan Agner
>
> Add Zstandard (or just Zstd) compression support. This allows to
> create Zstd compressed tarballs by using tar.zst as IMAGE_FSTYPES.
>
> Signed-off-by: Stefan Agner
> ---
> meta/classes/image_types.bbclass | 8
69 matches
Mail list logo
