From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] apply-patches: catch unexpected failure
Date: Tue, 5 Jul 2016 17:43:28 +0200 [thread overview]
Message-ID: <20160705174328.0366d798@free-electrons.com> (raw)
In-Reply-To: <1467716529-30183-1-git-send-email-romain.naour@gmail.com>
Hello,
On Tue, 5 Jul 2016 13:02:09 +0200, Romain Naour wrote:
> As reported by S?bastien Szymanski [1], the apply-patches script
> doesn't stop if a tar command can't extract an archive.
>
> Use "set -e" to exit immediately if a command return an error.
>
> [1] http://patchwork.ozlabs.org/patch/626196
>
> Signed-off-by: Romain Naour <romain.naour@gmail.com>
> Cc: S?bastien Szymanski <sebastien.szymanski@armadeus.com>
> ---
> support/scripts/apply-patches.sh | 3 +++
> 1 file changed, 3 insertions(+)
In fact, this broke many packages, so I reverted.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-05 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 11:02 [Buildroot] [PATCH] apply-patches: catch unexpected failure Romain Naour
2016-07-05 15:37 ` Thomas Petazzoni
2016-07-05 15:43 ` Thomas Petazzoni [this message]
2016-07-05 15:46 ` Romain Naour
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=20160705174328.0366d798@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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