From: Henning Schild <henning.schild@siemens.com>
To: Felix Moessbauer <felix.moessbauer@siemens.com>
Cc: isar-users@googlegroups.com, venkata.pyla@toshiba-tsip.com,
amikan@ilbers.de, jan.kiszka@siemens.com,
kazuhiro3.hayashi@toshiba.co.jp, dinesh.kumar@toshiba-tsip.com
Subject: Re: [PATCH] fix rebuild of rootfs_finalize task
Date: Fri, 6 Jan 2023 19:03:28 +0100 [thread overview]
Message-ID: <20230106190328.17ef9bc1@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230106100525.765479-1-felix.moessbauer@siemens.com>
ACK, forget why i wrote this is nicer.
Henning
Am Fri, 6 Jan 2023 10:05:25 +0000
schrieb Felix Moessbauer <felix.moessbauer@siemens.com>:
> The rootfs_finalize task currently cannot be re-executed, as it moves
> the sources-list into bootstrap.list. As this only has to be done
> once, it is not required on subsequent executions. To fix the rebuild
> issue, we simply ignore the return code of the mv statement.
>
> Signed-off-by: Felix Moessbauer <felix.moessbauer@siemens.com>
> ---
> meta/classes/image.bbclass | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index 629a0c1..6f0607e 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -425,7 +425,7 @@ do_rootfs_finalize() {
> rm -f "${ROOTFSDIR}/etc/apt/apt.conf.d/50isar"
>
> mv "${ROOTFSDIR}/etc/apt/sources-list" \
> - "${ROOTFSDIR}/etc/apt/sources.list.d/bootstrap.list"
> + "${ROOTFSDIR}/etc/apt/sources.list.d/bootstrap.list" ||
> true
> rm -f "${ROOTFSDIR}/etc/apt/sources-list"
> EOSUDO
prev parent reply other threads:[~2023-01-06 18:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 10:05 Felix Moessbauer
2023-01-06 17:56 ` Roberto A. Foglietta
2023-01-06 18:03 ` Henning Schild [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=20230106190328.17ef9bc1@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=venkata.pyla@toshiba-tsip.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