Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Leonardo Sandoval <leonardo.sandoval.gonzalez@linux.intel.com>
To: Fan Xin <fan.xin@jp.fujitsu.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] openvpn: Upgrade 2.3.9 -> 2.4.2
Date: Fri, 02 Jun 2017 09:37:08 -0500	[thread overview]
Message-ID: <1496414228.26945.94.camel@linux.intel.com> (raw)
In-Reply-To: <1496366490-28223-1-git-send-email-fan.xin@jp.fujitsu.com>

On Fri, 2017-06-02 at 10:21 +0900, Fan Xin wrote:
> Signed-off-by: Fan Xin <fan.xin@jp.fujitsu.com>
> ---
>  .../recipes-support/openvpn/{openvpn_2.3.9.bb => openvpn_2.4.2.bb}  | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>  rename meta-networking/recipes-support/openvpn/{openvpn_2.3.9.bb => openvpn_2.4.2.bb} (93%)
> 
> diff --git a/meta-networking/recipes-support/openvpn/openvpn_2.3.9.bb b/meta-networking/recipes-support/openvpn/openvpn_2.4.2.bb
> similarity index 93%
> rename from meta-networking/recipes-support/openvpn/openvpn_2.3.9.bb
> rename to meta-networking/recipes-support/openvpn/openvpn_2.4.2.bb
> index db510de..ae72671 100644
> --- a/meta-networking/recipes-support/openvpn/openvpn_2.3.9.bb
> +++ b/meta-networking/recipes-support/openvpn/openvpn_2.4.2.bb
> @@ -2,7 +2,7 @@ SUMMARY = "A full-featured SSL VPN solution via tun device."
>  HOMEPAGE = "http://openvpn.sourceforge.net"
>  SECTION = "net"
>  LICENSE = "GPLv2"
> -LIC_FILES_CHKSUM = "file://COPYING;md5=5aac200199fde47501876cba7263cb0c"
> +LIC_FILES_CHKSUM = "file://COPYING;md5=e9b64491ec98eb6c6493ac5e4118f107"

reason for the above chksum change? 

>  DEPENDS = "lzo openssl iproute2 ${@bb.utils.contains('DISTRO_FEATURES', 'pam', 'libpam', '', d)}"
>  
>  inherit autotools systemd
> @@ -12,8 +12,8 @@ SRC_URI = "http://swupdate.openvpn.org/community/releases/openvpn-${PV}.tar.gz \
>             file://openvpn@.service \
>             file://openvpn-volatile.conf"
>  
> -SRC_URI[md5sum] = "265755044ae88f9249d509f6d061f7e5"
> -SRC_URI[sha256sum] = "2c12fe9ea641ac1291e70322cc500641c84e5903dd4f40bf2eda7e9f209b2f9c"
> +SRC_URI[md5sum] = "0714019e109a043e858278c9e2ca18e0"
> +SRC_URI[sha256sum] = "b24740c9d44a81eaf2befc4846d51445a520104321e32aaf0c135ed2e098a624"
>  
>  SYSTEMD_SERVICE_${PN} += "openvpn@loopback-server.service openvpn@loopback-client.service"
>  SYSTEMD_AUTO_ENABLE = "disable"
> -- 
> 1.9.1
> 




      reply	other threads:[~2017-06-02 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-02  1:21 [PATCH] openvpn: Upgrade 2.3.9 -> 2.4.2 Fan Xin
2017-06-02 14:37 ` Leonardo Sandoval [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=1496414228.26945.94.camel@linux.intel.com \
    --to=leonardo.sandoval.gonzalez@linux.intel.com \
    --cc=fan.xin@jp.fujitsu.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