From: "vijaikumar....@gmail.com" <vijaikumar.kanagarajan@gmail.com>
To: isar-users <isar-users@googlegroups.com>
Subject: Re: [PATCH] wic: Remove racy python3 link cleanup
Date: Wed, 25 Nov 2020 01:27:28 -0800 (PST) [thread overview]
Message-ID: <bb2d6a35-bcd9-4296-ae06-c5258f2317dcn@googlegroups.com> (raw)
In-Reply-To: <978016c0-7cc4-f45d-4408-86b7b124af9b@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 1747 bytes --]
On Sunday, November 22, 2020 at 8:18:00 PM UTC+5:30 Jan Kiszka wrote:
> From: Jan Kiszka <jan.k...@siemens.com>
>
> When two wic tasks run in parallel, one can pull the carpet under the
> other by removing python3-native. We could lock everything but it's
> simpler to just keep the links around. They won't do any harm as they
> are only part of the buildchroot.
>
> Signed-off-by: Jan Kiszka <jan.k...@siemens.com>
> ---
> meta/classes/wic-img.bbclass | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/meta/classes/wic-img.bbclass b/meta/classes/wic-img.bbclass
> index 2275ebec..bbf5dd8a 100644
> --- a/meta/classes/wic-img.bbclass
> +++ b/meta/classes/wic-img.bbclass
> @@ -164,17 +164,16 @@ EOSUDO
> # The python path is hard-coded as /usr/bin/python3-native/python3 in wic.
> Handle that.
> mkdir -p /usr/bin/python3-native/
> if [ $(head -1 $(which bmaptool) | grep python3) ];then
> - ln -s /usr/bin/python3 /usr/bin/python3-native/python3
> + ln -fs /usr/bin/python3 /usr/bin/python3-native/python3
> else
> - ln -s /usr/bin/python2 /usr/bin/python3-native/python3
> + ln -fs /usr/bin/python2 /usr/bin/python3-native/python3
> fi
> export PATH="$BITBAKEDIR/bin:$PATH"
> "$SCRIPTSDIR"/wic create "$WKS_FULL_PATH" \
> --vars "$STAGING_DIR/$MACHINE/imgdata/" \
> -o "/$WICTMP/${IMAGE_FULLNAME}.wic/" \
> --bmap \
> - -e "$IMAGE_BASENAME" $@
> - rm -rf /usr/bin/python3-native' \
> + -e "$IMAGE_BASENAME" $@' \
> my_script "${BITBAKEDIR}" "${SCRIPTSDIR}" "${WKS_FULL_PATH}"
> "${STAGING_DIR}" \
> "${MACHINE}" "${WICTMP}" "${IMAGE_FULLNAME}" "${IMAGE_BASENAME}" \
> ${WIC_CREATE_EXTRA_ARGS}
> --
> 2.26.2
>
Reviewed-by: Vijai Kumar K <Vijaikumar_Kanagarajan@mentor.com>
[-- Attachment #1.2: Type: text/html, Size: 2388 bytes --]
next prev parent reply other threads:[~2020-11-25 9:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-22 14:47 Jan Kiszka
2020-11-25 9:27 ` vijaikumar....@gmail.com [this message]
2020-11-25 18:59 ` Baurzhan Ismagulov
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=bb2d6a35-bcd9-4296-ae06-c5258f2317dcn@googlegroups.com \
--to=vijaikumar.kanagarajan@gmail.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