public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Anton Mikanovich <amikan@ilbers.de>
To: "Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
	"isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH v3 5/6] CI: Fix used chroot recipe name
Date: Tue, 14 Feb 2023 12:30:23 +0200	[thread overview]
Message-ID: <0a0c7c4f-1906-e3fb-aed8-85a82daabf05@ilbers.de> (raw)
In-Reply-To: <AS4PR10MB5318337A39B3CF364974CCFEEDA29@AS4PR10MB5318.EURPRD10.PROD.OUTLOOK.COM>

14/02/2023 11:28, Schmidt, Adriaan wrote:
> Hi Anton,
>
> In addition to the renaming of buildchroot-target => sbuild-chroot-target,
> also the task needs to renamed in this check (do_buildchroot_deploy => do_sbuildchroot_deploy).
>
> Thanks,
> Adriaan

That's right, thanks.
Will fix it in v4.


  reply	other threads:[~2023-02-14 10:30 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13  7:40 [PATCH v3 0/6] Imager schroot migration Anton Mikanovich
2023-02-13  7:40 ` [PATCH v3 1/6] isar-apt: Move cleanup to postprocessing Anton Mikanovich
2023-02-13  7:40 ` [PATCH v3 2/6] imager: Migrate from buildchroot to schroot Anton Mikanovich
2023-02-13  7:40 ` [PATCH v3 3/6] imager: Move image types " Anton Mikanovich
2023-02-13  7:40 ` [PATCH v3 4/6] imager: Split imager deps between image types Anton Mikanovich
2023-02-13  7:40 ` [PATCH v3 5/6] CI: Fix used chroot recipe name Anton Mikanovich
2023-02-14  9:28   ` Schmidt, Adriaan
2023-02-14 10:30     ` Anton Mikanovich [this message]
2023-02-13  7:40 ` [PATCH v3 6/6] meta: Remove buildchroot Anton Mikanovich

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=0a0c7c4f-1906-e3fb-aed8-85a82daabf05@ilbers.de \
    --to=amikan@ilbers.de \
    --cc=adriaan.schmidt@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