From: Leon Anavi <leon.anavi@konsulko.com>
To: openembedded-devel@lists.openembedded.org
Cc: Leon Anavi <leon.anavi@konsulko.com>
Subject: [meta-python][PATCH 2/2] python3-croniter: Upgrade 1.2.0 -> 1.3.4
Date: Mon, 21 Feb 2022 21:22:56 +0200 [thread overview]
Message-ID: <20220221192256.3347297-2-leon.anavi@konsulko.com> (raw)
In-Reply-To: <20220221192256.3347297-1-leon.anavi@konsulko.com>
Upgrade to release 1.3.4:
- Add a way to make next() easier to use
- Restore compat with python2
- Fix regressions with set_current
- Fix compat for tests under py27
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
---
.../{python3-croniter_1.2.0.bb => python3-croniter_1.3.4.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta-python/recipes-devtools/python/{python3-croniter_1.2.0.bb => python3-croniter_1.3.4.bb} (78%)
diff --git a/meta-python/recipes-devtools/python/python3-croniter_1.2.0.bb b/meta-python/recipes-devtools/python/python3-croniter_1.3.4.bb
similarity index 78%
rename from meta-python/recipes-devtools/python/python3-croniter_1.2.0.bb
rename to meta-python/recipes-devtools/python/python3-croniter_1.3.4.bb
index 13dbf155c..4158dbe7c 100644
--- a/meta-python/recipes-devtools/python/python3-croniter_1.2.0.bb
+++ b/meta-python/recipes-devtools/python/python3-croniter_1.3.4.bb
@@ -5,7 +5,7 @@ LIC_FILES_CHKSUM = "file://docs/LICENSE;md5=b8ee59850b882cbf623188489ea748e2"
PYPI_PACKAGE = "croniter"
-SRC_URI[sha256sum] = "094422f6aeb9ed646714393503fa388afe4f846e110e1997fea5794e2085c2d7"
+SRC_URI[sha256sum] = "3169365916834be654c2cac57ea14d710e742f8eb8a5fce804f6ce548da80bf2"
inherit pypi setuptools3
--
2.30.2
prev parent reply other threads:[~2022-02-21 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 19:22 [meta-python][PATCH 1/2] python3-itsdangerous: Upgrade 2.0.1 -> 2.1.0 Leon Anavi
2022-02-21 19:22 ` Leon Anavi [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=20220221192256.3347297-2-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.