[OE-core] [PATCH 0/6 v2] Fix RPM4 regressions based on Pyro

[Mark Hatle]

On 8/16/17 8:34 AM, Richard Purdie wrote:
> On Tue, 2017-08-15 at 16:41 -0500, Mark Hatle wrote:
>> From the comments to the original patch, the only not addressed was
>> adding an OE self-test for this behavior.  I tried to do this, but I
>> don't see any existing tests that build a recipe and inspect the
>> results of the built package.  I'm not sure of any other way to
>> identify if things are working or not.
> 
> oe-selftest can do this.
> 
>> I have built and tested this for:
>>
>> core-image-base core-image-minimal core-image-full-cmdline 
>> core-image-kernel-dev core-image-lsb core-image-lsb-dev 
>> core-image-lsb-sdk core-image-testmaster core-image-clutter 
>> core-image-weston core-image-x11 core-image-sato core-image-sato-dev 
>> core-image-sato-sdk core-image-sato-sdk-ptest
> 
> As we both suspected there are some issues with enabling this again,
> many are showcased here:
> 
> https://autobuilder.yoctoproject.org/main/builders/nightly-arm-lsb/builds/1156/steps/BuildImages/logs/stdio
> 
> * ltp has ksh/csh requirements in ptest
> * package dhcp-client-4.3.5-r0.0.armv5e requires libdns.so.170, but none of the providers can be installed
> * nothing provides /usr/bin/python33 needed by bind-9.10.5+P3-r0.0.armv5e
> ERROR: openssl-1.1.0f-r0 do_package_qa: QA Issue: /usr/lib/openssl/ptest/util/find-unused-errs contained in package openssl-ptest requires /bin/bash, but no providers found in RDEPENDS_openssl-ptest? [file-rdeps]
> ERROR: openssl-1.1.0f-r0 do_package_qa: QA Issue: /usr/lib/openssl/ptest/fuzz/helper.py contained in package openssl-ptest requires /usr/bin/python, but no providers found in RDEPENDS_openssl-ptest? [file-rdeps]
> ERROR: bind-9.10.5-P3-r0 do_package_qa: QA Issue: /usr/sbin/dnssec-checkds contained in package bind requires /usr/bin/python33, but no providers found in RDEPENDS_bind? [file-rdeps]

The above are valid packaging bugs.  RP may get there first, but I'll try to get
patches setup for them.

--Mark

> I suspect the key piece of testing you were missing may have been ptest enablement?
> 
> I might try and sort a few patches for pieces of this.
> 
> Cheers,
> 
> Richard
>