public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: "'Jan Kiszka' via isar-users" <isar-users@googlegroups.com>
To: Quirin Gylstorff <Quirin.Gylstorff@siemens.com>,
	isar-users@googlegroups.com, felix.moessbauer@siemens.com,
	cedric.hombourger@siemens.com
Subject: Re: [RFC PATCH v2 1/5] enable-fsck: remove dependency to initramfs-tools
Date: Fri, 5 Sep 2025 16:52:56 +0200	[thread overview]
Message-ID: <f44074c1-e669-4707-aef0-3a8c74a43a7c@siemens.com> (raw)
In-Reply-To: <20250905142913.3336245-2-Quirin.Gylstorff@siemens.com>

On 05.09.25 16:28, Quirin Gylstorff wrote:
> From: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> 
> The packages doesn't use any artifacts provided by initramfs-tools.
> 
> Signed-off-by: Quirin Gylstorff <quirin.gylstorff@siemens.com>
> ---
>  .../enable-fsck/{enable-fsck_0.2.bb => enable-fsck_0.3.bb}      | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>  rename meta/recipes-support/enable-fsck/{enable-fsck_0.2.bb => enable-fsck_0.3.bb} (89%)
> 
> diff --git a/meta/recipes-support/enable-fsck/enable-fsck_0.2.bb b/meta/recipes-support/enable-fsck/enable-fsck_0.3.bb
> similarity index 89%
> rename from meta/recipes-support/enable-fsck/enable-fsck_0.2.bb
> rename to meta/recipes-support/enable-fsck/enable-fsck_0.3.bb
> index 2d0ec950..8a11990f 100644
> --- a/meta/recipes-support/enable-fsck/enable-fsck_0.2.bb
> +++ b/meta/recipes-support/enable-fsck/enable-fsck_0.3.bb
> @@ -9,7 +9,7 @@ inherit dpkg-raw
>  
>  DESCRIPTION = "This service enables fsck on first boot"
>  
> -DEBIAN_DEPENDS = "systemd, sed, mount, initramfs-tools"
> +DEBIAN_DEPENDS = "systemd, sed, mount"
>  
>  SRC_URI = " \
>      file://enable-fsck.service \

NACK. We need to fix this recipe first, and then you need to re-create
the initramfs, thus have a dependency on initramfs-tools | dracut.

Jan

-- 
Siemens AG, Foundational Technologies
Linux Expert Center

-- 
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/f44074c1-e669-4707-aef0-3a8c74a43a7c%40siemens.com.

  reply	other threads:[~2025-09-05 14:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 14:28 [RFC PATCH v2 0/5] Add support for dracut 'Quirin Gylstorff' via isar-users
2025-09-05 14:28 ` [RFC PATCH v2 1/5] enable-fsck: remove dependency to initramfs-tools 'Quirin Gylstorff' via isar-users
2025-09-05 14:52   ` 'Jan Kiszka' via isar-users [this message]
2025-09-05 14:28 ` [RFC PATCH v2 2/5] add dracut to custom kernel builds 'Quirin Gylstorff' via isar-users
2025-09-05 14:28 ` [RFC PATCH v2 3/5] rootfs: Allow to overwrite the initramfs generation cmds 'Quirin Gylstorff' via isar-users
2025-09-05 15:10   ` 'Jan Kiszka' via isar-users
2025-09-05 14:28 ` [RFC PATCH v2 4/5] rootfs Add dracut to initramfs generator 'Quirin Gylstorff' via isar-users
2025-09-05 14:28 ` [RFC PATCH v2 5/5] initramfs: allow to set the generator command 'Quirin Gylstorff' via isar-users

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=f44074c1-e669-4707-aef0-3a8c74a43a7c@siemens.com \
    --to=isar-users@googlegroups.com \
    --cc=Quirin.Gylstorff@siemens.com \
    --cc=cedric.hombourger@siemens.com \
    --cc=felix.moessbauer@siemens.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