All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Leon Anavi" <leon.anavi@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Leon Anavi <leon.anavi@konsulko.com>
Subject: [meta-python][PATCH 4/6] python3-requests-futures: Upgrade 0.9.5 -> 1.0.0
Date: Thu,  4 Jun 2020 15:12:21 +0300	[thread overview]
Message-ID: <20200604121223.3818-4-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20200604121223.3818-1-leon.anavi@konsulko.com>

Upgrade to release 1.0.0.

Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
 ...sts-futures_0.9.5.bb => python3-requests-futures_1.0.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-requests-futures_0.9.5.bb => python3-requests-futures_1.0.0.bb} (73%)

diff --git a/meta-python/recipes-devtools/python/python3-requests-futures_0.9.5.bb b/meta-python/recipes-devtools/python/python3-requests-futures_1.0.0.bb
similarity index 73%
rename from meta-python/recipes-devtools/python/python3-requests-futures_0.9.5.bb
rename to meta-python/recipes-devtools/python/python3-requests-futures_1.0.0.bb
index b94929d8c..2372ffa45 100644
--- a/meta-python/recipes-devtools/python/python3-requests-futures_0.9.5.bb
+++ b/meta-python/recipes-devtools/python/python3-requests-futures_1.0.0.bb
@@ -3,8 +3,8 @@ HOMEPAGE = "https://github.com/ross/requests-futures"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=e1e50798d0afe0e1f87594c6619a2fa5"
 
-SRC_URI[md5sum] = "e20dc6f063c70888a7f8225e349b6682"
-SRC_URI[sha256sum] = "33aa8a3b7892850701707d7e094b1e1ce7c4f7a36ff2a1dcc2da4e01a1a00f7e"
+SRC_URI[md5sum] = "601b5e90413bb00e06148752d31f0cc7"
+SRC_URI[sha256sum] = "35547502bf1958044716a03a2f47092a89efe8f9789ab0c4c528d9c9c30bc148"
 
 inherit pypi setuptools3
 
-- 
2.17.1


  parent reply	other threads:[~2020-06-04 12:12 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-04 12:12 [meta-python][PATCH 1/6] python3-dateutil: Consolidate in a single file Leon Anavi
2020-06-04 12:12 ` [meta-python][PATCH 2/6] python3-dnspython: " Leon Anavi
2020-06-05 17:26   ` [oe] " Trevor Gamblin
2020-06-04 12:12 ` [meta-python][PATCH 3/6] python3-future: " Leon Anavi
2020-06-05 17:26   ` [oe] " Trevor Gamblin
2020-06-04 12:12 ` Leon Anavi [this message]
2020-06-05 17:26   ` [oe] [meta-python][PATCH 4/6] python3-requests-futures: Upgrade 0.9.5 -> 1.0.0 Trevor Gamblin
2020-06-04 12:12 ` [meta-python][PATCH 5/6] python3-greenlet: Consolidate in a single file Leon Anavi
2020-06-05 17:26   ` [oe] " Trevor Gamblin
2020-06-04 12:12 ` [meta-python][PATCH 6/6] python3-html2text: Upgrade 2019.8.11 -> 2020.1.16 Leon Anavi
2020-06-05 18:15   ` [oe] " Trevor Gamblin
2020-06-05 17:25 ` [oe] [meta-python][PATCH 1/6] python3-dateutil: Consolidate in a single file Trevor Gamblin

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=20200604121223.3818-4-leon.anavi@konsulko.com \
    --to=leon.anavi@konsulko.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.