From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH v2] use ^_ as separator in perms files
Date: Mon, 15 Aug 2016 16:54:47 +0200 [thread overview]
Message-ID: <20160815145447.4sivm2vzr5k53ll6@pengutronix.de> (raw)
In-Reply-To: <20160815141058.GA21035@localhost.localdomain>
On Mon, Aug 15, 2016 at 04:10:58PM +0200, Ladislav Michl wrote:
> On Thu, Aug 04, 2016 at 08:51:39AM +0200, Michael Olbrich wrote:
> > I'm already testing it. Looks good so far. I just need to setup a test-case
> > to trigger the error path before I push it.
>
> Just tested, error path triggered, but 'ptxdist clean root' didn't help.
> I had to delete *.perms files manually. Is it worth better fix or is it
> enough just change error message?
Can you try to reproduce this? Clean root should trigger targetinstall for
all packages and new permission files should be created. For which image
did it fail?
Michael
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2016-08-15 14:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 11:22 [ptxdist] [PATCH] " Ladislav Michl
2016-07-27 10:59 ` Michael Olbrich
2016-07-28 23:12 ` Ladislav Michl
2016-07-29 7:39 ` Michael Olbrich
2016-07-31 21:10 ` [ptxdist] [PATCH v2] " Ladislav Michl
2016-08-03 10:23 ` Ladislav Michl
2016-08-04 6:51 ` Michael Olbrich
2016-08-15 14:10 ` Ladislav Michl
2016-08-15 14:54 ` Michael Olbrich [this message]
2016-08-15 16:21 ` Ladislav Michl
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=20160815145447.4sivm2vzr5k53ll6@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.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