On 05/29/2017 10:32 AM, Patrick Ohly wrote: > Software layers were previously allowed to change signatures, but > that's not desired for those layers either. The rule that a layer > which is "Yocto Compatible 2.0" must not change signatures unless > explicitly requested holds for all kinds of layers.
If i understand correctly now a software layer can't change a signature
but how do we handle this?, currently if a software layer is added and
has bbappends or newer version of a recipe the signature will change.
May be we need to postpone this validation removal until we have a
manner to avoid a software layer automatically change the signatures.
Cheers,
Anibal
>
> Signed-off-by: Patrick Ohly <patrick.o...@intel.com>
> ---
> scripts/lib/compatlayer/cases/common.py | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/scripts/lib/compatlayer/cases/common.py
> b/scripts/lib/compatlayer/cases/common.py
> index 2dfcbb1..fe4936e 100644
> --- a/scripts/lib/compatlayer/cases/common.py
> +++ b/scripts/lib/compatlayer/cases/common.py
> @@ -27,10 +27,6 @@ class CommonCompatLayer(OECompatLayerTestCase):
> 'bitbake -e')
>
> def test_signatures(self):
> - if self.tc.layer['type'] == LayerType.SOFTWARE:
> - raise unittest.SkipTest("Layer %s isn't BSP or DISTRO one." \
> - % self.tc.layer['name'])
> -
> # task -> (old signature, new signature)
> sig_diff = {}
> curr_sigs, _ = get_signatures(self.td['builddir'], failsafe=True)
>
signature.asc
Description: OpenPGP digital signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
