Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joe MacDonald <Joe.MacDonald@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-networking][PATCH v2] net-snmp: Backport fix for NETSNMP_NO_SYSTEMD typos
Date: Mon, 10 Jun 2013 11:17:41 -0400	[thread overview]
Message-ID: <20130610151740.GE9561@windriver.com> (raw)
In-Reply-To: <m6pg8v2p8pw3.fsf@cisco.com>

[-- Attachment #1: Type: text/plain, Size: 2527 bytes --]

[[oe] [meta-networking][PATCH v2] net-snmp: Backport fix for NETSNMP_NO_SYSTEMD typos] On 13.06.04 (Tue 18:36) Thomas Fitzsimmons wrote:

> Added Signed-off-by for backport patch refresh.  Bumped PR.

Merged, thanks.

-J.

> 
> Signed-off-by: Thomas Fitzsimmons <fitzsim@cisco.com>
> ---
>  .../net-snmp/net-snmp/systemd-support.patch        |    6 ++++--
>  .../recipes-protocols/net-snmp/net-snmp_5.7.2.bb   |    2 ++
>  2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp/systemd-support.patch b/meta-networking/recipes-protocols/net-snmp/net-snmp/systemd-support.patch
> index 18955f2..e19153b 100644
> --- a/meta-networking/recipes-protocols/net-snmp/net-snmp/systemd-support.patch
> +++ b/meta-networking/recipes-protocols/net-snmp/net-snmp/systemd-support.patch
> @@ -7,12 +7,14 @@ fef6cddfdb94da1a6b1fb768af62918b80f11fd3
>  0641e43c694c485cbbffef0556efc4641bd3ff50
>  76530a89f1c8bbd0b63acce63e10d5d4812a1a16 (conflict resolved)
>  bf108d7f1354f6276fc43c129963f2c49b9fc242
> +3692875172352f72cf3afd0d35f355e83d7e421b
>  74412748067c685e1d8ab6ed3bcc3ca9c2774844
>  86132e3f1e6ef7b4e0b96d8fa24e37c81b71b0e0
>  63557cf8986a33dba1d4429b583a901361052c4f
>  
>  Upstream-Status: Backport
>  
> +Signed-off-by: Thomas Fitzsimmons <fitzsim@cisco.com>
>  diff --git a/README.systemd b/README.systemd
>  new file mode 100644
>  index 0000000..f731851
> @@ -89,10 +91,10 @@ index b177d5b..08bdfc7 100644
>   #endif
>   
>   #ifndef WIN32
> -+#ifndef NETSNMP_NO_SYSYSTEMD
> ++#ifndef NETSNMP_NO_SYSTEMD
>  +    /* check if systemd has sockets for us and don't close them */
>  +    prepared_sockets = netsnmp_sd_listen_fds(0);
> -+#endif /* NETSNMP_NO_SYSYSTEMD */
> ++#endif /* NETSNMP_NO_SYSTEMD */
>  +
>       /*
>        * close all non-standard file descriptors we may have
> diff --git a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
> index 4c3939a..d21995a 100644
> --- a/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
> +++ b/meta-networking/recipes-protocols/net-snmp/net-snmp_5.7.2.bb
> @@ -6,6 +6,8 @@ LIC_FILES_CHKSUM = "file://README;beginline=3;endline=8;md5=7f7f00ba639ac8e8deb5
>  
>  DEPENDS = "openssl libnl pciutils"
>  
> +PR = "r1"
> +
>  SRC_URI = "${SOURCEFORGE_MIRROR}/net-snmp/net-snmp-${PV}.tar.gz \
>          file://init \
>          file://snmpd.conf \
-- 
-Joe MacDonald.
:wq

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

      reply	other threads:[~2013-06-10 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04 22:36 [meta-networking][PATCH v2] net-snmp: Backport fix for NETSNMP_NO_SYSTEMD typos Thomas Fitzsimmons
2013-06-10 15:17 ` Joe MacDonald [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=20130610151740.GE9561@windriver.com \
    --to=joe.macdonald@windriver.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox