mail archive of the rauc mailing list
 help / color / mirror / Atom feed
From: "Enrico Jörns" <ejo@pengutronix.de>
To: "Stahl, Michael" <mstahl@moba.de>,
	"RAUC@pengutronix.de" <RAUC@pengutronix.de>
Subject: Re: [RAUC] remove trailing whitespaces at slot-type
Date: Tue, 16 Mar 2021 13:36:23 +0100	[thread overview]
Message-ID: <30733bddc7e689ac30c38c9431855a29ea5c418c.camel@pengutronix.de> (raw)
In-Reply-To: <AM9PR09MB47560E3559F2EA2C6A1C61B1DB6B9@AM9PR09MB4756.eurprd09.prod.outlook.com>

Hi Michael,

Am Dienstag, dem 16.03.2021 um 12:25 +0000 schrieb Stahl, Michael:
> I just searched some hours because rauc wount update my rootfs. The message
> was:
> Installation error: Unsupported image /run/rauc/bundle/MyRootfs.tar.gz
> 
> I found out that I had some trailing whitespaces in the system.conf at
> type=ext4 
> Because of that the g_pattern_match_simpel function in get_update_handler
> (update_handler.c) didn't match.
> 
> Maybe it is possible to remove trailing whitespaces before calling
> g_pattern_match_simple function in future.

thanks for reporting this. Yes, this actually sounds reasonable to me.

If you would like to make a patch for this, also please feel free to contribute.

My guess would be we should do this during config file parsing already
(config_file.c) as having leading/trailing whitespaces in values is probably
wrong for almost all options.

So far we do this only for the system variant during context setup.


Best regards

Enrico



-- 
Pengutronix e.K.                           | Enrico Jörns                |
Embedded Linux Consulting & Support        | https://www.pengutronix.de/ |
Steuerwalder Str. 21                       | Phone: +49-5121-206917-180  |
31137 Hildesheim, Germany                  | Fax:   +49-5121-206917-9    |


_______________________________________________
RAUC mailing list

      reply	other threads:[~2021-03-16 12:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-16 12:25 Stahl, Michael
2021-03-16 12:36 ` Enrico Jörns [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=30733bddc7e689ac30c38c9431855a29ea5c418c.camel@pengutronix.de \
    --to=ejo@pengutronix.de \
    --cc=RAUC@pengutronix.de \
    --cc=mstahl@moba.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