All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Mark Asselstine <mark.asselstine@windriver.com>,
	meta-virtualization@yoctoproject.org,
	bruce.ashfield@windriver.com
Subject: Re: [m-c-s][PATCH] python-*: fixup postinst scripts
Date: Wed, 15 Nov 2017 20:58:36 +0000	[thread overview]
Message-ID: <1510779516.3952.165.camel@linuxfoundation.org> (raw)
In-Reply-To: <1510768793-27481-1-git-send-email-mark.asselstine@windriver.com>

On Wed, 2017-11-15 at 12:59 -0500, Mark Asselstine wrote:
> Checking for "$D" and doing an "exit 1" now results in errors such
> as:
> 
> [log_check] warning: %post(keystone-cronjobs-...) scriptlet failed,
> exit status 2
> 
> during image creation. Instead of escaping the script for "level-1"
> (image creation postinst) we wrap the "level-2" (first boot) postinst
> in an if statement. This also ensure the scriptlet in
> indentity.bbclass is less prone to behaving differently based on the
> postinsts defined in the classes which inherit 'identity'.

I think this could mean the postinst doesn't get executed at all if
there isn't an exit 1, else how would it know to defer to first boot?

Cheers,

Richard


  parent reply	other threads:[~2017-11-15 20:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 17:59 [m-c-s][PATCH] python-*: fixup postinst scripts Mark Asselstine
2017-11-15 20:54 ` Bruce Ashfield
2017-11-15 21:10   ` Mark Asselstine
2017-11-15 20:58 ` Richard Purdie [this message]
2017-11-15 21:08   ` Mark Asselstine
2017-11-15 21:09     ` Bruce Ashfield
2017-11-15 22:01       ` Mark Asselstine

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=1510779516.3952.165.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bruce.ashfield@windriver.com \
    --cc=mark.asselstine@windriver.com \
    --cc=meta-virtualization@yoctoproject.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.