All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bruce Ashfield" <bruce.ashfield@gmail.com>
To: Yi Fan Yu <yifan.yu@windriver.com>
Cc: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization][PATCH] nagios-nsca: blacklist recipe due to unsupported libmcrypt
Date: Sun, 7 Feb 2021 08:49:06 -0500	[thread overview]
Message-ID: <20210207134905.GC48372@gmail.com> (raw)
In-Reply-To: <20210205215310.17125-1-yifan.yu@windriver.com>

merged (now we see if anyone notices the blacklist and asks!)

Bruce

In message: [meta-virtualization][PATCH] nagios-nsca: blacklist recipe due to unsupported libmcrypt
on 05/02/2021 Yi Fan Yu wrote:

> nagios-nsca depends on libmcrypt...
> However, libmcrypt is considered as abandonware
> The last release was in 2007.
> 
> libmcrypt might not be building properly with
> the upgrade of autoconf to 2.71.
> 
> Signed-off-by: Yi Fan Yu <yifan.yu@windriver.com>
> ---
>  recipes-extended/nagios/nagios-nsca_2.9.2.bb | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/recipes-extended/nagios/nagios-nsca_2.9.2.bb b/recipes-extended/nagios/nagios-nsca_2.9.2.bb
> index d342810..66f8da5 100644
> --- a/recipes-extended/nagios/nagios-nsca_2.9.2.bb
> +++ b/recipes-extended/nagios/nagios-nsca_2.9.2.bb
> @@ -82,3 +82,5 @@ SYSTEMD_AUTO_ENABLE_${PN}-daemon = "enable"
>  INITSCRIPT_PACKAGES = "${PN}-daemon"
>  INITSCRIPT_NAME_${PN}-daemon = "nsca"
>  INITSCRIPT_PARAMS_${PN}-daemon = "defaults"
> +
> +PNBLACKLIST[nagios-nsca] ?= "Depends on libmcrypt, which is considered abandonware"
> -- 
> 2.29.2
> 

> 
> 
> 


      reply	other threads:[~2021-02-07 13:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-05 21:53 [meta-virtualization][PATCH] nagios-nsca: blacklist recipe due to unsupported libmcrypt Yi Fan Yu
2021-02-07 13:49 ` Bruce Ashfield [this message]

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=20210207134905.GC48372@gmail.com \
    --to=bruce.ashfield@gmail.com \
    --cc=meta-virtualization@lists.yoctoproject.org \
    --cc=yifan.yu@windriver.com \
    /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.