From: Richard Purdie <firstname.lastname@example.org>
To: email@example.com, firstname.lastname@example.org
Subject: Re: [bitbake-devel] Problems having both git and npmsw sources in recipe #bitbake
Date: Fri, 14 Apr 2023 17:08:08 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On Fri, 2023-04-14 at 04:41 -0700, firstname.lastname@example.org wrote:
> I have posted the following topic under the group Openembedded-issues. I am a little unsure if that is the right place, as there seems to be little or no activity in that group?
> Openembeddedemail@example.com | Problems having both git and npmsw sources in recipe
> I am experiencing problems with a recipe where I have both a git and a npmsw source in the SRC_URI. It seems that when the fetcher is fetching from the shrinkwrap, the SRCREV variable has been deleted but it still ends up fetching from the git source resulting in an error because SRCREV is undefined.
> The problem occurs because the Fetch class defaults to the value of SRC_URI if the urls parameter contains an empty list. The following change to the npmsw.py file seems to solve the problem:
> diff --git a/bitbake/lib/bb/fetch2/npmsw.py b/bitbake/lib/bb/fetch2/npmsw.py
> index a8c4d3528f..4d700a537a 100644
> --- a/bitbake/lib/bb/fetch2/npmsw.py
> +++ b/bitbake/lib/bb/fetch2/npmsw.py
> @@ -193,7 +193,9 @@ class NpmShrinkWrap(FetchMethod):
> # This fetcher resolves multiple URIs from a shrinkwrap file and then
> # forwards it to a proxy fetcher. The management of the donestamp file,
> # the lockfile and the checksums are forwarded to the proxy fetcher.
> - ud.proxy = Fetch([dep["url"] for dep in ud.deps if dep["url"]], data)
> + shrinkwrap_urls = [dep["url"] for dep in ud.deps if dep["url"]]
> + if shrinkwrap_urls:
> + ud.proxy = Fetch(shrinkwrap_urls, data)
> ud.needdonestamp = False
> Are this change OK or can it result in other issues?
> Also more generally why does the Fetch class default to the value of SRC_URI variable if the urls parameter contains an empty list? Isn't this a strange implementation? It also seems to result in issues if the shrinkwrap file contains no dependencies.
> Please note that I am fairly new to bitbake and completely new to the source code. :)
I think your patch is right. The Fetch class defaults to use SRC_URI
for legacy reasons based on how things were abstracted and extended, it
made sense at the time. I'm not sure if we still need it or not now.
If you send the above patch as a proper patch we can test it and likely
next prev parent reply other threads:[~2023-04-14 16:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-14 11:41 Problems having both git and npmsw sources in recipe #bitbake public
2023-04-14 16:08 ` Richard Purdie [this message]
2023-04-16 20:11 ` public
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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;
as well as URLs for NNTP newsgroup(s).