All of lore.kernel.org
 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/3] meta/lib/oe/sbom30.py: correct alias
Date: Wed, 11 Dec 2024 18:03:54 +0100	[thread overview]
Message-ID: <D6918L62GCW9.139TWVMC398ET@bootlin.com> (raw)
In-Reply-To: <20241211120728.3737604-1-hongxu.jia@windriver.com>

On Wed Dec 11, 2024 at 1:07 PM 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,

We have some warnings on the autobuilder while picking these patches,
such as:

WARNING: core-image-sato-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/7f7bda815cc04b5b265ac8602753d177a96016826f71217624323d1afbb6a65e/gdk-pixbuf/UNIHASH/build/recipe
  http://spdxdocs.org/openembedded-alias/by-doc-hash/c0aa4c9cb1de03839f2a5e077627543f00e6269d6a16bfccf156b395df054f2d/gtk+3/UNIHASH/build/recipe

https://valkyrie.yoctoproject.org/#/builders/13/builds/557/steps/13/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/89/builds/579/steps/17/logs/stdio
https://valkyrie.yoctoproject.org/#/builders/95/builds/610/steps/13/logs/stdio

Can you have a look at this issue please ?

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



      parent reply	other threads:[~2024-12-11 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-11 12:07 [PATCH 1/3] meta/lib/oe/sbom30.py: correct alias Hongxu Jia
2024-12-11 12:07 ` [PATCH 2/3] meta/lib/oe/spdx30_tasks.py: fix hash link conflict while multiconfig enabled Hongxu Jia
2024-12-11 12:07 ` [PATCH 3/3] gcc-cross.inc: add var-SSTATE_ARCHS_TUNEPKG to vardeps of do_create_spdx Hongxu Jia
2024-12-11 15:33   ` Joshua Watt
2024-12-11 16:11     ` hongxu
2024-12-11 17:03 ` Mathieu Dubois-Briand [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=D6918L62GCW9.139TWVMC398ET@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 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.