Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Stanislav Brabec <utx@penguin.cz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] Fixed checksum for tda1004x-firmware.
Date: Wed, 09 Sep 2009 14:24:05 +0200	[thread overview]
Message-ID: <1252499045.5887.11.camel@hammer.suse.cz> (raw)
In-Reply-To: <1252329016-10848-3-git-send-email-ihar.hrachyshka@gmail.com>

Ihar Hrachyshka wrote:
> Signed-off-by: Ihar Hrachyshka <ihar.hrachyshka@gmail.com>
> ---
>  conf/checksums.ini |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/conf/checksums.ini b/conf/checksums.ini
> index 053a2ad..bb075cc 100644
> --- a/conf/checksums.ini
> +++ b/conf/checksums.ini
> @@ -18299,8 +18299,8 @@ md5=7fa369bff1031acbe4ca41f03bee7d02
>  sha256=53d2f92c3d14423b49c2ff077855cf3987d38def963c82fd26fba5de379ca540

If your patch will be applied, you would probably have to review
d5345f88b5ffdca098e0281f42f51e42ef43e79d and nearly completely revert
plus remove unzip-native from DEPENDS.

Warning: You cannot do it completely. There are recipes that call unzip
on auto-extract .exe file, and you have to keep my change there.

-- 
Stanislav Brabec
http://www.penguin.cz/~utx/zaurus




      parent reply	other threads:[~2009-09-09 12:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-07 13:10 [PATCH] Fixed concurrency problem for ZIP packed recipes Ihar Hrachyshka
2009-09-07 13:10 ` [PATCH] Use automatic unzip-native dependency detection Ihar Hrachyshka
2009-09-07 13:10   ` [PATCH] Fixed checksum for tda1004x-firmware Ihar Hrachyshka
2009-09-07 13:10     ` [PATCH] Use NEED_UNZIP_FOR_UNPACK variable for some recipes Ihar Hrachyshka
2009-09-09 13:05       ` Phil Blundell
2009-09-10  7:48         ` Ihar Hrachyshka
2009-09-09 12:24     ` Stanislav Brabec [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=1252499045.5887.11.camel@hammer.suse.cz \
    --to=utx@penguin.cz \
    --cc=openembedded-devel@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