From: Bruce Ashfield <bruce.ashfield@gmail.com>
To: meta-virtualization@lists.yoctoproject.org
Subject: Re: [meta-virtualization] [meta-cloud-services] [PATCH] fix license error
Date: Fri, 07 Aug 2026 11:55:41 -0700 (PDT) [thread overview]
Message-ID: <6a762a2d.0a531e61.138fdb.127d@mx.google.com> (raw)
In-Reply-To: <20260807025036.1571-1-wangmy@fujitsu.com>
Hi Wang,
Individually each of these changes looks right, but the commit as
posted bundles ~5 unrelated fixes under "fix license error" and I'd
like a v2 split before I take them. Bisect-hostile if any one turns
out to have side effects, and the subject undersells (and mis-names)
most of what's in there.
Suggested split, one commit per logical change:
1. python3-*: use SPDX-2 BSD-3-Clause instead of bare BSD
The 11 recipes that just swap LICENSE = "BSD" for
LICENSE = "BSD-3-Clause". Pure license syntax cleanup, matches
what OE-core is asking for.
2. python3-django-nose, python3-nose-exclude: drop dead python3-nose
RDEPENDS
python3-nose is Python-2-era and has been removed upstream. The
django-nose swap to python3-nose-exclude belongs here too.
3. python3-pecan: migrate to python_setuptools_build_meta
PEP 517 backend switch + the scripts= sed in setup.py. Not a
license fix.
4. python3-pysnmp: replace dead pycrypto with pycryptodome
pycrypto is EOL upstream and gone from oe-core; pycryptodome is
the maintained fork.
5. python3-testscenarios: update to 0.6.2
PV bump, dual-license update to "Apache-2.0 OR BSD-3-Clause",
backend switch to python_hatchling, dependencies. All belongs
together as one version-bump commit.
The 12006 open-iscsi-kernel removal I've taken as-is, thanks.
Bruce
prev parent reply other threads:[~2026-08-07 18:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 2:50 [meta-virtualization] [meta-cloud-services] [PATCH] fix license error Wang Mingyu
2026-08-07 2:50 ` [meta-virtualization] [meta-cloud-services] [PATCH] open-iscsi-kernel: remove recipe Wang Mingyu
2026-08-07 18:55 ` Bruce Ashfield [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=6a762a2d.0a531e61.138fdb.127d@mx.google.com \
--to=bruce.ashfield@gmail.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.