From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Benjamin Robin (Schneider Electric)"
<benjamin.robin@bootlin.com>,
openembedded-core@lists.openembedded.org
Cc: ross.burton@arm.com, antonin.godard@bootlin.com,
mathieu.dubois-briand@bootlin.com, thomas.petazzoni@bootlin.com
Subject: Re: [PATCH] devtool-source: set S variable to a sub dir of UNPACKDIR
Date: Thu, 16 Apr 2026 11:31:51 +0100 [thread overview]
Message-ID: <ae7097bacdb935c2dfb6b5392b31eeda9b5ebfff.camel@linuxfoundation.org> (raw)
In-Reply-To: <20260416-fix-devtool-source-v1-1-3a9b689fbe16@bootlin.com>
On Thu, 2026-04-16 at 10:14 +0200, Benjamin Robin (Schneider Electric) wrote:
> If a recipe set UNPACKDIR to a directory that is not contained within
> WORKDIR, before this modification, this generates the following error:
> "S should be set relative to UNPACKDIR."
>
> S should not be updated, otherwise the recipe may not find the extracted
> sources. In all recipes, S should reference the UNPACKDIR variable.
> There is an exception for the kernel to prevent infinite recursion
> when expanding the STAGING_KERNEL_DIR variable.
>
> So, only updates UNPACKDIR to be within the DEVTOOL_TEMPDIR directory.
>
> Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
> ---
> I have done various testing, but since I don't know all the requirements
> of devtool, and all the impacts of this change, I may have broken some
> stuff (I hope not).
>
> This patch fixes the following command:
> - devtool upgrade sbom-cve-check-update-cvelist-native
>
> It does not break the following commands:
> - devtool upgrade linux-yocto
> - devtool upgrade python3-sbom-cve-check
For reference devtool has a strong test suite and you can run it with
"oe-selftest -r devtool".
Cheers,
Richard
prev parent reply other threads:[~2026-04-16 10:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 8:14 [PATCH] devtool-source: set S variable to a sub dir of UNPACKDIR Benjamin Robin (Schneider Electric)
2026-04-16 10:31 ` Richard Purdie [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=ae7097bacdb935c2dfb6b5392b31eeda9b5ebfff.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=antonin.godard@bootlin.com \
--cc=benjamin.robin@bootlin.com \
--cc=mathieu.dubois-briand@bootlin.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=thomas.petazzoni@bootlin.com \
/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