linux/poky.git/meta, branch yocto-2.5.2

build-appliance-image: Update to sumo head revision

2018-12-05T22:35:24+00:00

(From OE-Core rev: 6637f400fb01501353f376d73658b359cedfa3c2) Signed-off-by: Richard Purdie

sanity: Add check for WSL

2018-12-05T22:34:00+00:00

Users are starting to expect OE to work under WSL which it doesn't. Add a warning to tell them about this up front and manage expectations. (From OE-Core rev: 4f22710f9a310412f1de0b4e6905c058ec416f25) (From OE-Core rev: 33a577864123833d7d8182fe90df7069fc583bc6) Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

busybox: make busybox.links.{suid, nosuid} reproducible

2018-12-05T22:34:00+00:00

The busybox.link.* files are generated from autoconf.h and applets.h, which are both auto-generated by the build system. The contents of the two files might be in different order, and so the link files are not reproducble as is. Fix this by sorting the lists using `sort`. (From OE-Core rev: bade7cc344c2f0e9316f973c34e9c9dfcbdbe32d) (From OE-Core rev: 0f70da971e6e01ed9b669137b3ba39b1898a7dfe) Signed-off-by: Martin Hundebøll Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

shadow: improve reproducibility by hard-coding shell path

2018-12-05T22:34:00+00:00

The shadow configure script tries really hard to detect the running shell to make sure it doesn't do unsupported calls. On my system the shell is detected as /bin/sh, while a build in an ubuntu docker it resolves to /bin/bash. And since the shell path is baked into the target binaries through config.h, the build becomes inreproducible. Fix reproducibility by hard-coding the shell to be /bin/sh (From OE-Core rev: 5f4fe91cb6c21cd3ecd0b68d1c6b46a9530c7570) (From OE-Core rev: 83214b835cd82d5dddb47c418c4e7a20ac433f61) Signed-off-by: Martin Hundebøll Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

socat: fix LICENSE

2018-12-05T22:34:00+00:00

According to both the README and source headers, the LICENSE value for socat is explicitly GPLv2, not v2 or later, so adjust LICENSE accordingly (leaving aside whether "GPL-2.0+-with-OpenSSL-exception" should actually be considered a valid LICENSE string or not). (From OE-Core rev: 466044a341a8b42159bd9388950c9079e0d7a2c3) (From OE-Core rev: caa0b85cecf37945d67d5844c772a11ed790f8a5) Signed-off-by: Paul Eggleton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

gnupg: patch gnupg-native to allow path relocation

2018-11-24T21:49:51+00:00

GnuPG hard-codes $bindir etc and uses them to find the helper binaries, such as gpg-agent. This breaks if gnupg-native is reused from sstate for a different build directory and GPG signing of packages is required. Patch in getenv() checks for gnupg-native when returning the hardcoded paths, and create a wrapper script which overrides GNUPG_BINDIR. There are more paths that can be overridden, but this one is sufficient to make GnuPG work. (From OE-Core rev: dfd69ff889ed78bf137116583d8ae351859ee203) (From OE-Core rev: ddaf41f210f80556eca1d0acaee1e3f9cbf80122) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie

dhcp: allow for excluding the external bind

2018-11-24T21:45:58+00:00

There is a known issue when using ISC DHCP alongside bind 9.10. DHCP uses libraries provided by bind and there is a bug which results in dhcpd/dhclient not running in the background and not responding to sigterm. The issue was first reported in 02/2015 by the fedora team here: https://lists.isc.org/pipermail/bind-users/2015-February/094636.html and as of 02/2018 it is still unresolved: https://bugzilla.redhat.com/show_bug.cgi?id=1457871 Fedora's workaround seems to consist of providing working libraries from the bind 9.9 package just for DHCP. added 'ext-bind' in PACKACGECONFIG added notes on how to enable the workaround refreshed patches too [ Yocto # 12744 ] (From OE-Core rev: 1c35c68da07ccca5d80820e2de51c0b6bf51b349) Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

curl: actually apply latest CVE patches

2018-11-24T21:45:58+00:00

(From OE-Core rev: f0394e80a37f1da47042a1aa0487594f390603f9) (From OE-Core rev: b2ccfeeffc5762648ee6b1f1d05c3cc6f347ed28) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

unzip: actually apply CVE-2018-18384

2018-11-24T21:45:58+00:00

(From OE-Core rev: d8e1b7afc536f989e7e6efdab0998d54f26ad1f6) (From OE-Core rev: 1a42e6401369ffaf02f4711c01f757007f831cc8) Signed-off-by: Ross Burton Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie

oeqa/selftest/recipetool: Fix problems from changing upstream source

2018-11-24T21:45:58+00:00

The upstream source tarball checksums changed. Use the copy from our source mirror to avoid failures. [YOCTO #12979] (From OE-Core rev: e97a31e6bbaec5cb56d4750bf5171dbba510ee33) (From OE-Core rev: d637eea4af8b538fb45056f0022975d7c41cdf5f) Signed-off-by: Mohamad Noor Alim Hussin Signed-off-by: Richard Purdie Signed-off-by: Armin Kuster Signed-off-by: Richard Purdie