From: akuster808 <akuster808@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: [meta-security][PATCH] libcap-ng: fix checksums
Date: Mon, 12 Jan 2015 04:35:33 -0800 [thread overview]
Message-ID: <54B3BF95.5090401@gmail.com> (raw)
In-Reply-To: <2573410.MtKzVNeoZz@peggleto-mobl5.ger.corp.intel.com>
Paul,
Thanks for the feedback. My intension was to add some sort of a note by
my action did not reflect that.
I will send out an update.
- Armin
On 01/12/2015 01:53 AM, Paul Eggleton wrote:
> Hi Armin,
>
> On Sunday 11 January 2015 09:56:22 Armin Kuster wrote:
>> Signed-off-by: Armin Kuster <akuster808@gmail.com>
>> ---
>> recipes-security/libcap-ng/libcap-ng_0.7.4.bb | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/recipes-security/libcap-ng/libcap-ng_0.7.4.bb
>> b/recipes-security/libcap-ng/libcap-ng_0.7.4.bb index 3f225ba..8823dad
>> 100644
>> --- a/recipes-security/libcap-ng/libcap-ng_0.7.4.bb
>> +++ b/recipes-security/libcap-ng/libcap-ng_0.7.4.bb
>> @@ -12,8 +12,8 @@ SRC_URI =
>> "http://people.redhat.com/sgrubb/libcap-ng/libcap-ng-${PV}.tar.gz \
>>
>> inherit lib_package autotools pythonnative
>>
>> -SRC_URI[md5sum] = "610afb774f80a8032b711281df126283"
>> -SRC_URI[sha256sum] =
>> "5ca441c8d3a1e4cfe8a8151907977662679457311ccaa7eaac91447c33a35bb1"
>> +SRC_URI[md5sum] = "55c57c0673b944ea1a755bcb2636dabd"
>> +SRC_URI[sha256sum] =
>> "48a2083276f9820cb92dcb05d001b30733bcbf48c14c230303cac3cd08b45b6b"
>>
>> DEPENDS += "swig-native python"
>
> Could you please note in the commit message why these are being changed? It
> looks like they weren't changed at the last upgrade, which is fine, but that
> should be noted so that it's clear that it wasn't a matter of the files being
> changed upstream.
>
> Cheers,
> Paul
>
prev parent reply other threads:[~2015-01-12 12:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-11 17:56 [meta-security][PATCH] libcap-ng: fix checksums Armin Kuster
2015-01-12 9:53 ` Paul Eggleton
2015-01-12 12:35 ` akuster808 [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=54B3BF95.5090401@gmail.com \
--to=akuster808@gmail.com \
--cc=paul.eggleton@linux.intel.com \
--cc=yocto@yoctoproject.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 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.