All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bob Cochran <yocto@mindchasers.com>
To: poky@yoctoproject.org
Subject: [PATCH] update checksums for libx11-trim-1.4.4. The ones included in recipe were from 1.3.4
Date: Wed, 30 Nov 2011 11:54:21 -0500	[thread overview]
Message-ID: <4ED65FBD.4060400@mindchasers.com> (raw)

Updated the checksums in the recipe to match the libx11-trim-1.4.4 tar 
on freedesktop.org.  It looks like the MD5 & SHA checksums were carried 
over from the previous recipe (1.3.4).

I noticed this when trying to do a fresh build off master this morning.

Signed-off-by: Robert Cochran<yocto@mindchasers.com>
---
.../recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb |    4 ++--
  1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta/recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb 
b/meta/recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb
index 7aed308..32d025f 100644
--- a/meta/recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb
+++ b/meta/recipes-graphics/xorg-lib/libx11-trim_1.4.4.bb
@@ -14,7 +14,7 @@ SRC_URI += "file://x11_disable_makekeys.patch \
              file://makekeys_crosscompile.patch"


-SRC_URI[md5sum] = "f65c9c7ecbfb64c19dbd7927160d63fd"
-SRC_URI[sha256sum] = 
"88d7238ce5f7cd123450567de7a3b56a43556e4ccc45df38b8324147c889a844"
+SRC_URI[md5sum] = "ed7c382cbf8c13425b6a66bcac0ca5d9"
+SRC_URI[sha256sum] = 
"7fe62180f08ef5f0a0062fb444591e349cae2ab5af6ad834599f5c654e6c840d"

  EXTRA_OECONF += "--with-keysymdef=${STAGING_INCDIR}/X11/ --disable-xcms "
--
1.7.5.4



             reply	other threads:[~2011-11-30 16:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-30 16:54 Bob Cochran [this message]
2011-11-30 17:06 ` [PATCH] update checksums for libx11-trim-1.4.4. The ones included in recipe were from 1.3.4 Koen Kooi
2011-11-30 17:21   ` Martin Jansa

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=4ED65FBD.4060400@mindchasers.com \
    --to=yocto@mindchasers.com \
    --cc=poky@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.