Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Yoann Congal" <yoann.congal@smile.fr>
To: <daniel.turull@ericsson.com>, <openembedded-core@lists.openembedded.org>
Cc: <JPEWhacker@gmail.com>, <mathieu.dubois-briand@bootlin.com>
Subject: Re: [OE-core] [PATCH v3 0/3] spdx: add support to include releaseTime
Date: Tue, 29 Sep 2026 08:16:12 +0200	[thread overview]
Message-ID: <DLRKWLFNOLML.3NT9JU6NO87KG@smile.fr> (raw)
In-Reply-To: <20260928190400.3908822-1-daniel.turull@ericsson.com>

On Mon Sep 28, 2026 at 9:03 PM CEST, Daniel Turull via lists.openembedded.org wrote:
> From: Daniel Turull <daniel.turull@ericsson.com>
>
> We have a requirements to include release time of open source components
> in the SBOM. There is a field specific for that in spdx 3 spec.
>
> https://spdx.github.io/spdx-spec/v3.0.1/model/Core/Properties/releaseTime/
>
> This can also be used to evaluate how old are some of the core
> components and decide if they need replacement.
>
> The previous 2 versions did not have cover letter.
>
> Tested with oe-selftest -r spdx
>
> Daniel Turull (3):
>   classes/base: exclude __CACHED_SOURCE_DATE_EPOCH from task hash
>   create-spdx-3.0: record component release date in SPDX output
>   scripts/contrib: add spdx-release-date-report.py
>
>  meta/classes-global/base.bbclass            |   4 +
>  meta/classes/create-spdx-3.0.bbclass        |   2 +-
>  meta/lib/oe/spdx30_tasks.py                 |  19 ++
>  meta/lib/oeqa/selftest/cases/spdx.py        |  39 ++++
>  scripts/contrib/spdx-release-date-report.py | 193 ++++++++++++++++++++
>  5 files changed, 256 insertions(+), 1 deletion(-)
>  create mode 100755 scripts/contrib/spdx-release-date-report.py

Hello,

Note: while this is not a fix, this looks related to
https://bugzilla.yoctoproject.org/show_bug.cgi?id=15530

Thanks!
-- 
Yoann Congal
Smile ECS



  parent reply	other threads:[~2026-09-29  6:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-28 19:03 [PATCH v3 0/3] spdx: add support to include releaseTime daniel.turull
2026-09-28 19:03 ` [PATCH v3 1/3] classes/base: exclude __CACHED_SOURCE_DATE_EPOCH from task hash daniel.turull
2026-09-29 14:53   ` Joshua Watt
2026-09-28 19:03 ` [PATCH v3 2/3] create-spdx-3.0: record component release date in SPDX output daniel.turull
2026-09-28 20:59   ` [OE-core] " Richard Purdie
2026-09-29  4:54     ` Daniel Turull
2026-09-28 19:04 ` [PATCH v3 3/3] scripts/contrib: add spdx-release-date-report.py daniel.turull
2026-09-29  6:16 ` Yoann Congal [this message]
2026-09-29  6:36   ` [OE-core] [PATCH v3 0/3] spdx: add support to include releaseTime Daniel Turull

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=DLRKWLFNOLML.3NT9JU6NO87KG@smile.fr \
    --to=yoann.congal@smile.fr \
    --cc=JPEWhacker@gmail.com \
    --cc=daniel.turull@ericsson.com \
    --cc=mathieu.dubois-briand@bootlin.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