All of lore.kernel.org
 help / color / mirror / Atom feed
From: "kai" <kai.kang@windriver.com>
To: Scott Weaver <weaverjs@gmail.com>, bitbake-devel@lists.openembedded.org
Subject: Re: [bitbake-devel][ 1/3] bitbake: fetch2: fix premirror URI when downloadfilename defined
Date: Wed, 22 Sep 2021 09:58:13 +0800	[thread overview]
Message-ID: <dd26626a-079e-86d8-34ce-ad5d2b71ac8b@windriver.com> (raw)
In-Reply-To: <20210905222738.1050768-2-weaverjs@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]

On 9/6/21 6:27 AM, Scott Weaver wrote:
> When downloadfilename is defined in a recipe's SRC_URI and PREMIRRORS is also
> defined using the same URI, the downloadfilename is appended to the mirror
> URI and it should not be.
>
> [YOCTO #13039]

As I commented in the bugzilla, I suppose it is an invalid bug.

It save the tarball with the name of the value of downloadfilename 
rather than the basename of the url.
In this case, the name of tarball in the premirror downloads/ directory 
is uthash-2.0.2.tar.gz rather than
2.0.2.tar.gz if the premirror is created by run bitbake do_fetch. So 
when premirror is used, it checks
uthash-2.0.2.tar.gz in the premirrors but not the original value 
'2.0.2.tar.gz'.

With this patch, it fails to fetch the tarball from premirrors. It could 
be reproduced by config:

BB_NO_NETWORK = "1"
BB_FETCH_PREMIRRORONLY = "1"

Regards,
Kai
>
> Signed-off-by: Scott Weaver <weaverjs@gmail.com>
> ---
>   bitbake/lib/bb/fetch2/__init__.py | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bitbake/lib/bb/fetch2/__init__.py b/bitbake/lib/bb/fetch2/__init__.py
> index 914fa5c024..47a4943369 100644
> --- a/bitbake/lib/bb/fetch2/__init__.py
> +++ b/bitbake/lib/bb/fetch2/__init__.py
> @@ -466,7 +466,7 @@ def uri_replace(ud, uri_find, uri_replace, replacements, d, mirrortarball=None):
>                       # Kill parameters, they make no sense for mirror tarballs
>                       uri_decoded[5] = {}
>                   elif ud.localpath and ud.method.supports_checksum(ud):
> -                    basename = os.path.basename(ud.localpath)
> +                    basename = os.path.basename(uri_decoded[loc])
>                   if basename and not result_decoded[loc].endswith(basename):
>                       result_decoded[loc] = os.path.join(result_decoded[loc], basename)
>           else:
>
> 
>

-- 
Kai Kang
Wind River Linux


[-- Attachment #2: Type: text/html, Size: 2792 bytes --]

  reply	other threads:[~2021-09-22  1:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-05 22:27 [bitbake-devel][0/3] BZ#13039: updates to fetch2 and tests/fetch Scott Weaver
2021-09-05 22:27 ` [bitbake-devel][ 1/3] bitbake: fetch2: fix premirror URI when downloadfilename defined Scott Weaver
2021-09-22  1:58   ` kai [this message]
2021-09-28  2:00     ` Scott Weaver
2021-10-14  9:01       ` Robert Yang
2021-10-15  6:37   ` ChenQi
     [not found]   ` <16AE2029FEDEE475.7161@lists.openembedded.org>
2021-10-15  6:40     ` ChenQi
2021-09-05 22:27 ` [bitbake-devel][ 2/3] bitbake: tests/fetch: add downloadfilename tests Scott Weaver
2021-09-05 22:27 ` [bitbake-devel][ 3/3] bitbake: tests/fetch: add and fix npm tests Scott Weaver

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=dd26626a-079e-86d8-34ce-ad5d2b71ac8b@windriver.com \
    --to=kai.kang@windriver.com \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=weaverjs@gmail.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 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.