openembedded-devel.lists.openembedded.org archive mirror
 help / color / mirror / Atom feed
From: wangmy@fujitsu.com
To: openembedded-devel@lists.openembedded.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [oe] [meta-python] [PATCH] python3-license-expression: upgrade 30.1.0 -> 30.1.1
Date: Wed, 31 May 2023 15:40:13 +0800	[thread overview]
Message-ID: <1685518820-20028-15-git-send-email-wangmy@fujitsu.com> (raw)
In-Reply-To: <1685518820-20028-1-git-send-email-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

Changelog:
=============
    Use latest skeleton
    Update license list to latest ScanCode and SPDX 3.20

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 ...xpression_30.1.0.bb => python3-license-expression_30.1.1.bb} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
 rename meta-python/recipes-devtools/python/{python3-license-expression_30.1.0.bb => python3-license-expression_30.1.1.bb} (90%)

diff --git a/meta-python/recipes-devtools/python/python3-license-expression_30.1.0.bb b/meta-python/recipes-devtools/python/python3-license-expression_30.1.1.bb
similarity index 90%
rename from meta-python/recipes-devtools/python/python3-license-expression_30.1.0.bb
rename to meta-python/recipes-devtools/python/python3-license-expression_30.1.1.bb
index 5dfd02be4..31fb88d6e 100644
--- a/meta-python/recipes-devtools/python/python3-license-expression_30.1.0.bb
+++ b/meta-python/recipes-devtools/python/python3-license-expression_30.1.1.bb
@@ -4,7 +4,7 @@ HOMEPAGE = "https://github.com/nexB/license-expression"
 LICENSE = "Apache-2.0"
 LIC_FILES_CHKSUM = "file://apache-2.0.LICENSE;md5=86d3f3a95c324c9479bd8986968f4327"
 
-SRC_URI[sha256sum] = "943b1d2cde251bd30a166b509f78990fdd060be9750f3f1a324571e804857a53"
+SRC_URI[sha256sum] = "42375df653ad85e6f5b4b0385138b2dbea1f5d66360783d8625c3e4f97f11f0c"
 
 inherit pypi ptest python_setuptools_build_meta
 
-- 
2.34.1



  parent reply	other threads:[~2023-05-31  7:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  7:39 [oe] [meta-oe] [PATCH] ctags: upgrade 6.0.20230521.0 -> 6.0.20230528.0 wangmy
2023-05-31  7:40 ` [oe] [meta-gnome] [PATCH] eog: upgrade 44.1 -> 44.2 wangmy
2023-05-31  7:40 ` [oe] [meta-gnome] [PATCH] nautilus: " wangmy
2023-05-31  7:40 ` [oe] [meta-gnome] [PATCH] evolution-data-server: upgrade 3.48.1 -> 3.48.2 wangmy
2023-05-31  7:40 ` [oe] [meta-oe] [PATCH] flatbuffers: upgrade 23.1.4 -> 23.3.56 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-asgiref: upgrade 3.7.1 -> 3.7.2 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-bitarray: upgrade 2.7.3 -> 2.7.4 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-cachetools: upgrade 5.3.0 -> 5.3.1 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-coverage: upgrade 7.2.6 -> 7.2.7 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-croniter: upgrade 1.3.14 -> 1.3.15 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-deprecated: upgrade 1.2.13 -> 1.2.14 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-google-api-python-client: upgrade 2.86.0 -> 2.87.0 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-google-auth: upgrade 2.18.1 -> 2.19.0 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-imageio: upgrade 2.29.0 -> 2.30.0 wangmy
2023-05-31  7:40 ` wangmy [this message]
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-lru-dict: upgrade 1.1.8 -> 1.2.0 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-paramiko: upgrade 3.1.0 -> 3.2.0 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-pint: upgrade 0.21 -> 0.22 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-protobuf: upgrade 4.23.1 -> 4.23.2 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-xlsxwriter: upgrade 3.1.1 -> 3.1.2 wangmy
2023-05-31  7:40 ` [oe] [meta-python] [PATCH] python3-zeroconf: upgrade 0.62.0 -> 0.63.0 wangmy
2023-05-31  7:40 ` [oe] [meta-oe] [PATCH] xterm: upgrade 380 -> 381 wangmy

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=1685518820-20028-15-git-send-email-wangmy@fujitsu.com \
    --to=wangmy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).