public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: roberto.foglietta@linuxteam.org
Cc: isar-users@googlegroups.com, roberto.foglietta@gmail.com
Subject: Re: [PATCH] image class bugfix: interuption does not break the rebuild
Date: Thu, 5 Jan 2023 21:14:16 +0100	[thread overview]
Message-ID: <20230105211416.3753a489@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <20230105192012.2761557-1-roberto.foglietta@linuxteam.org>

Was this sent twice or do you want to include a changelog to the v1?

This looks again like it is in merge conflict of ongoing work by me,
please note that somewhere to help maintainers resolve the conflict and
tell me if you want to take over here.

In which case you can, but give me a Reported-by if you want

Am Thu,  5 Jan 2023 20:20:12 +0100
schrieb roberto.foglietta@linuxteam.org:

> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
> 
> image class bugfix: interuption does not break the rebuild

Not sure i would understand that, but also not sure my commit message
was any better.

Henning

> 
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
>  meta/classes/image.bbclass | 9 +++++----
>  1 file changed, 5 insertions(+), 4 deletions(-)
> 
> diff --git a/meta/classes/image.bbclass b/meta/classes/image.bbclass
> index d72b8fa..b04826b 100644
> --- a/meta/classes/image.bbclass
> +++ b/meta/classes/image.bbclass
> @@ -428,10 +428,11 @@ do_rootfs_finalize() {
>          rm -f "${ROOTFSDIR}/etc/apt/sources.list.d/base-apt.list"
>          rm -f "${ROOTFSDIR}/etc/apt/apt.conf.d/50isar"
>  
> -        mv "${ROOTFSDIR}/etc/apt/sources-list" \
> -            "${ROOTFSDIR}/etc/apt/sources.list.d/bootstrap.list"
> -
> -        rm -f "${ROOTFSDIR}/etc/apt/sources-list"
> +        if [ -e "${ROOTFSDIR}/etc/apt/sources-list" ]; then
> +            mv  "${ROOTFSDIR}/etc/apt/sources-list" \
> +                "${ROOTFSDIR}/etc/apt/sources.list.d/bootstrap.list"
> || :
> +            rm  "${ROOTFSDIR}/etc/apt/sources-list" -f
> +        fi
>  
>  	BTROOTFS="${TMPDIR}/work/${DISTRO}-${DISTRO_ARCH}/buildchroot-target"
>  	for i in $(ls -1d ${BTROOTFS}/*/rootfs/ 2>/dev/null ||
> true); do


  reply	other threads:[~2023-01-05 20:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 19:20 roberto.foglietta
2023-01-05 20:14 ` Henning Schild [this message]
2023-01-05 21:06   ` Roberto A. Foglietta
  -- strict thread matches above, loose matches on Subject: below --
2023-01-05 19:06 roberto.foglietta

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=20230105211416.3753a489@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=roberto.foglietta@gmail.com \
    --cc=roberto.foglietta@linuxteam.org \
    /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