public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: Markus Volk <f_l_k@t-online.de>
To: Ross Burton <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [meta-oe][PATCH] wic/direct.py: ignore root mountpoint in fstab updater
Date: Wed, 27 Jul 2022 18:31:38 +0200	[thread overview]
Message-ID: <QWTOFR.3UW7PSRDH9903@t-online.de> (raw)
In-Reply-To: <A08B6BB6-EFD1-425D-AC02-457EF8A40229@arm.com>

[-- Attachment #1: Type: text/plain, Size: 2058 bytes --]

Yes. With the patch the warning disappears from dmesg

Am Mi, 27. Jul 2022 um 15:44:48 +0000 schrieb Ross Burton 
<ross.burton@arm.com>:
> This looks like a fix for 
> <https://bugzilla.yoctoproject.org/show_bug.cgi?id=14865>, can you 
> confirm that?
> 
> Ross
> 
>>  On 27 Jul 2022, at 14:45, Markus Volk via lists.openembedded.org 
>> <f_l_k=t-online.de@lists.openembedded.org 
>> <mailto:f_l_k=t-online.de@lists.openembedded.org>> wrote:
>> 
>>  We already have a root entry in fstab. This commit prevents 
>> processing root
>>  mountpoint in fstab_updater and thus avoids duplicate entries for 
>> root in fstab.
>> 
>>  Signed-off-by: Markus Volk <f_l_k@t-online.de 
>> <mailto:f_l_k@t-online.de>>
>>  ---
>>  scripts/lib/wic/plugins/imager/direct.py | 3 ++-
>>  1 file changed, 2 insertions(+), 1 deletion(-)
>> 
>>  diff --git a/scripts/lib/wic/plugins/imager/direct.py 
>> b/scripts/lib/wic/plugins/imager/direct.py
>>  index c44159b235..75004ab320 100644
>>  --- a/scripts/lib/wic/plugins/imager/direct.py
>>  +++ b/scripts/lib/wic/plugins/imager/direct.py
>>  @@ -117,7 +117,8 @@ class DirectPlugin(ImagerPlugin):
>>          updated = False
>>          for part in self.parts:
>>              if not part.realnum or not part.mountpoint \
>>  -               or not part.mountpoint.startswith('/'):
>>  +               or not part.mountpoint.startswith('/') \
>>  +               or part.mountpoint == "/":
>>                  continue
>> 
>>              if part.use_uuid:
>>  --
>>  2.34.1
>> 
>> 
>> 
>> 
> 
> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#168572): 
> <https://lists.openembedded.org/g/openembedded-core/message/168572>
> Mute This Topic: <https://lists.openembedded.org/mt/92649199/3618223>
> Group Owner: openembedded-core+owner@lists.openembedded.org 
> <mailto:openembedded-core+owner@lists.openembedded.org>
> Unsubscribe: 
> <https://lists.openembedded.org/g/openembedded-core/unsub> 
> [f_l_k@t-online.de <mailto:f_l_k@t-online.de>]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


[-- Attachment #2: Type: text/html, Size: 2532 bytes --]

  reply	other threads:[~2022-07-27 16:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 13:45 [meta-oe][PATCH] wic/direct.py: ignore root mountpoint in fstab updater Markus Volk
2022-07-27 15:44 ` [OE-core] " Ross Burton
2022-07-27 16:31   ` Markus Volk [this message]
     [not found]   ` <1705BCB17DD12169.1380@lists.openembedded.org>
2022-07-27 17:04     ` Markus Volk
2022-07-28 16:15       ` Ross Burton
2022-08-02 14:05         ` Markus Volk

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=QWTOFR.3UW7PSRDH9903@t-online.de \
    --to=f_l_k@t-online.de \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@arm.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