Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/4] freetype: upgrade to 2.4.9
Date: Mon, 11 Jun 2012 10:49:57 -0700	[thread overview]
Message-ID: <4FD62FC5.5010807@intel.com> (raw)
In-Reply-To: <1339166898-11667-2-git-send-email-laurentiu.palcu@intel.com>

On 06/08/2012 07:48 AM, Laurentiu Palcu wrote:
> Signed-off-by: Laurentiu Palcu<laurentiu.palcu@intel.com>

Hi Laurentiu,

Since this commit fixes a bug and addresses security issues, please be 
sure to include these details in the future in your commit log. 
Something along the lines of:

Addresses CVE-2012-1126, CVE-2012-1127, CVE-2012-1128, ...

This fixes [YOCTO #2468]

helps us track security-related fixes and bugfixes more easily.

Note, in this case the number of CVEs this fixes is unusually long (I 
count 19 of them), but listing all of them is good policy.

Thanks,

Scott

> ---
>   .../no-hardcode.patch                              |    0
>   .../{freetype_2.4.8.bb =>  freetype_2.4.9.bb}       |    4 ++--
>   2 files changed, 2 insertions(+), 2 deletions(-)
>   rename meta/recipes-graphics/freetype/{freetype-2.4.8 =>  freetype-2.4.9}/no-hardcode.patch (100%)
>   rename meta/recipes-graphics/freetype/{freetype_2.4.8.bb =>  freetype_2.4.9.bb} (91%)
>
> diff --git a/meta/recipes-graphics/freetype/freetype-2.4.8/no-hardcode.patch b/meta/recipes-graphics/freetype/freetype-2.4.9/no-hardcode.patch
> similarity index 100%
> rename from meta/recipes-graphics/freetype/freetype-2.4.8/no-hardcode.patch
> rename to meta/recipes-graphics/freetype/freetype-2.4.9/no-hardcode.patch
> diff --git a/meta/recipes-graphics/freetype/freetype_2.4.8.bb b/meta/recipes-graphics/freetype/freetype_2.4.9.bb
> similarity index 91%
> rename from meta/recipes-graphics/freetype/freetype_2.4.8.bb
> rename to meta/recipes-graphics/freetype/freetype_2.4.9.bb
> index bce01cf..31bee80 100644
> --- a/meta/recipes-graphics/freetype/freetype_2.4.8.bb
> +++ b/meta/recipes-graphics/freetype/freetype_2.4.9.bb
> @@ -18,8 +18,8 @@ PR = "r0"
>   SRC_URI = "${SOURCEFORGE_MIRROR}/freetype/freetype-${PV}.tar.bz2 \
>              file://no-hardcode.patch"
>
> -SRC_URI[md5sum] = "dbf2caca1d3afd410a29217a9809d397"
> -SRC_URI[sha256sum] = "a9eb7da3875fcb2f022a9c280c01b94ae45ac83d8102838c05dce1277948fb71"
> +SRC_URI[md5sum] = "77a893dae81fd5b896632715ca041179"
> +SRC_URI[sha256sum] = "c4204ac1d48e99d4375a2f32bf4f3f92780a9d9f015e64e57e852f6c004859b9"
>
>   S = "${WORKDIR}/freetype-${PV}"
>


-- 
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center



  reply	other threads:[~2012-06-11 18:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-08 14:48 [PATCH 0/4] Package upgrades: freetype, tzdata, ethtool, menu-cache Laurentiu Palcu
2012-06-08 14:48 ` [PATCH 1/4] freetype: upgrade to 2.4.9 Laurentiu Palcu
2012-06-11 17:49   ` Scott Garman [this message]
2012-06-08 14:48 ` [PATCH 2/4] tzdata: upgrade to 2012c Laurentiu Palcu
2012-06-08 14:48 ` [PATCH 3/4] ethtool: upgrade to 3.2 Laurentiu Palcu
2012-06-08 14:48 ` [PATCH 4/4] menu-cache: upgrade to 0.3.3 Laurentiu Palcu
2012-06-11 12:55 ` [PATCH 0/4] Package upgrades: freetype, tzdata, ethtool, menu-cache Richard Purdie

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=4FD62FC5.5010807@intel.com \
    --to=scott.a.garman@intel.com \
    --cc=openembedded-core@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