Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>
To: <hongxu.jia@eng.windriver.com>,
	<openembedded-core@lists.openembedded.org>,
	<jpewhacker@gmail.com>
Subject: Re: [OE-core] [PATCH 1/4] meta/lib/oe/sbom30.py: correct alias
Date: Tue, 17 Dec 2024 08:37:40 +0100	[thread overview]
Message-ID: <D6DSYBCD4I4G.2O4ZDW15ZPJ1S@bootlin.com> (raw)
In-Reply-To: <20241217034724.2737515-1-hongxu.jia@windriver.com>

On Tue Dec 17, 2024 at 4:47 AM CET, hongxu via lists.openembedded.org wrote:
> After commit [spdx 3.0: Rework how SPDX aliases are linked] applied,
> it added extra "/" to namespace, which causing the replacement of
> UNIHASH missing a "/"
>
>   http://spdxdocs.org/openembedded-alias/by-doc-hash/0b308e4b9ad979f642d8787c61f76c31bdcad04837eeaaf8bc383f33f99bbeb8/flex-nativeUNIHASH/build/recipe
>
> After applying this commit to remove "/" from namespace.
>
>   http://spdxdocs.org/openembedded-alias/by-doc-hash/0b308e4b9ad979f642d8787c61f76c31bdcad04837eeaaf8bc383f33f99bbeb8/flex-native/UNIHASH/build/recipe
>
> Signed-off-by: Hongxu Jia <hongxu.jia@windriver.com>
> ---

Hi Hongxu,

Sorry, but I still get the SPDX IDs were unable to be resolved warning.
E.g.:

WARNING: core-image-sato-sdk-1.0-r0 do_create_image_sbom_spdx: The following SPDX IDs were unable to be resolved:
  http://spdxdocs.org/openembedded-alias/by-doc-hash/82b2ddffbd624bcb26b4c93f8e7bf31e456ea81a1e5720354726d1fc7e433dd0/openssl/UNIHASH/package/openssl-bin
  http://spdxdocs.org/openembedded-alias/by-doc-hash/882a5d190518b194aea7380573eeee8a79f524131463308e414d0cb51f9a8099/openssl/UNIHASH/package/openssl
  http://spdxdocs.org/openembedded-alias/by-doc-hash/974e7ddc5b8f9307c770783e7d96e9e9fc65cd5b3f9cdd5a8578e4ed121dd8d1/initscripts/UNIHASH/build/recipe
  http://spdxdocs.org/openembedded-alias/by-doc-hash/f63cc948b407d32cfacbfc288d66c3fb64a6a611debfd7989d2cda55d7a957ca/openssh/UNIHASH/package/openssh

https://valkyrie.yoctoproject.org/#/builders/6/builds/668/steps/12/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/8/builds/666/steps/15/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/9/builds/646/steps/12/logs/stdio

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com



  parent reply	other threads:[~2024-12-17  7:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  3:47 [PATCH 1/4] meta/lib/oe/sbom30.py: correct alias Hongxu Jia
2024-12-17  3:47 ` [PATCH 2/4] meta/lib/oe/spdx30_tasks.py: fix hash link conflict while multiconfig enabled Hongxu Jia
2024-12-17  3:47 ` [PATCH V2 3/4] gcc-cross.inc: add var-SSTATE_ARCHS_TUNEPKG to vardeps of do_create_spdx Hongxu Jia
2024-12-17  3:47 ` [PATCH V3 4/4] meta/lib/oe/sbom30.py: fix alias in simplelicensing_customIdToUri not extracted Hongxu Jia
2024-12-17  7:37 ` Mathieu Dubois-Briand [this message]
2024-12-17 12:49   ` [PATCH 1/4] meta/lib/oe/sbom30.py: correct alias hongxu
2024-12-20 16:09     ` [OE-core] " Mathieu Dubois-Briand
2024-12-25  2:41       ` Hongxu Jia

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=D6DSYBCD4I4G.2O4ZDW15ZPJ1S@bootlin.com \
    --to=mathieu.dubois-briand@bootlin.com \
    --cc=hongxu.jia@eng.windriver.com \
    --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