public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Subject: Re: [PATCH 0/3] fix and test wic exclude-path
Date: Fri, 12 Jun 2020 08:55:22 +0200	[thread overview]
Message-ID: <20200612065522.GP5077@yssyq.m.ilbers.de> (raw)
In-Reply-To: <20200610172627.09cfb239@md1za8fc.ad001.siemens.net>

Hello Henning,

On Wed, Jun 10, 2020 at 05:26:27PM +0200, Henning Schild wrote:
> Still having to work around that in a downstream layer. Any more
> comments or questions?

I'd like to look at the following issues:

1. I'd like to understand what exactly is failing when the fix is not applied.

2. The test case is failing with the fix applied.


Regarding (1), you responded:

> The "--exclude-path" is the real diff. It is a wic feature that never
> worked in isar because of bind-mounts that oe does not use. It is an
> important feature when splitting a rootfs into multiple partitions.
> Say you want a seperate home, you would add that and need to exclude
> home from root. Same goes for other directories people like to have in
> separate partitions, in fact boot is where i found it.

Thanks for the explanation. The concept is already clear from your patch
description. Do you have an example of a failing ln command and which
filesystems the source and the destination are on, for the test case you added?

Because I interpret --exclude-path usr as "don't copy usr", but
meta-isar/scripts/lib/wic/canned-wks/sdimage-efi.wks contains only / and /boot.
If it complained about / and /boot, then I'd expect it to fail also without
--exclude-path usr.


With kind regards,
Baurzhan.

  reply	other threads:[~2020-06-12  6:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-06 20:16 Henning Schild
2020-04-06 20:16 ` [PATCH 1/3] oe.path: Add copyhardlink() helper function Henning Schild
2020-04-06 20:16 ` [PATCH 2/3] lib/oe/path: try hardlinking instead of guessing when it might fail Henning Schild
2020-04-06 20:16 ` [PATCH 3/3] CI: test the exclude-path feature of wic Henning Schild
2020-05-07 19:25   ` Baurzhan Ismagulov
2020-05-07 20:13     ` Henning Schild
2020-09-01 19:54   ` [PATCH v2 " Baurzhan Ismagulov
2020-09-02  5:30     ` vijaikumar....@gmail.com
2020-09-02 10:10       ` Henning Schild
2020-04-06 20:18 ` [PATCH 0/3] fix and test wic exclude-path Henning Schild
2020-06-10 15:26 ` Henning Schild
2020-06-12  6:55   ` Baurzhan Ismagulov [this message]
2020-06-12 15:17     ` Jan Kiszka
2020-06-12 18:11       ` Henning Schild
2020-06-12 18:17         ` Henning Schild
2020-06-12 18:44           ` Jan Kiszka
2020-06-12 18:22       ` Henning Schild
2020-06-12 18:46         ` Jan Kiszka
2020-06-12 18:03     ` Henning Schild
2020-09-01 19:53       ` Baurzhan Ismagulov
2020-09-02  5:24         ` vijaikumar....@gmail.com
2020-09-02 10:04         ` Henning Schild
2020-09-14 13:36 ` Baurzhan Ismagulov

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=20200612065522.GP5077@yssyq.m.ilbers.de \
    --to=ibr@radix50.net \
    --cc=isar-users@googlegroups.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