All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wang Mingyu < wangmy@fujitsu.com>
To: meta-virtualization@lists.yoctoproject.org
Cc: Wang Mingyu <wangmy@fujitsu.com>
Subject: [meta-virtualization] [meta-cloud-services] [PATCH 4/5] python3-pysnmp: replace dead pycrypto with pycryptodome and use SPDX-2 BSD-3-Clause instead of bare BSD
Date: Wed, 19 Aug 2026 17:45:11 +0800	[thread overview]
Message-ID: <20260819094512.1153-4-wangmy@fujitsu.com> (raw)
In-Reply-To: <20260819094512.1153-1-wangmy@fujitsu.com>

From: Wang Mingyu <wangmy@fujitsu.com>

pycrypto is EOL upstream and gone from oe-core; pycryptodome is the maintained fork.

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
---
 .../recipes-devtools/python/python3-pysnmp_4.4.12.bb          | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/meta-openstack/recipes-devtools/python/python3-pysnmp_4.4.12.bb b/meta-openstack/recipes-devtools/python/python3-pysnmp_4.4.12.bb
index c7acfaea..4cdd76f1 100644
--- a/meta-openstack/recipes-devtools/python/python3-pysnmp_4.4.12.bb
+++ b/meta-openstack/recipes-devtools/python/python3-pysnmp_4.4.12.bb
@@ -1,7 +1,7 @@
 DESCRIPTION = "A pure-Python SNMPv1/v2c/v3 library"
 HOMEPAGE = "https://pypi.python.org/pypi/pysnmp"
 SECTION = "devel/python"
-LICENSE = "BSD"
+LICENSE = "BSD-3-Clause"
 LIC_FILES_CHKSUM = "file://LICENSE.rst;md5=b15d29f500f748d1c2a15709769090a8"
 
 SRC_URI[md5sum] = "2222880259daf6e2cb322e938c818276"
@@ -9,6 +9,6 @@ SRC_URI[sha256sum] = "0c3dbef2f958caca96071fe5c19de43e9c1b0484ab02a0cf08b190bcee
 
 inherit setuptools3 pypi
 
-RDEPENDS:${PN} += "${PYTHON_PN}-pycrypto \
+RDEPENDS:${PN} += "${PYTHON_PN}-pycryptodome \
                    ${PYTHON_PN}-pyasn1 \
 "
-- 
2.43.0



  parent reply	other threads:[~2026-08-19  9:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-19  9:45 [meta-virtualization] [meta-cloud-services] [PATCH 1/5] python3-*: Use SPDX-2 BSD-3-Clause instead of bare BSD Wang Mingyu
2026-08-19  9:45 ` [meta-virtualization] [meta-cloud-services] [PATCH 2/5] python3-django-nose, python3-nose-exclude: drop dead python3-nose RDEPENDS and use " Wang Mingyu
2026-08-20 21:12   ` Bruce Ashfield
2026-08-19  9:45 ` [meta-virtualization] [meta-cloud-services] [PATCH 3/5] python3-pecan: migrate to python_setuptools_build_meta " Wang Mingyu
2026-08-20 21:12   ` Bruce Ashfield
2026-08-19  9:45 ` Wang Mingyu [this message]
2026-08-20 21:12   ` [meta-virtualization] [meta-cloud-services] [PATCH 4/5] python3-pysnmp: replace dead pycrypto with pycryptodome " Bruce Ashfield
2026-08-19  9:45 ` [meta-virtualization] [meta-cloud-services] [PATCH 5/5] python3-testscenarios: update to 0.6.2 Wang Mingyu
2026-08-20 21:12   ` Bruce Ashfield
2026-08-20 21:12 ` [meta-virtualization] [meta-cloud-services] [PATCH 1/5] python3-*: Use SPDX-2 BSD-3-Clause instead of bare BSD Bruce Ashfield

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=20260819094512.1153-4-wangmy@fujitsu.com \
    --to=wangmy@fujitsu.com \
    --cc=meta-virtualization@lists.yoctoproject.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.