From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: add shadow 4.2.1
Date: Sat, 18 Jul 2015 22:11:49 +0200 [thread overview]
Message-ID: <20150718221149.7d6a85bb@free-electrons.com> (raw)
In-Reply-To: <1426736888-29437-3-git-send-email-steven@uplinklabs.net>
Hello Steven,
On Wed, 18 Mar 2015 20:48:05 -0700, Steven Noonan wrote:
> Signed-off-by: Steven Noonan <steven@uplinklabs.net>
> ---
> package/Config.in | 1 +
> package/shadow/Config.in | 10 +
> package/shadow/chgpasswd.pam | 4 +
> package/shadow/chpasswd.pam | 6 +
> package/shadow/newusers.pam | 6 +
> package/shadow/passwd.pam | 4 +
> package/shadow/remove-util-linux-conflicts.patch | 642 ++++++++++++++++++++++
> package/shadow/shadow-4.2.1-subordinate-ids.patch | 34 ++
> package/shadow/shadow-strncpy-usage.patch | 25 +
> package/shadow/shadow.hash | 1 +
> package/shadow/shadow.mk | 43 ++
> package/shadow/xstrdup.patch | 9 +
> 12 files changed, 785 insertions(+)
> create mode 100644 package/shadow/Config.in
> create mode 100644 package/shadow/chgpasswd.pam
> create mode 100644 package/shadow/chpasswd.pam
> create mode 100644 package/shadow/newusers.pam
> create mode 100644 package/shadow/passwd.pam
> create mode 100644 package/shadow/remove-util-linux-conflicts.patch
> create mode 100644 package/shadow/shadow-4.2.1-subordinate-ids.patch
> create mode 100644 package/shadow/shadow-strncpy-usage.patch
> create mode 100644 package/shadow/shadow.hash
> create mode 100644 package/shadow/shadow.mk
> create mode 100644 package/shadow/xstrdup.patch
Shortly after you submitted this patch, Ryan Barnett (in Cc) made a
number of comments / asked some questions, but you never answered or
posted a new version.
Ryan also mentioned that another proposal had been made for the shadow
package, as part of the SELinux support. While the SELinux series is
still on-going (some of it has been merged, some remains to be merged),
the shadow package is no longer part of it.
Therefore, Steven and Ryan, if you still care about shadow, please
resubmit a new version that addresses the different problems/questions.
In the mean time, I'll mark the patch as Changes Requested in patchwork.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-07-18 20:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-19 3:48 [Buildroot] [PATCH] package: add hwloc 1.10.1 Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add powertop 2.7 Steven Noonan
2015-03-19 5:31 ` Baruch Siach
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add shadow 4.2.1 Steven Noonan
2015-03-19 13:07 ` Ryan Barnett
2015-07-18 20:11 ` Thomas Petazzoni [this message]
2015-03-19 3:48 ` [Buildroot] [PATCH] package/numactl: upgrade to 2.0.10 Steven Noonan
2015-03-19 5:26 ` Baruch Siach
2015-03-19 5:30 ` Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add pacman 4.2.1 Steven Noonan
2015-03-20 6:15 ` Baruch Siach
2015-03-20 19:52 ` Thomas Petazzoni
2015-03-20 20:18 ` Steven Noonan
2015-03-20 20:34 ` Thomas Petazzoni
2015-03-20 21:19 ` Steven Noonan
2015-03-19 3:48 ` [Buildroot] [PATCH] package: add mosh 1.2.4 Steven Noonan
2015-03-20 6:12 ` Baruch Siach
2015-03-19 5:21 ` [Buildroot] [PATCH] package: add hwloc 1.10.1 Baruch Siach
2015-03-19 5:24 ` Steven Noonan
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=20150718221149.7d6a85bb@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