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: [meta-oe][PATCH] [v3] lz4: update to latest version
Date: Tue, 15 Jul 2014 12:37:11 -0700	[thread overview]
Message-ID: <53C582E7.3090409@mvista.com> (raw)
In-Reply-To: <53C54AD7.4050702@linux.intel.com>


On 07/15/2014 08:37 AM, Saul Wold wrote:
> On 07/15/2014 08:22 AM, akuster wrote:
>>
>> On 07/15/2014 08:06 AM, Saul Wold wrote:
>>> On 07/15/2014 06:28 AM, Armin Kuster wrote:
>>>> update to version r119
>>>> Use github instead of svn
>>>> LICENSE md5sum changed since it was updated in r117
>>>
>>> What exactly changed in r117?  Same License different working or ??
>>
>> They updated the copyright date.
>>
>
> That's what we need in the commit message then, please update your 
> commit message.

done

>
> Is there a valid PV that you can set for lz4, seems like they are 
> still calling them rXXX, so PV should be "r119"

done.

Thanks,
Armin
>
> Thanks
>     Sau!
>
>> - Armin
>>>
>>> Sau!
>>>
>>>> FIxes CVE-2014-4611
>>>>
>>>> Signed-off-by: Armin Kuster <akuster@mvista.com>
>>>> ---
>>>>   meta/recipes-support/lz4/{lz4_svn.bb => lz4_git.bb} | 11 ++++-------
>>>>   1 file changed, 4 insertions(+), 7 deletions(-)
>>>>   rename meta/recipes-support/lz4/{lz4_svn.bb => lz4_git.bb} (68%)
>>>>
>>>> diff --git a/meta/recipes-support/lz4/lz4_svn.bb
>>>> b/meta/recipes-support/lz4/lz4_git.bb
>>>> similarity index 68%
>>>> rename from meta/recipes-support/lz4/lz4_svn.bb
>>>> rename to meta/recipes-support/lz4/lz4_git.bb
>>>> index 38e36d8..3978d76 100644
>>>> --- a/meta/recipes-support/lz4/lz4_svn.bb
>>>> +++ b/meta/recipes-support/lz4/lz4_git.bb
>>>> @@ -2,15 +2,12 @@ SUMMARY = "Extremely Fast Compression algorithm"
>>>>   DESCRIPTION = "LZ4 is a very fast lossless compression algorithm,
>>>> providing compression speed at 400 MB/s per core, scalable with
>>>> multi-cores CPU. It also features an extremely fast decoder, with
>>>> speed in multiple GB/s per core, typically reaching RAM speed limits
>>>> on multi-core systems."
>>>>
>>>>   LICENSE = "BSD"
>>>> -LIC_FILES_CHKSUM =
>>>> "file://LICENSE;md5=2008d2325e11691e17fcaa3a6046f850"
>>>> +LIC_FILES_CHKSUM =
>>>> "file://LICENSE;md5=0b0d063f37a4477b54af2459477dcafd"
>>>>
>>>> -# Upstream names releases after SVN revs
>>>> -SRCREV = "112"
>>>> -PV = "r${SRCREV}"
>>>> +SRCREV = "28fd251bc7b42e5cde15f9a2d78fc53b3b575558"
>>>> +SRC_URI= "git://github.com/Cyan4973/lz4.git;branch=master"
>>>>
>>>> -SRC_URI = "svn://lz4.googlecode.com/svn/;module=trunk;protocol=http"
>>>> -
>>>> -S = "${WORKDIR}/trunk"
>>>> +S = "${WORKDIR}/git"
>>>>
>>>>   EXTRA_OEMAKE = "PREFIX=${prefix} CC='${CC}' DESTDIR=${D}
>>>> LIBDIR=${libdir} INCLUDEDIR=${includedir}"
>>>>
>>>>
>>
>>



      reply	other threads:[~2014-07-15 19:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-15 13:28 [meta-oe][PATCH] [v3] lz4: update to latest version Armin Kuster
2014-07-15 15:06 ` Saul Wold
2014-07-15 15:22   ` akuster
2014-07-15 15:37     ` Saul Wold
2014-07-15 19:37       ` akuster [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=53C582E7.3090409@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