public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: roberto.foglietta@linuxteam.org, isar-users@googlegroups.com
Subject: Re: [PATCH v2] dpkg: schroot migration then buildchroot references removed, v2
Date: Tue, 10 Jan 2023 12:09:04 +0100	[thread overview]
Message-ID: <CAJGKYO4cNcXo6q8MWH7yDh9mici--+hb5j4W1GLnsZeq4cZEXg@mail.gmail.com> (raw)
In-Reply-To: <e634c215-caf4-9465-4b5a-34e6f02b5ce0@siemens.com>

On Tue, 10 Jan 2023 at 07:59, Jan Kiszka <jan.kiszka@siemens.com> wrote:
>
> On 10.01.23 05:04, roberto.foglietta@linuxteam.org wrote:
> > From: "Roberto A. Foglietta" <roberto.foglietta@gmail.com>
> >
> > dpkg, adding feature: migration to schroot
> >

>
> I've only dropped this bit in
> https://patchwork.isar-build.org/project/isar/patch/4a89ddd8-5be1-9aff-ab5c-579ecda50b8f@siemens.com/,
> wasn't sure about the rest. How did you validate your cleanup?
>
> >  # Add dependency from the correct schroot: host or target
> >  do_apt_fetch[depends] += "${SCHROOT_DEP}"
> >> > 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>
> > ---
>
> Patch version changes and dependencies generally go here, not above.
>
> >  meta/classes/dpkg-base.bbclass | 6 ------
> >  1 file changed, 6 deletions(-)
> >
> > diff --git a/meta/classes/dpkg-base.bbclass b/meta/classes/dpkg-base.bbclass
> > index 260aa73..ce150b3 100644
> > --- a/meta/classes/dpkg-base.bbclass
> > +++ b/meta/classes/dpkg-base.bbclass
> > @@ -5,7 +5,6 @@
> >  # SPDX-License-Identifier: MIT
> >
> >  inherit sbuild
> > -inherit buildchroot
> >  inherit debianize
> >  inherit terminal
> >  inherit repository
> > @@ -123,9 +122,6 @@ do_apt_fetch() {
> >  addtask apt_fetch
> >  do_apt_fetch[lockfiles] += "${REPO_ISAR_DIR}/isar.lock"
> >
> > -# Add dependency from the correct buildchroot: host or target
> > -do_apt_fetch[depends] += "${BUILDCHROOT_DEP}"
> > -
> > @@ -193,8 +189,6 @@ BUILDROOT = "${BUILDCHROOT_DIR}/${PP}"
> >  dpkg_do_mounts() {
> >      mkdir -p ${BUILDROOT}
> >      sudo mount --bind ${WORKDIR} ${BUILDROOT}
> > -
> > -    buildchroot_do_mounts
> >  }
> >
> >  dpkg_undo_mounts() {
>
> Isn't there is more to clean up then? Are we still using BUILDROOT in
> the end? In fact: Are we still calling dpkg_do_mounts at all??

your own patch tell me that your questions found an answer:

       dpkg-base: Drop dependency on buildchroot v2

> I don't
> find references in the tree, today.

Which tree? Of which repository?

Best regards, R-

      reply	other threads:[~2023-01-10 11:09 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
2023-01-10  6:59 ` Jan Kiszka
2023-01-10 11:09   ` Roberto A. Foglietta [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=CAJGKYO4cNcXo6q8MWH7yDh9mici--+hb5j4W1GLnsZeq4cZEXg@mail.gmail.com \
    --to=roberto.foglietta@gmail.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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