From: Liu Yiding <liuyd.fnst@fujitsu.com>
To: openembedded-core@lists.openembedded.org
Subject: [OE-core][PATCH v3] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0
Date: Mon, 12 Jan 2026 18:10:27 +0800 [thread overview]
Message-ID: <20260112101027.7153-1-liuyd.fnst@fujitsu.com> (raw)
1. Upstream has renamed roman_numerals-py to roman_numerals
https://pypi.org/project/roman-numerals-py/4.1.0/
2. Changelog
https://github.com/AA-Turner/roman-numerals/blob/master/CHANGES.rst
Signed-off-by: Liu Yiding <liuyd.fnst@fujitsu.com>
---
...numerals-py_3.1.0.bb => python3-roman-numerals_4.1.0.bb} | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
rename meta/recipes-devtools/python/{python3-roman-numerals-py_3.1.0.bb => python3-roman-numerals_4.1.0.bb} (60%)
diff --git a/meta/recipes-devtools/python/python3-roman-numerals-py_3.1.0.bb b/meta/recipes-devtools/python/python3-roman-numerals_4.1.0.bb
similarity index 60%
rename from meta/recipes-devtools/python/python3-roman-numerals-py_3.1.0.bb
rename to meta/recipes-devtools/python/python3-roman-numerals_4.1.0.bb
index 9a76df0de2..7a97fd3b19 100644
--- a/meta/recipes-devtools/python/python3-roman-numerals-py_3.1.0.bb
+++ b/meta/recipes-devtools/python/python3-roman-numerals_4.1.0.bb
@@ -3,9 +3,9 @@ HOMEPAGE = "https://github.com/AA-Turner/roman-numerals/"
LICENSE = "0BSD & CC0-1.0"
LIC_FILES_CHKSUM = "file://LICENCE.rst;md5=bfcc8b16e42929aafeb9d414360bc2fd"
-SRC_URI[sha256sum] = "be4bf804f083a4ce001b5eb7e3c0862479d10f94c936f6c4e5f250aa5ff5bd2d"
-PYPI_PACKAGE = "roman_numerals_py"
-UPSTREAM_CHECK_PYPI_PACKAGE = "roman_numerals_py"
+SRC_URI[sha256sum] = "1af8b147eb1405d5839e78aeb93131690495fe9da5c91856cb33ad55a7f1e5b2"
+PYPI_PACKAGE = "roman_numerals"
+UPSTREAM_CHECK_PYPI_PACKAGE = "roman_numerals"
inherit pypi python_flit_core
--
2.43.0
next reply other threads:[~2026-01-12 10:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-12 10:10 Liu Yiding [this message]
2026-01-12 10:24 ` [PATCH v3] python3-roman-numerals-py: upgrade 3.1.0 -> 4.1.0 Varatharajan, Deepesh
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=20260112101027.7153-1-liuyd.fnst@fujitsu.com \
--to=liuyd.fnst@fujitsu.com \
--cc=openembedded-core@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox