All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter Kjellerstedt" <peter.kjellerstedt@axis.com>
To: Federico Pellegrin <fede.evol@gmail.com>,
	"poky@lists.yoctoproject.org" <poky@lists.yoctoproject.org>
Cc: Federico Pellegrin <fede@evolware.org>
Subject: Re: [poky][PATCH] signing-keys: add RDEPENDS to signing-keys from specific provider
Date: Sun, 19 Jun 2022 13:06:33 +0000	[thread overview]
Message-ID: <dd08964309c24d7985a45c774710c13b@axis.com> (raw)
In-Reply-To: <20220618052305.304352-1-fede@evolware.org>

> -----Original Message-----
> From: poky@lists.yoctoproject.org <poky@lists.yoctoproject.org> On Behalf
> Of Federico Pellegrin
> Sent: den 18 juni 2022 07:23
> To: poky@lists.yoctoproject.org
> Cc: Federico Pellegrin <fede@evolware.org>
> Subject: [poky][PATCH] signing-keys: add RDEPENDS to signing-keys from
> specific provider

Poky is made up of multiple repositories. Patches for meta should go to the 
openembedded-core@lists.openembedded.org mailing list (this is documented 
in README.md).

> 
> 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 bringing the specific provider
> PROVIDES to include also the generic package (RPM example):
> signing-keys
> signing-keys-rpm = 1.0-r0
> 
> Likely another way could be also to change the requirement for
> dev or just allow empty packages as well.
> 
> Signed-off-by: Federico Pellegrin <fede@evolware.org>
> ---
>  meta/recipes-core/meta/signing-keys.bb | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/meta/recipes-core/meta/signing-keys.bb b/meta/recipes-
> core/meta/signing-keys.bb
> index 03463f95f56..d0602cf82af 100644
> --- a/meta/recipes-core/meta/signing-keys.bb
> +++ b/meta/recipes-core/meta/signing-keys.bb
> @@ -18,6 +18,10 @@ FILES:${PN}-rpm = "${sysconfdir}/pki/rpm-gpg"
>  FILES:${PN}-ipk = "${sysconfdir}/pki/ipk-gpg"
>  FILES:${PN}-packagefeed = "${sysconfdir}/pki/packagefeed-gpg"
> 
> +RPROVIDES:${PN}-rpm += "${PN}"
> +RPROVIDES:${PN}-ipk += "${PN}"
> +RPROVIDES:${PN}-packagefeed += "${PN}"

This is incorrect. The correct thing to do is to instead remove the 
dependency from ${PN}-dev on ${PN}, i.e.:

RDEPENDS:${PN}-dev = ""

> +
>  python do_get_public_keys () {
>      from oe.gpg_sign import get_signer
> 
> --
> 2.35.3

//Peter


  reply	other threads:[~2022-06-19 13:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-18  5:23 [poky][PATCH] signing-keys: add RDEPENDS to signing-keys from specific provider fede.evol
2022-06-19 13:06 ` Peter Kjellerstedt [this message]
2022-06-19 15:13   ` Federico Pellegrin
  -- strict thread matches above, loose matches on Subject: below --
2022-06-18  5:20 Federico Pellegrin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=dd08964309c24d7985a45c774710c13b@axis.com \
    --to=peter.kjellerstedt@axis.com \
    --cc=fede.evol@gmail.com \
    --cc=fede@evolware.org \
    --cc=poky@lists.yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.