From: Yi Liu <liuyi@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] rootfs-u-boot: add missing import get_bitbake_var
Date: Tue, 18 Jun 2024 23:55:17 -0700 (PDT) [thread overview]
Message-ID: <ab71bc45-1955-46eb-af2c-50182f2af0ecn@googlegroups.com> (raw)
In-Reply-To: <a45909a3-f748-4212-82e1-37bc43b70664@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1398 bytes --]
This issue was found by my VSCode, which hinted that some error there when
I went through this python file.
Best Regards,
Liu Yi
On Wednesday, June 19, 2024 at 12:27:11 PM UTC+8 Jan Kiszka wrote:
On 19.06.24 05:04, 'Liu Yi' via isar-users wrote:
> The variable image_rootfs_dir will not be correctly defined if missing
import of get_bitbake_var func.
>
> Signed-off-by: Liu Yi <li...@siemens.com>
> ---
> meta/scripts/lib/wic/plugins/source/rootfs-u-boot.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/scripts/lib/wic/plugins/source/rootfs-u-boot.py
b/meta/scripts/lib/wic/plugins/source/rootfs-u-boot.py
> index 7dde49d4..5611f93a 100644
> --- a/meta/scripts/lib/wic/plugins/source/rootfs-u-boot.py
> +++ b/meta/scripts/lib/wic/plugins/source/rootfs-u-boot.py
> @@ -20,7 +20,7 @@ import os
>
> from wic import WicError
> from wic.plugins.source.rootfs import RootfsPlugin
> -from wic.misc import exec_cmd
> +from wic.misc import get_bitbake_var, exec_cmd
>
> logger = logging.getLogger('wic')
>
Interesting. The code was like that since its beginning 6 years ago. How
did you trigger the issue? Maybe you can augment the commit message with
this information. Otherwise:
Reviewed-by: Jan Kiszka <jan.k...@siemens.com>
Thanks,
Jan
--
Siemens AG, Technology
Linux Expert Center
[-- Attachment #1.2: Type: text/html, Size: 1917 bytes --]
next prev parent reply other threads:[~2024-06-19 6:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 3:04 Liu Yi
2024-06-19 4:27 ` Jan Kiszka
2024-06-19 6:55 ` Yi Liu [this message]
2024-06-19 8:38 ` Jan Kiszka
2024-06-24 6:35 ` Uladzimir Bely
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=ab71bc45-1955-46eb-af2c-50182f2af0ecn@googlegroups.com \
--to=liuyi@siemens.com \
--cc=isar-users@googlegroups.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