From: "Jörg Sommer" <joerg.sommer@navimatix.de>
To: Joshua Watt <jpewhacker@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core][PATCH] Remove SPDX 2.2 support
Date: Thu, 26 Mar 2026 10:43:39 +0100 [thread overview]
Message-ID: <acT_KkDva9SHEzxc@navimatix.de> (raw)
In-Reply-To: <CAJdd5GYyaYytJPp=ruw4bP9yVxHnfFS8C1KG6+GMPQAiswpV=Q@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Joshua Watt schrieb am Mi 25. Mär, 16:17 (-0600):
> On Wed, Mar 25, 2026 at 1:56 PM Jörg Sommer <joerg.sommer@navimatix.de> wrote:
> >
> > Joshua Watt via lists.openembedded.org schrieb am Mi 25. Mär, 11:16 (-0600):
> > > Removes SPDX 2.2 support in favor of SPDX 3 support being the only
> > > option. The SPDX 3 data is far superior to SPDX 2.2 and thus more useful
> > > for SBoM uses cases.
> >
> > s/uses/use/
> >
> > Could this be delayed until after the release of 6.0, so 6.0 would contain
> > SPDX 2.2 support? For internal tools we still use SPDX 2.2
>
> We already had discussion on the OE arch list:
> https://lists.openembedded.org/g/openembedded-architecture/topic/proposal_to_drop_spdx_2_2/118281203
> please feel free to chime in there.
Thanks for the link. This helps to argue that our tools must be updated.
--
Navimatix GmbH T: 03641 - 327 99 0
Tatzendpromenade 2 F: 03641 - 526 306
07745 Jena www.navimatix.de
Geschäftsführer: Steffen Späthe, Jan Rommeley
Registergericht: Amtsgericht Jena, HRB 501480
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5000 bytes --]
prev parent reply other threads:[~2026-03-26 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 17:16 [OE-core][PATCH] Remove SPDX 2.2 support Joshua Watt
2026-03-25 17:30 ` Patchtest results for " patchtest
2026-03-25 17:39 ` Daniel Turull
2026-03-25 19:17 ` Joshua Watt
2026-03-25 19:56 ` Jörg Sommer
2026-03-25 22:17 ` Joshua Watt
2026-03-26 9:43 ` Jörg Sommer [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=acT_KkDva9SHEzxc@navimatix.de \
--to=joerg.sommer@navimatix.de \
--cc=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