From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chen Qi <Qi.Chen@windriver.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 4/9] gzip: upgrade to 1.8
Date: Mon, 13 Jun 2016 09:18:07 +0100 [thread overview]
Message-ID: <1465805887.13979.199.camel@linuxfoundation.org> (raw)
In-Reply-To: <1465802599.13979.195.camel@linuxfoundation.org>
On Mon, 2016-06-13 at 08:23 +0100, Richard Purdie wrote:
> On Sun, 2016-06-12 at 10:21 +0800, Chen Qi wrote:
> > Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> > ---
> > meta/recipes-extended/gzip/{gzip_1.6.bb => gzip_1.8.bb} | 0
> > 1 file changed, 0 insertions(+), 0 deletions(-)
> > rename meta/recipes-extended/gzip/{gzip_1.6.bb => gzip_1.8.bb}
> > (100%)
> >
> > diff --git a/meta/recipes-extended/gzip/gzip_1.6.bb b/meta/recipes
> > -extended/gzip/gzip_1.8.bb
> > similarity index 100%
> > rename from meta/recipes-extended/gzip/gzip_1.6.bb
> > rename to meta/recipes-extended/gzip/gzip_1.8.bb
>
> WARNING: gzip-1.8-r0 do_fetch: Checksum mismatch for local file
> /home/pokybuild/yocto-autobuilder/yocto-worker/build
> -appliance/build/build/downloads/gzip-1.8.tar.gz
> Cleaning and trying again.
> WARNING: gzip-1.8-r0 do_fetch: Renaming /home/pokybuild/yocto
> -autobuilder/yocto-worker/build-appliance/build/build/downloads/gzip
> -1.8.tar.gz to /home/pokybuild/yocto-autobuilder/yocto-worker/build
> -appliance/build/build/downloads/gzip-1.8.tar.gz_bad
> -checksum_732553152814b22dc35aa0267df5286c
> ERROR: gzip-1.8-r0 do_fetch: Checksum failure fetching
> http://ftp.gnu.org/gnu/gzip/gzip-1.8.tar.gz
> ERROR: gzip-1.8-r0 do_fetch: Function failed: Fetcher failure for
> URL: 'http://ftp.gnu.org/gnu/gzip/gzip-1.8.tar.gz'. Checksum
> mismatch!
> File: '/home/pokybuild/yocto-autobuilder/yocto-worker/build
> -appliance/build/build/downloads/gzip-1.8.tar.gz' has md5 checksum
> 732553152814b22dc35aa0267df5286c when
> 38603cb2843bf5681ff41aab3bcd6a20 was expected
> File: '/home/pokybuild/yocto-autobuilder/yocto-worker/build
> -appliance/build/build/downloads/gzip-1.8.tar.gz' has sha256 checksum
> 1ff7aedb3d66a0d73f442f6261e4b3860df6fd6c94025c2cb31a202c9c60fe0e when
> 97eb83b763d9e5ad35f351fe5517e6b71521d7aac7acf3e3cacdb6b1496d8f7e was
> expected
> If this change is expected (e.g. you have upgraded to a new version
> without updating the checksums) then you can use these lines within
> the recipe:
> SRC_URI[md5sum] = "732553152814b22dc35aa0267df5286c"
> SRC_URI[sha256sum] =
> "1ff7aedb3d66a0d73f442f6261e4b3860df6fd6c94025c2cb31a202c9c60fe0e"
> Otherwise you should retry the download and/or check with upstream to
> determine if the file has become corrupted or otherwise unexpectedly
> modified.
The patch directory also needed renaming. I've merged fixes into
-next...
Cheers,
Richard
next prev parent reply other threads:[~2016-06-13 8:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-12 2:20 [PATCH 0/9] Package Upgrades -- 20160612 Chen Qi
2016-06-12 2:20 ` [PATCH 1/9] grep: upgrade to 2.25 Chen Qi
2016-06-12 2:21 ` [PATCH 2/9] sysstat: upgrade to 11.3.4 Chen Qi
2016-06-12 2:21 ` [PATCH 3/9] sudo: upgrade to 1.8.16 Chen Qi
2016-06-12 2:21 ` [PATCH 4/9] gzip: upgrade to 1.8 Chen Qi
2016-06-13 7:23 ` Richard Purdie
2016-06-13 8:18 ` Richard Purdie [this message]
2016-06-14 4:38 ` Maxin B. John
2016-06-14 9:41 ` ChenQi
2016-06-14 12:03 ` Richard Purdie
2016-06-15 3:17 ` ChenQi
2016-06-12 2:21 ` [PATCH 5/9] byacc: upgrade to 20160324 Chen Qi
2016-06-12 2:21 ` [PATCH 6/9] curl: upgrade to 7.49.1 Chen Qi
2016-06-12 2:21 ` [PATCH 7/9] tar: upgrade to 1.29 Chen Qi
2016-06-12 2:21 ` [PATCH 8/9] pciutils: upgrade to 3.5.1 Chen Qi
2016-06-12 2:21 ` [PATCH 9/9] resolvconf: upgrade to 1.79 Chen Qi
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=1465805887.13979.199.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.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