From: Henning Schild <henning.schild@siemens.com>
To: Uladzimir Bely <ubely@ilbers.de>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v3] meta: drop debian stretch support
Date: Wed, 4 Jan 2023 09:17:57 +0100 [thread overview]
Message-ID: <20230104091757.2e53baa7@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <5438450.rdbgypaU67@home>
Am Wed, 04 Jan 2023 10:04:48 +0300
schrieb Uladzimir Bely <ubely@ilbers.de>:
> In the email from Tuesday, 3 January 2023 01:03:02 +03 user Henning
> Schild wrote:
> > On Mon, 2 Jan 2023 16:56:24 +0100
> >
> > Henning Schild <henning.schild@siemens.com> wrote:
> > > This one maybe should have waited a little longer for review, it
> > > fell right into the time between christmas and new year.
> > >
> > > A changelog to v1 would have been nice, or a reply to my review
> > > comments i gave.
> > >
> > > Am Tue, 27 Dec 2022 09:35:55 +0300
> > >
> > > schrieb Anton Mikanovich <amikan@ilbers.de>:
> > > > Debian Stretch state was moved to EOL since July 2020, so drop
> > > > it. This will allow us to get rid of many hacks inside Isar
> > > > core and single example packages.
> > > > Also drop raspbian-stretch distro and rpi machine used it.
> > > > Drop wic_fakeroot fsck hack because it is no more needed.
> > > >
> > > > Update documentation to remove Debian Stretch there also.
> > > >
> > > > Signed-off-by: Anton Mikanovich <amikan@ilbers.de>
> > > > ---
> > > >
> > > > README.md | 2 +-
> > > > doc/offline.md | 4 +-
> > > > doc/technical_overview.md | 6 +--
> > > > doc/user_manual.md | 48
> > > >
> > > > +++++++------------ meta-isar/conf/distro/raspbian-stretch.conf
> > > > | 17 ------- meta-isar/conf/distro/raspbian-stretch.list |
> > > > 2 -
> > > >
> > > > meta-isar/conf/local.conf.sample | 7 ---
> > > > meta-isar/conf/machine/rpi.conf | 8 ----
> > > > .../multiconfig/container-amd64-stretch.conf | 7 ---
> > > > .../conf/multiconfig/qemuamd64-stretch.conf | 5 --
> > > > .../conf/multiconfig/qemuarm-stretch.conf | 5 --
> > > > .../conf/multiconfig/qemuarm64-stretch.conf | 6 ---
> > > > .../conf/multiconfig/qemui386-stretch.conf | 5 --
> > > > .../conf/multiconfig/qemumipsel-stretch.conf | 5 --
> > > > meta-isar/conf/multiconfig/rpi-stretch.conf | 47
> > > >
> > > > ------------------ meta/classes/buildchroot.bbclass
> > > > | 3 +- meta/classes/dpkg-gbp.bbclass | 7 +--
> > > >
> > > > meta/classes/image.bbclass | 2 -
> > > > meta/classes/sbuild.bbclass | 3 +-
> > > > meta/conf/distro/debian-stretch.conf | 17 -------
> > > > meta/conf/distro/debian-stretch.list | 8 ----
> > > > .../files/isar-apt-fallback.conf | 4 --
> > > > .../isar-bootstrap/isar-bootstrap.inc | 18 +------
> > > > meta/recipes-kernel/linux/linux-custom.inc | 1 -
> > > > scripts/start_vm | 2 +-
> > > > scripts/wic_fakeroot | 8 ----
> > >
> > > I think this complete file can be removed. Not sure how i said it
> > > in my review to v1. Right now this wrapper does nothing but wrap.
> > > All the work it used to do has been deprecated and removed.
> > >
> > > I suggest to throw a patch on top to remove the file and set
> > >
> > > FAKEROOTCMD ?= "true;"
> > >
> > > like the removed comment suggested.
> >
> > I tried dropping the now seemingly useless wrapper but that somehow
> > did not work like it used to. So maybe we need to keep it after all.
> >
> > But it would be nice to know why we need to have it in place and
> > have that written down in a comment and a commit message.
> >
> > regards,
> > Henning
> >
>
> Hello.
>
> I've experimented with this FAKEROOTCMD a bit and it seems we really
> still need it.
>
> It really almost dummy except removing first argument from command
> line passed (`args.pop(0)`) and it seems to be the main thing we want
> from it (removing "pseudo" or "fakeroot"?).
>
> Simple replacing the script call with `true` command doesn't work as
> well as attempt to use this logic without `pop(0)`.
Not sure if we want to do anything about that. Maybe we can shorten
that script and add comments on why we still have it. Or we just leave
it.
Henning
prev parent reply other threads:[~2023-01-04 8:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 6:35 Anton Mikanovich
2022-12-30 19:20 ` Anton Mikanovich
2023-01-02 11:01 ` Jan Kiszka
2023-01-02 12:51 ` Moessbauer, Felix
2023-01-02 12:54 ` Moessbauer, Felix
2023-01-02 13:06 ` Jan Kiszka
2023-01-03 9:16 ` Baurzhan Ismagulov
2023-01-04 6:56 ` Uladzimir Bely
2023-01-02 15:56 ` Henning Schild
2023-01-02 22:03 ` Henning Schild
2023-01-04 7:04 ` Uladzimir Bely
2023-01-04 8:17 ` 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=20230104091757.2e53baa7@md1za8fc.ad001.siemens.net \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=ubely@ilbers.de \
/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