All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Yang <liezhi.yang@windriver.com>
To: Otavio Salvador <otavio@ossystems.com.br>,
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/2] libpam: Fix runtime providers
Date: Sat, 30 Aug 2014 18:16:31 +0800	[thread overview]
Message-ID: <5401A47F.7060702@windriver.com> (raw)
In-Reply-To: <1409268800-17566-1-git-send-email-otavio@ossystems.com.br>


Hello,

I've sent a patch to fix the warning like:

WARNING: QA Issue: lib32-pam-plugin-access rdepends on 
lib32-lib32-libpam-suffix, but it isn't a build dependency? [build-deps]
WARNING: QA Issue: lib32-pam-plugin-cracklib rdepends on 
lib32-lib32-libpam-suffix, but it isn't a build dependency? [build-deps]

WARNING: QA Issue: nativesdk-pam-plugin-access rdepends on 
nativesdk-nativesdk-libpam-suffix, but it isn't a build dependency? [build-deps]
WARNING: QA Issue: nativesdk-pam-plugin-cracklib rdepends on 
nativesdk-nativesdk-libpam-suffix, but it isn't a build dependency? [build-deps]


And the patch:
http://lists.openembedded.org/pipermail/openembedded-core/2014-August/096594.html

// Robert

On 08/29/2014 07:33 AM, Otavio Salvador wrote:
> The runtime providers were commented out. Removing the comment brings
> up a issue with the native renaming which has been workarounded
> disabling the runtime recommendation. This is indeed a workaround so a
> FIXME comment has been added to remind about it in case we someday
> move to native prefix.
>
> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
> ---
>   meta/recipes-extended/pam/libpam_1.1.6.bb |    5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/recipes-extended/pam/libpam_1.1.6.bb b/meta/recipes-extended/pam/libpam_1.1.6.bb
> index d7033d0..f08b4af 100644
> --- a/meta/recipes-extended/pam/libpam_1.1.6.bb
> +++ b/meta/recipes-extended/pam/libpam_1.1.6.bb
> @@ -81,7 +81,10 @@ RDEPENDS_${PN}-xtests = "${PN}-${libpam_suffix} \
>       pam-plugin-cracklib-${libpam_suffix} pam-plugin-pwhistory-${libpam_suffix} \
>       pam-plugin-succeed-if-${libpam_suffix} pam-plugin-time-${libpam_suffix} \
>       coreutils bash"
> -#RRECOMMENDS_${PN} = "${PN}-runtime-${libpam_suffix}"
> +
> +# FIXME: Native suffix breaks here, disable it for now
> +RRECOMMENDS_${PN} = "${PN}-runtime-${libpam_suffix}"
> +RRECOMMENDS_${PN}_class-native = ""
>
>   python populate_packages_prepend () {
>       def pam_plugin_append_file(pn, dir, file):
>


  parent reply	other threads:[~2014-08-30 10:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 23:33 [PATCH 1/2] libpam: Fix runtime providers Otavio Salvador
2014-08-28 23:33 ` [PATCH 2/2] libpam: Fix multilib packaging Otavio Salvador
2014-08-30 10:16 ` Robert Yang [this message]
2014-08-30 14:28   ` [PATCH 1/2] libpam: Fix runtime providers Otavio Salvador
  -- strict thread matches above, loose matches on Subject: below --
2014-08-28 22:40 Otavio Salvador

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=5401A47F.7060702@windriver.com \
    --to=liezhi.yang@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    /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.