[OE-core] core-image-weston testimage fails

2020-09-04 Thread Khem Raj
Hi Alex I am seeing below error with core-image-weston/qemuarm64 using oe-core master. Any ideas before I debug this? NOTE: == NOTE: FAIL: test_weston_can_initialize_new_wayland_compositor (weston.WestonTest) NOTE: --

[OE-core] [PATCH v2] help2man: rewrite recipe

2020-09-04 Thread Ross Burton
This recipe was originally explicitly minimal because it was needed to bootstrap autotools, but that isn't the case anymore. Instead of being explicitly native, use BBCLASSEXTEND. No need to explicitly depend on autoconf-native automake-native, because the autotools class does that. As this reci

Re: [OE-core] [PATCH] rootfs-postcommands.bbclass: make /etc/timestamp path configurable

2020-09-04 Thread Richard Purdie
On Fri, 2020-09-04 at 09:08 +0200, Rasmus Villemoes wrote: > Not every image necessarily wants a timestamp file, Wouldn't you just not have rootfs_update_timestamp in ROOTFS_POSTPROCESS_COMMAND in that case? > and even if it does, it's possible to create filesystem images that do not > have a >

Re: [OE-core] [PATCH 7/8] bind: Add 9.16.x

2020-09-04 Thread Andrey Zhizhikin
Hello Armin, On Tue, Sep 1, 2020 at 5:23 PM akuster wrote: > > Removed obsolete packageconfig options > > License change to MPL-2.0 > https://gitlab.isc.org/isc-projects/bind9/blob/master/LICENSE > > Refreshed: > bind-ensure-searching-for-json-headers-searches-sysr.patch > 0001-named-lwresd-V-and

[OE-core] [PATCH] rootfs-postcommands.bbclass: make /etc/timestamp path configurable

2020-09-04 Thread Rasmus Villemoes
Not every image necessarily wants a timestamp file, and even if it does, it's possible to create filesystem images that do not have a /etc directory or where some other location for the file is more appropriate. So add a ROOTFS_TIMESTAMP_FILE variable weakly defaulting to /etc/timestamp - setting t