public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "Moessbauer, Felix" <felix.moessbauer@siemens.com>
To: "amikan@ilbers.de" <amikan@ilbers.de>,
	"Kiszka, Jan" <jan.kiszka@siemens.com>
Cc: "isar-users@googlegroups.com" <isar-users@googlegroups.com>
Subject: Re: [PATCH] initramfs: Add missing TASK_USE_SUDO
Date: Sat, 4 Feb 2023 12:11:36 +0000	[thread overview]
Message-ID: <25423ee6d92d4ad562508116ff51d61cde339efe.camel@siemens.com> (raw)
In-Reply-To: <ecd135a9-3bf2-d597-a49e-a9cc6ece45f5@siemens.com>

On Fri, 2023-02-03 at 19:18 +0100, Jan Kiszka wrote:
> On 03.02.23 18:51, Jan Kiszka wrote:
> > From: Jan Kiszka <jan.kiszka@siemens.com>
> > 
> > Forgotten in fea0f649fc3a.
> > 
> > Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
> > ---
> > 
> > Aren't we testing this class in Isar? Found it while porting isar-
> > cip-
> > core to bb2.
> 
> There is a target mc:qemuamd64-bullseye:isar-initramfs in citest.py -
> no
> idea why that did not trigger. In any case, please merge quickly to
> help
> downstream.

Acked. The same applies to other fixes to make ISAR work again on
sid or risv or in CI. Latest next is currently not usable.

Felix

> 
> Thanks,
> Jan
> 
> > 
> >  meta/classes/initramfs.bbclass | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/meta/classes/initramfs.bbclass
> > b/meta/classes/initramfs.bbclass
> > index db283347..a5141a53 100644
> > --- a/meta/classes/initramfs.bbclass
> > +++ b/meta/classes/initramfs.bbclass
> > @@ -28,6 +28,7 @@ ROOTFS_PACKAGES = "initramfs-tools
> > ${INITRAMFS_PREINSTALL} ${INITRAMFS_INSTALL}"
> >  inherit rootfs
> >  
> >  do_generate_initramfs[dirs] = "${DEPLOY_DIR_IMAGE}"
> > +do_generate_initramfs[network] = "${TASK_USE_SUDO}"
> >  do_generate_initramfs() {
> >      rootfs_do_mounts
> >      rootfs_do_qemu
> 
> -- 
> Siemens AG, Technology
> Competence Center Embedded Linux
> 


  reply	other threads:[~2023-02-04 12:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-03 17:51 Jan Kiszka
2023-02-03 18:18 ` Jan Kiszka
2023-02-04 12:11   ` Moessbauer, Felix [this message]
2023-02-07  5:41   ` Jan Kiszka
2023-02-07  8:56 ` Uladzimir Bely
2023-02-07 13:45   ` Jan Kiszka

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=25423ee6d92d4ad562508116ff51d61cde339efe.camel@siemens.com \
    --to=felix.moessbauer@siemens.com \
    --cc=amikan@ilbers.de \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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