From: Henning Schild <henning.schild@siemens.com>
To: isar-users <isar-users@googlegroups.com>
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: [PATCH 0/3] "root" to "builder" repair series
Date: Mon, 12 Nov 2018 16:51:46 +0100 [thread overview]
Message-ID: <20181112155149.24215-1-henning.schild@siemens.com> (raw)
These three patches should be applied in the given order. The one from
Jan has been taken off the Mailinglist and has started the discussion
about reverting the other one and not doing chowning anymore.
Henning Schild (2):
Revert "Change ownership of WORKDIR prior to unpacking"
buildchroot: do not chown to builder:builder anymore
Jan Kiszka (1):
buildchroot: Align UID and GID of builder user with caller
meta/classes/base.bbclass | 5 -----
meta/recipes-devtools/buildchroot/buildchroot.inc | 4 +++-
meta/recipes-devtools/buildchroot/files/build.sh | 2 --
meta/recipes-devtools/buildchroot/files/configscript.sh | 4 ++--
4 files changed, 5 insertions(+), 10 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-12 15:51 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-12 15:51 Henning Schild [this message]
2018-11-12 15:51 ` [PATCH 1/3] buildchroot: Align UID and GID of builder user with caller Henning Schild
2018-11-13 7:53 ` Jan Kiszka
2018-11-14 7:32 ` Henning Schild
2018-11-14 8:31 ` [PATCH v2 " Jan Kiszka
2018-11-12 15:51 ` [PATCH 2/3] Revert "Change ownership of WORKDIR prior to unpacking" Henning Schild
2018-11-14 13:10 ` Jan Kiszka
2018-11-14 13:23 ` Jan Kiszka
2018-11-14 13:58 ` Jan Kiszka
2018-11-14 14:11 ` Henning Schild
2018-11-14 15:43 ` Henning Schild
2018-11-14 15:45 ` Jan Kiszka
2018-11-15 8:28 ` Henning Schild
2018-11-12 15:51 ` [PATCH 3/3] buildchroot: do not chown to builder:builder anymore Henning Schild
2018-11-14 12:55 ` [PATCH 0/3] "root" to "builder" repair series 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=20181112155149.24215-1-henning.schild@siemens.com \
--to=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.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