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 5/5] python3-incremental: Upgrade 17.5.0 -> 21.3.0
Date: Mon,  8 Mar 2021 18:18:10 +0200	[thread overview]
Message-ID: <20210308161810.21582-5-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20210308161810.21582-1-leon.anavi@konsulko.com>

Upgrade to release 21.3.0:

- The output of incremental is now compatible with Black
- Incremental now properly supports PEP 440-compliant dev, rc,
  post suffixes
- Incremental now properly supports PEP 440-compliant post
  releases

Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
 ...on3-incremental_17.5.0.bb => python3-incremental_21.3.0.bb} | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)
 rename meta-python/recipes-devtools/python/{python3-incremental_17.5.0.bb => python3-incremental_21.3.0.bb} (82%)

diff --git a/meta-python/recipes-devtools/python/python3-incremental_17.5.0.bb b/meta-python/recipes-devtools/python/python3-incremental_21.3.0.bb
similarity index 82%
rename from meta-python/recipes-devtools/python/python3-incremental_17.5.0.bb
rename to meta-python/recipes-devtools/python/python3-incremental_21.3.0.bb
index 568ba1989..ff8fab31f 100644
--- a/meta-python/recipes-devtools/python/python3-incremental_17.5.0.bb
+++ b/meta-python/recipes-devtools/python/python3-incremental_21.3.0.bb
@@ -3,8 +3,7 @@ HOMEPAGE = "https://github.com/twisted/incremental"
 LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=6ca9b07f08e2c72d48c74d363d1e0e15"
 
-SRC_URI[md5sum] = "602746e0d438e075a5a9e0678140bba2"
-SRC_URI[sha256sum] = "7b751696aaf36eebfab537e458929e194460051ccad279c72b755a167eebd4b3"
+SRC_URI[sha256sum] = "02f5de5aff48f6b9f665d99d48bfc7ec03b6e3943210de7cfc88856d755d6f57"
 
 inherit pypi setuptools3
 
-- 
2.17.1


  parent reply	other threads:[~2021-03-08 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-08 16:18 [meta-python][PATCH 1/5] python3-ruamel-yaml: Upgrade 0.16.12 -> 0.16.13 Leon Anavi
2021-03-08 16:18 ` [meta-python][PATCH 2/5] python3-prettytable: Upgrade 2.0.0 -> 2.1.0 Leon Anavi
2021-03-10 16:46   ` [oe] " Trevor Gamblin
2021-03-08 16:18 ` [meta-python][PATCH 3/5] python3-huey: Upgrade 2.3.0 -> 2.3.1 Leon Anavi
2021-03-10 16:46   ` [oe] " Trevor Gamblin
2021-03-08 16:18 ` [meta-python][PATCH 4/5] python3-pychromecast: Upgrade 8.1.0 -> 9.1.1 Leon Anavi
2021-03-10 16:46   ` [oe] " Trevor Gamblin
2021-03-08 16:18 ` Leon Anavi [this message]
2021-03-10 16:47   ` [oe] [meta-python][PATCH 5/5] python3-incremental: Upgrade 17.5.0 -> 21.3.0 Trevor Gamblin
2021-03-10 16:46 ` [oe] [meta-python][PATCH 1/5] python3-ruamel-yaml: Upgrade 0.16.12 -> 0.16.13 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=20210308161810.21582-5-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.