From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alejandro Hernandez <alejandro.hernandez@linux.intel.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] python-setuptools: Upgrade to v 25.1.0
Date: Thu, 28 Jul 2016 22:39:43 +0100 [thread overview]
Message-ID: <1469741983.9142.34.camel@linuxfoundation.org> (raw)
In-Reply-To: <1469728851-20606-1-git-send-email-alejandro.hernandez@linux.intel.com>
On Thu, 2016-07-28 at 18:00 +0000, Alejandro Hernandez wrote:
> LICENCE checksum did not change, it is emebedded on the setup.py
> file,
> this file changed, so the line number where we get the checksum
> changed.
>
> Signed-off-by: Alejandro Hernandez <
> alejandro.hernandez@linux.intel.com>
> ---
> meta/recipes-devtools/python/python-setuptools.inc | 6 ++--
> .../python/python-setuptools_22.0.5.bb | 38 ------------
> ----------
> .../python/python-setuptools_25.1.0.bb | 38
> ++++++++++++++++++++++
> 3 files changed, 41 insertions(+), 41 deletions(-)
> delete mode 100644 meta/recipes-devtools/python/python
> -setuptools_22.0.5.bb
> create mode 100644 meta/recipes-devtools/python/python
> -setuptools_25.1.0.bb
This patch results in:
ERROR: python3-setuptools-22.0.5-r0 do_fetch: Checksum failure fetching https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-22.0.5.tar.gz
ERROR: python3-setuptools-22.0.5-r0 do_fetch: Function failed: Fetcher failure for URL: 'https://files.pythonhosted.org/packages/source/s/setuptools/setuptools-22.0.5.tar.gz'. Checksum mismatch!
File: '/media/build3/sources/setuptools-22.0.5.tar.gz' has md5 checksum 869f3029dcc66a64ba39875e2a2f044a when a4814dead37e74a86883c66f7d420d73 was expected
File: '/media/build3/sources/setuptools-22.0.5.tar.gz' has sha256 checksum 19aad19471052d5daefe96f2c1fa2e88dcdb17488bf8708d7e6356881ea833cb when 6a0f8111feb5a3438c6309cda49810a16d23e73c173331281edc37dd1374d1d5 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] = "869f3029dcc66a64ba39875e2a2f044a"
SRC_URI[sha256sum] = "19aad19471052d5daefe96f2c1fa2e88dcdb17488bf8708d7e6356881ea833cb"
Otherwise you should retry the download and/or check with upstream to determine if the file has become corrupted or otherwise unexpectedly modified.
ERROR: Logfile of failure stored in: /media/build1/poky/build/tmp/work/core2-64-poky-linux/python3-setuptools/22.0.5-r0/temp/log.do_fetch.131527
ERROR: Task /media/build1/poky/meta/recipes-devtools/python/python3-setuptools_22.0.5.bb:do_fetch (/media/build1/poky/meta/recipes-devtools/python/python3-setuptools_22.0.5.bb:do_fetch) failed with exit code '1'
Since I suspect there is a common file between python and python3...
Cheers,
Richard
next prev parent reply other threads:[~2016-07-28 21:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-28 18:00 [PATCH v3] python-setuptools: Upgrade to v 25.1.0 Alejandro Hernandez
2016-07-28 21:39 ` Richard Purdie [this message]
2016-08-01 16:33 ` Alejandro Hernandez
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=1469741983.9142.34.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alejandro.hernandez@linux.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