Openembedded Core Discussions
 help / color / mirror / Atom feed
From: akuster <akuster@mvista.com>
To: Saul Wold <sgw@linux.intel.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] serf: 1.3.6 -> 1.3.8
Date: Mon, 17 Nov 2014 07:43:49 -0800	[thread overview]
Message-ID: <546A17B5.6070704@mvista.com> (raw)
In-Reply-To: <e6e4ba1fd6f31ecd724e7ca035f4cdc45576e0a3.1416213365.git.wenzong.fan@windriver.com>

Since Dizzy would need the security fix in serf 1.3.7, would  I backport 
1.3.8 to Dizzy from master or do we need a separate 1.3.7 update for Dizzy?

- Armin


On 11/17/2014 12:38 AM, wenzong.fan@windriver.com wrote:
> From: Wenzong Fan <wenzong.fan@windriver.com>
>
> Release changes:
>
> Serf 1.3.8 [2014-10-20, from /tags/1.3.8, rxxxx]
>    Fix issue #152: CRC calculation error for gzipped http reponses > 4GB.
>    Fix issue #153: SSPI CredHandle not freed when APR pool is destroyed.
>    Fix issue #154: Disable SSLv2 and SSLv3 as both or broken.
>
> Serf 1.3.7 [2014-08-11, from /tags/1.3.7, r2411]
>    Handle NUL bytes in fields of an X.509 certificate. (r2393, r2399)
>
> Signed-off-by: Wenzong Fan <wenzong.fan@windriver.com>
> ---
>   .../serf/{serf_1.3.6.bb => serf_1.3.8.bb}          |    6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>   rename meta/recipes-support/serf/{serf_1.3.6.bb => serf_1.3.8.bb} (74%)
>
> diff --git a/meta/recipes-support/serf/serf_1.3.6.bb b/meta/recipes-support/serf/serf_1.3.8.bb
> similarity index 74%
> rename from meta/recipes-support/serf/serf_1.3.6.bb
> rename to meta/recipes-support/serf/serf_1.3.8.bb
> index 08b04d3..10db122 100644
> --- a/meta/recipes-support/serf/serf_1.3.6.bb
> +++ b/meta/recipes-support/serf/serf_1.3.8.bb
> @@ -1,8 +1,8 @@
>
> -SRC_URI = "http://serf.googlecode.com/svn/src_releases/serf-1.3.6.tar.bz2 \
> +SRC_URI = "http://serf.googlecode.com/svn/src_releases/serf-${PV}.tar.bz2 \
>              file://norpath.patch"
> -SRC_URI[md5sum] = "7fe38fa6eab078e0beabf291d8e4995d"
> -SRC_URI[sha256sum] = "ca637beb0399797d4fc7ffa85e801733cd9c876997fac4a4fd12e9afe86563f2"
> +SRC_URI[md5sum] = "2e4efe57ff28cb3202a112e90f0c2889"
> +SRC_URI[sha256sum] = "e0500be065dbbce490449837bb2ab624e46d64fc0b090474d9acaa87c82b2590"
>
>   LICENSE = "Apache-2.0"
>   LIC_FILES_CHKSUM = "file://LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
>


  reply	other threads:[~2014-11-17 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17  8:38 [PATCH 0/1] uprev serf: 1.3.6 -> 1.3.8 wenzong.fan
2014-11-17  8:38 ` [PATCH 1/1] " wenzong.fan
2014-11-17 15:43   ` akuster [this message]
2014-11-17 16:29     ` Mark Hatle
2014-11-17 15:35 ` [PATCH 0/1] uprev " akuster
2014-11-18  2:58   ` wenzong fan
2014-11-19  1:46   ` wenzong fan

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=546A17B5.6070704@mvista.com \
    --to=akuster@mvista.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sgw@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox