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]python-cryptography:upgrade to 2.4
Date: Wed, 5 Dec 2018 08:55:33 -0800 [thread overview]
Message-ID: <CAMKF1soNSAGuEWey2BiEvE0ekDJ6XC2bE8Kyh1OJ6=-L+kS_RA@mail.gmail.com> (raw)
In-Reply-To: <20181205012446.28018-2-hongl.fnst@cn.fujitsu.com>
http://errors.yoctoproject.org/Errors/Details/203490/ plrase upgrade
py3 version too
On Tue, Dec 4, 2018 at 5:23 PM Hong Liu <hongl.fnst@cn.fujitsu.com> wrote:
>
> 1.Upgrade python-cryptography from 2.3 to 2.4
>
> Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com>
> ---
> meta-python/recipes-devtools/python/python-cryptography.inc | 4 ++--
> .../{python-cryptography_2.3.bb => python-cryptography_2.4.1.bb} | 0
> 2 files changed, 2 insertions(+), 2 deletions(-)
> rename meta-python/recipes-devtools/python/{python-cryptography_2.3.bb => python-cryptography_2.4.1.bb} (100%)
>
> diff --git a/meta-python/recipes-devtools/python/python-cryptography.inc b/meta-python/recipes-devtools/python/python-cryptography.inc
> index dbbfe2c..0e53d95 100644
> --- a/meta-python/recipes-devtools/python/python-cryptography.inc
> +++ b/meta-python/recipes-devtools/python/python-cryptography.inc
> @@ -10,8 +10,8 @@ DEPENDS += " \
> ${PYTHON_PN}-six \
> "
>
> -SRC_URI[md5sum] = "a0f3f563ab1c5c3bc02fae8d4aa3ad16"
> -SRC_URI[sha256sum] = "c132bab45d4bd0fff1d3fe294d92b0a6eb8404e93337b3127bdec9f21de117e6"
> +SRC_URI[md5sum] = "464f180ff64622760cca7167f97b3ff4"
> +SRC_URI[sha256sum] = "e85b410885addaeb31a867eabcefc9ef4a7e904ad45eac9e60a763a54b244626"
>
> RDEPENDS_${PN} += " \
> ${PYTHON_PN}-cffi \
> diff --git a/meta-python/recipes-devtools/python/python-cryptography_2.3.bb b/meta-python/recipes-devtools/python/python-cryptography_2.4.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.4.1.bb
> --
> 2.7.4
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel
next prev parent reply other threads:[~2018-12-05 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 1:24 [PATCH] [meta-python][PATCH] python-cryptography-vectors:upgrade to 2.4.1 Hong Liu
2018-12-05 1:24 ` [PATCH] [meta-python][PATCH]python-cryptography:upgrade to 2.4 Hong Liu
2018-12-05 16:55 ` Khem Raj [this message]
2018-12-05 16:56 ` [PATCH] [meta-python][PATCH] python-cryptography-vectors:upgrade to 2.4.1 Khem Raj
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='CAMKF1soNSAGuEWey2BiEvE0ekDJ6XC2bE8Kyh1OJ6=-L+kS_RA@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.