All of lore.kernel.org
 help / color / mirror / Atom feed
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][PATCH2/2] python-cryptography-vectors: 2.3->2.3.1
Date: Wed, 19 Sep 2018 07:58:31 -0700	[thread overview]
Message-ID: <CAMKF1soScJH3oM9gPf7-n3quWcdvLP8iEVAgKK9L3gfVJG5ziw@mail.gmail.com> (raw)
In-Reply-To: <20180918093521.1113-2-hongl.fnst@cn.fujitsu.com>

ERROR: python3-cryptography-vectors-2.3.1-r0 do_fetch: Fetcher failure
for URL: 'https://files.pythonhosted.org/packages/source/c/cryptograph
File: '/mnt/a/oe/downloads/cryptography_vectors-2.3.1.tar.gz' has md5
checksum 9c8259889ab84b456459fc3fc3d185f4 when
294d44f32885a6b97d5f9cdd
File: '/mnt/a/oe/downloads/cryptography_vectors-2.3.1.tar.gz' has
sha256 checksum
bf4d9b61dce69c49e830950aa36fad194706463b0b6dfe81425b9e0bc66
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] = "9c8259889ab84b456459fc3fc3d185f4"
SRC_URI[sha256sum] =
"bf4d9b61dce69c49e830950aa36fad194706463b0b6dfe81425b9e0bc6644d46"
Otherwise you should retry the download and/or check with upstream to
determine if the file has become corrupted or otherwise
On Tue, Sep 18, 2018 at 2:35 AM Hong Liu <hongl.fnst@cn.fujitsu.com> wrote:
>
> 1.Upgrade python-cryptography-vectors from 2.3 to 2.3.1
>
> 2.Upgrade python3-cryptography-vectors from 2.3 to 2.3.1
>
> Signed-off-by: Hong Liu <hongl.fnst@cn.fujitsu.com>
> ---
>  ...n-cryptography-vectors_2.3.bb => python-cryptography-vectors_2.3.1.bb} | 0
>  ...-cryptography-vectors_2.3.bb => python3-cryptography-vectors_2.3.1.bb} | 0
>  2 files changed, 0 insertions(+), 0 deletions(-)
>  rename meta-python/recipes-devtools/python/{python-cryptography-vectors_2.3.bb => python-cryptography-vectors_2.3.1.bb} (100%)
>  rename meta-python/recipes-devtools/python/{python3-cryptography-vectors_2.3.bb => python3-cryptography-vectors_2.3.1.bb} (100%)
>
> diff --git a/meta-python/recipes-devtools/python/python-cryptography-vectors_2.3.bb b/meta-python/recipes-devtools/python/python-cryptography-vectors_2.3.1.bb
> similarity index 100%
> rename from meta-python/recipes-devtools/python/python-cryptography-vectors_2.3.bb
> rename to meta-python/recipes-devtools/python/python-cryptography-vectors_2.3.1.bb
> diff --git a/meta-python/recipes-devtools/python/python3-cryptography-vectors_2.3.bb b/meta-python/recipes-devtools/python/python3-cryptography-vectors_2.3.1.bb
> similarity index 100%
> rename from meta-python/recipes-devtools/python/python3-cryptography-vectors_2.3.bb
> rename to meta-python/recipes-devtools/python/python3-cryptography-vectors_2.3.1.bb
> --
> 2.7.4
>
>
>
> --
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-devel


  reply	other threads:[~2018-09-19 14:58 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 [this message]
2018-09-18  9:35 ` [PATCH] [meta-python][PATCH] python-py:1.5.4 -> 1.6.0 Hong Liu
2018-09-19 14:59 ` [PATCH] [meta-python][PATCH 1/2] python-cryptography:2.3 -> 2.3.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=CAMKF1soScJH3oM9gPf7-n3quWcdvLP8iEVAgKK9L3gfVJG5ziw@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.