| Message ID | 20220619152417.44584-1-fede@evolware.org |
|---|---|
| State | New |
| Headers | show |
| Series | [poky,meta,PATCHv2] signing-keys: fix RDEPENDS to signing-keys-dev | expand |
diff --git a/meta/recipes-core/meta/signing-keys.bb b/meta/recipes-core/meta/signing-keys.bb index 03463f95f56..107a39d6581 100644 --- a/meta/recipes-core/meta/signing-keys.bb +++ b/meta/recipes-core/meta/signing-keys.bb @@ -18,6 +18,8 @@ FILES:${PN}-rpm = "${sysconfdir}/pki/rpm-gpg" FILES:${PN}-ipk = "${sysconfdir}/pki/ipk-gpg" FILES:${PN}-packagefeed = "${sysconfdir}/pki/packagefeed-gpg" +RDEPENDS:${PN}-dev = "" + python do_get_public_keys () { from oe.gpg_sign import get_signer
Specific provider (ie. RPM or IPK) does "provide" just itself as a package to the system. This will cause the "-dev" package, which refers to the generic signing-keys and not the provider specific, to miss the dependency. Error case (RPM) when populating sdk: Error: Problem: conflicting requests - nothing provides signing-keys = 1.0-r0 needed by signing-keys-dev-1.0-r0.noarch (try to add '--skip-broken' to skip uninstallable packages) Examining signing-keys-rpm packages in PROVIDES we have indeed: signing-keys-rpm = 1.0-r0 But in signing-keys-dev: in REQUIRES: signing-keys-1.0-r0 This MR will fix the situation by removing the RDEPENDS for the -dev package Signed-off-by: Federico Pellegrin <fede@evolware.org> --- meta/recipes-core/meta/signing-keys.bb | 2 ++ 1 file changed, 2 insertions(+)