public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Harald Seiler <hws@denx.de>
To: isar-users@googlegroups.com
Subject: [PATCH 0/2] Fix shell-scripts
Date: Tue,  5 Feb 2019 14:00:02 +0100	[thread overview]
Message-ID: <20190205130004.15200-1-hws@denx.de> (raw)

Fixes a few potential issues with the shell-scripts used in isar.  This is
for the most part expansions that would break for paths containing special
characters and portability concerns.  Additionally contains a fix for a
bug in common.sh where the group-name was not actually checked.


Harald Seiler (2):
  Fix all shell-script expansions
  buildchroot: Fix not checking group

 isar-init-build-env                                |  6 ++--
 meta-isar/conf/distro/raspbian-configscript.sh     |  2 +-
 .../isar-bootstrap/files/chroot-setup.sh           |  8 ++---
 meta/recipes-devtools/buildchroot/files/common.sh  |  9 ++++--
 meta/recipes-kernel/linux/files/build-kernel.sh    | 36 +++++++++++-----------
 .../enable-fsck/files/enable-fsck.sh               |  4 +--
 .../files/expand-last-partition.sh                 | 16 +++++-----
 scripts/ci_build.sh                                | 14 ++++-----
 scripts/mount_chroot.sh                            | 12 ++++----
 scripts/rpm2cpio.sh                                |  4 +--
 10 files changed, 58 insertions(+), 53 deletions(-)

-- 
2.14.1


             reply	other threads:[~2019-02-05 13:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 13:00 Harald Seiler [this message]
2019-02-05 13:00 ` [PATCH 1/2] Fix all shell-script expansions Harald Seiler
2019-02-06  7:49   ` Claudius Heine
2019-02-06  9:27     ` Harald Seiler
2019-02-06 10:08       ` Claudius Heine
2019-02-05 13:00 ` [PATCH 2/2] buildchroot: Fix not checking group Harald Seiler
2019-02-05 18:34   ` Henning Schild
2019-02-06 10:09 ` [PATCH 0/2] Fix shell-scripts Maxim Yu. Osipov

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=20190205130004.15200-1-hws@denx.de \
    --to=hws@denx.de \
    --cc=isar-users@googlegroups.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