From: Khem Raj <raj.khem@gmail.com>
To: hongl.fnst@cn.fujitsu.com
Cc: openembeded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [PATCH] [meta-python][PATCH 1/2] python-cryptography:2.3 -> 2.3.1
Date: Wed, 19 Sep 2018 07:59:10 -0700 [thread overview]
Message-ID: <CAMKF1sq73oTGHg8hpgX3=6TnrhkOr1Lb9mOBRFRPTFv3GB69dw@mail.gmail.com> (raw)
In-Reply-To: <20180918093521.1113-1-hongl.fnst@cn.fujitsu.com>
ERROR: python3-cryptography-2.3.1-r0 do_fetch: Fetcher failure for
URL: 'https://files.pythonhosted.org/packages/source/c/cryptography/crypto
File: '/mnt/a/oe/downloads/cryptography-2.3.1.tar.gz' has md5 checksum
2b5e8269c43c9b9ab54fc8c75ba3c7ac when a0f3f563ab1c5c3bc02fae8d4aa3ad16
File: '/mnt/a/oe/downloads/cryptography-2.3.1.tar.gz' has sha256
checksum 8d10113ca826a4c29d5b85b2c4e045ffa8bad74fb525ee0eceb1d38d4c70dfd6
wh
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 r
SRC_URI[md5sum] = "2b5e8269c43c9b9ab54fc8c75ba3c7ac"
SRC_URI[sha256sum] =
"8d10113ca826a4c29d5b85b2c4e045ffa8bad74fb525ee0eceb1d38d4c70dfd6"
On Tue, Sep 18, 2018 at 2:35 AM Hong Liu <hongl.fnst@cn.fujitsu.com> wrote:
>
> 1.Upgrade python-cryptography from 2.3 to 2.3.1
>
> 2.Upgrade python3-cryptography from 2.3 to 2.3.1
>
> Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com>
> ---
> .../python/{python-cryptography_2.3.bb => python-cryptography_2.3.1.bb} | 0
> .../python/{python3-cryptography_2.3.bb => python3-cryptography_2.3.1.bb} | 0
> 2 files changed, 0 insertions(+), 0 deletions(-)
> rename meta-python/recipes-devtools/python/{python-cryptography_2.3.bb => python-cryptography_2.3.1.bb} (100%)
> rename meta-python/recipes-devtools/python/{python3-cryptography_2.3.bb => python3-cryptography_2.3.1.bb} (100%)
>
> diff --git a/meta-python/recipes-devtools/python/python-cryptography_2.3.bb b/meta-python/recipes-devtools/python/python-cryptography_2.3.1.bb
> similarity index 100%
> rename from meta-python/recipes-devtools/python/python-cryptography_2.3.bb
> rename to meta-python/recipes-devtools/python/python-cryptography_2.3.1.bb
> diff --git a/meta-python/recipes-devtools/python/python3-cryptography_2.3.bb b/meta-python/recipes-devtools/python/python3-cryptography_2.3.1.bb
> similarity index 100%
> rename from meta-python/recipes-devtools/python/python3-cryptography_2.3.bb
> rename to meta-python/recipes-devtools/python/python3-cryptography_2.3.1.bb
> --
> 2.7.4
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
prev parent reply other threads:[~2018-09-19 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 9:35 [PATCH] [meta-python][PATCH 1/2] python-cryptography:2.3 -> 2.3.1 Hong Liu
2018-09-18 9:35 ` [PATCH] [meta-python][PATCH2/2] python-cryptography-vectors: 2.3->2.3.1 Hong Liu
2018-09-19 14:58 ` Khem Raj
2018-09-18 9:35 ` [PATCH] [meta-python][PATCH] python-py:1.5.4 -> 1.6.0 Hong Liu
2018-09-19 14:59 ` Khem Raj [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='CAMKF1sq73oTGHg8hpgX3=6TnrhkOr1Lb9mOBRFRPTFv3GB69dw@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=hongl.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 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.