From: Joshua Watt <jpewhacker@gmail.com>
To: openembedded-core@lists.openembedded.org
Cc: Joshua Watt <JPEWhacker@gmail.com>
Subject: [OE-core][PATCH 0/3] Fix incomplete license expressions being preferred over complete ones
Date: Mon, 26 Oct 2026 16:06:32 -0600 [thread overview]
Message-ID: <20261026220751.2480577-1-JPEWhacker@gmail.com> (raw)
Fixes a bug where an incomplete (missing the actual license text) could
be preferred over the same expression that included the license text.
Joshua Watt (3):
lib/oe/license.py: Fix documentation of parse_legacy_license()
lib/oe/sbom.py: Fix partial licenses masking complete ones
lib/oe/sbom.py: Split deduplication of CreationInfo
meta/lib/oe/license.py | 4 +-
meta/lib/oe/sbom30.py | 107 +++++++++++++++++++++++++++++++++--------
2 files changed, 88 insertions(+), 23 deletions(-)
--
2.56.0
next reply other threads:[~2026-10-26 22:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 22:06 Joshua Watt [this message]
2026-10-26 22:06 ` [OE-core][PATCH 1/3] lib/oe/license.py: Fix documentation of parse_legacy_license() Joshua Watt
2026-10-26 22:06 ` [OE-core][PATCH 2/3] lib/oe/sbom.py: Fix partial licenses masking complete ones Joshua Watt
2026-10-26 22:06 ` [OE-core][PATCH 3/3] lib/oe/sbom.py: Split deduplication of CreationInfo Joshua Watt
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=20261026220751.2480577-1-JPEWhacker@gmail.com \
--to=jpewhacker@gmail.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