From: akuster808 <akuster808@gmail.com>
To: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [meta-python][PATCH] python-cryptography: 2.1.4 -> 2.2
Date: Wed, 21 Mar 2018 07:47:20 -0700 [thread overview]
Message-ID: <8af916ce-0d79-7be7-172f-07abb7540e30@gmail.com> (raw)
In-Reply-To: <1521603377-34881-6-git-send-email-huangqy.fnst@cn.fujitsu.com>
On 03/20/2018 08:36 PM, Huang Qiyu wrote:
> 1.Upgrade python-cryptography from 2.1.4 to 2.2.
> 2.Update the checksum of LIC_FILES_CHKSUM, but license remained the same.
>
> Signed-off-by: Huang Qiyu <huangqy.fnst@cn.fujitsu.com>
I am seeing:
ERROR: python3-cryptography-2.1.4-r0 do_fetch: Checksum failure fetching
https://files.pythonhosted.org/packages/source/c/cryptography/cryptography-2.1.4.tar.gz
ERROR: python3-cryptography-2.1.4-r0 do_fetch: Fetcher failure for URL:
'https://files.pythonhosted.org/packages/source/c/cryptography/cryptography-2.1.4.tar.gz'.
Checksum mismatch!
File: '/home/akuster/OE/downloads/cryptography-2.1.4.tar.gz' has md5
checksum 9f39d4d8f2b05f295fa0ff52475ec4f2 when
c49c1ee145a900313a216fa2c788208c was expected
File: '/home/akuster/OE/downloads/cryptography-2.1.4.tar.gz' has sha256
checksum
e4d967371c5b6b2e67855066471d844c5d52d210c36c28d49a8507b96e2c5291 when
f5a0279e362c37e2150a32fe35ec20226e9237b6c9927fce8d53ef8e49e64f48 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] = "9f39d4d8f2b05f295fa0ff52475ec4f2"
SRC_URI[sha256sum] =
"e4d967371c5b6b2e67855066471d844c5d52d210c36c28d49a8507b96e2c5291"
Otherwise you should retry the download and/or check with upstream to
determine if the file has become corrupted or otherwise unexpectedly
modified.
please double check.
- armin
> ---
> meta-python/recipes-devtools/python/python-cryptography.inc | 6 +++---
> .../{python-cryptography_2.1.4.bb => python-cryptography_2.2.bb} | 0
> 2 files changed, 3 insertions(+), 3 deletions(-)
> rename meta-python/recipes-devtools/python/{python-cryptography_2.1.4.bb => python-cryptography_2.2.bb} (100%)
>
> diff --git a/meta-python/recipes-devtools/python/python-cryptography.inc b/meta-python/recipes-devtools/python/python-cryptography.inc
> index 4be7907..fcd5358 100644
> --- a/meta-python/recipes-devtools/python/python-cryptography.inc
> +++ b/meta-python/recipes-devtools/python/python-cryptography.inc
> @@ -1,7 +1,7 @@
> SUMMARY = "Provides cryptographic recipes and primitives to python developers"
> HOMEPAGE = "https://cryptography.io/"
> LICENSE = "Apache-2.0 | BSD"
> -LIC_FILES_CHKSUM = "file://LICENSE;md5=d5ede125ed08d4fd14ec44d334bdb388"
> +LIC_FILES_CHKSUM = "file://LICENSE;md5=097f805837700cfac572ac274cd38124"
>
> DEPENDS += " \
> ${PYTHON_PN}-cffi \
> @@ -10,8 +10,8 @@ DEPENDS += " \
> ${PYTHON_PN}-six \
> "
>
> -SRC_URI[md5sum] = "9f39d4d8f2b05f295fa0ff52475ec4f2"
> -SRC_URI[sha256sum] = "e4d967371c5b6b2e67855066471d844c5d52d210c36c28d49a8507b96e2c5291"
> +SRC_URI[md5sum] = "c49c1ee145a900313a216fa2c788208c"
> +SRC_URI[sha256sum] = "f5a0279e362c37e2150a32fe35ec20226e9237b6c9927fce8d53ef8e49e64f48"
>
> RDEPENDS_${PN} += " \
> ${PYTHON_PN}-cffi \
> diff --git a/meta-python/recipes-devtools/python/python-cryptography_2.1.4.bb b/meta-python/recipes-devtools/python/python-cryptography_2.2.bb
> similarity index 100%
> rename from meta-python/recipes-devtools/python/python-cryptography_2.1.4.bb
> rename to meta-python/recipes-devtools/python/python-cryptography_2.2.bb
next prev parent reply other threads:[~2018-03-21 14:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 3:36 [meta-networking][PATCH] quagga: 1.2.2 -> 1.2.4 Huang Qiyu
2018-03-21 3:36 ` [meta-networking][PATCH] strongswan: 5.5.3 -> 5.6.2 Huang Qiyu
2018-03-21 3:36 ` [meta-oe][PATCH] python-pygobject: 3.22.0 -> 3.28.0 Huang Qiyu
2018-03-21 3:36 ` [meta-oe][PATCH] sessreg: 1.1.0 -> 1.1.1 Huang Qiyu
2018-03-21 3:36 ` [meta-python][PATCH] python-cffi: 1.11.4 -> 1.11.5 Huang Qiyu
2018-03-21 3:36 ` [meta-python][PATCH] python-cryptography: 2.1.4 -> 2.2 Huang Qiyu
2018-03-21 14:47 ` akuster808 [this message]
2018-03-21 3:36 ` [meta-python][PATCH] python-cryptography-vectors: " Huang Qiyu
2018-03-21 14:48 ` akuster808
2018-03-21 3:36 ` [meta-python][PATCH] python-cython: 0.27.3 -> 0.28.1 Huang Qiyu
2018-03-21 14:51 ` akuster808
2018-03-21 3:36 ` [meta-python][PATCH] python-dbus: 1.2.4 -> 1.2.6 Huang Qiyu
2018-03-21 3:36 ` [meta-python][PATCH] python-msgpack: 0.5.5 -> 0.5.6 Huang Qiyu
2018-03-21 14:49 ` akuster808
2018-03-21 3:36 ` [meta-python][PATCH] python-pip: 9.0.1 -> 9.0.2 Huang Qiyu
2018-03-21 14:49 ` akuster808
2018-03-21 3:36 ` [meta-python][PATCH] python-pytest: 3.4.1 -> 3.4.2 Huang Qiyu
2018-03-30 18:23 ` Tim Orling
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=8af916ce-0d79-7be7-172f-07abb7540e30@gmail.com \
--to=akuster808@gmail.com \
--cc=huangqy.fnst@cn.fujitsu.com \
--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