public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: roberto.foglietta@linuxteam.org
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v2] dpkg: schroot migration then buildchroot references removed, v2
Date: Tue, 10 Jan 2023 05:24:21 +0100	[thread overview]
Message-ID: <CAJGKYO4iODzwkYrBDOEZwED3nbvcU5N9fxJt62CPa-=g_e2e9w@mail.gmail.com> (raw)
In-Reply-To: <20230110040427.1177958-1-roberto.foglietta@linuxteam.org>

On Tue, 10 Jan 2023 at 05:04, <roberto.foglietta@linuxteam.org> wrote:
>
> From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
>
> dpkg, adding feature: migration to schroot
>
> The patchset v.2 by Anton Mikanovich to migrate buildchroot to schroot is not
> complete because the buildchroot is still used by the dpkg base class which can
> be freed by buildchroot with this patch which applies on the top of these four:
>
>     * events: Cleanup lost schroot sessions if any, v2
>     * imager: Move image types to schroot, v2
>     * imager: Migrate from buildchroot to schroot, v2
>     * sbuild: Allow setting custom config paths, v2
>
> v2: remove the lines instead of commenting them, better description
>
> Signed-off-by: Roberto A. Foglietta <roberto.foglietta@gmail.com>
> ---
>  meta/classes/dpkg-base.bbclass | 6 ------
>  1 file changed, 6 deletions(-)


Hi all,

to complete the migration to schroot the patch above should be applied.

I also suggest to review the code in these two files and three functions:

meta/classes/image-tools-extension.bbclass

do_start_imager_session()
do_stop_imager_session()

b/meta/classes/isar-events.bbclass

stop_schroot_session()

In particular in this function stop_schroot_session() the code could
be factorized in common with do_stop_imager_session() using a function
like stop_schroot_session() to use everywhere is necessary.

About this, I am going to send the following patch

v7-0001-image-tools-ext.-start_imager_session-not-break-t.patch

Best regards, R-

  reply	other threads:[~2023-01-10  4:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-10  4:04 roberto.foglietta
2023-01-10  4:24 ` Roberto A. Foglietta [this message]
2023-01-10  6:59 ` Jan Kiszka
2023-01-10 11:09   ` Roberto A. 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='CAJGKYO4iODzwkYrBDOEZwED3nbvcU5N9fxJt62CPa-=g_e2e9w@mail.gmail.com' \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.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