From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chen Qi <Qi.Chen@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] shadow: upgrade from 4.1.4.3 to 4.2.1
Date: Thu, 03 Jul 2014 16:52:37 +0100 [thread overview]
Message-ID: <1404402757.6362.82.camel@ted> (raw)
In-Reply-To: <84fd3c3cb49d0ba85292dee3181b18a46c2081b1.1404110873.git.Qi.Chen@windriver.com>
On Mon, 2014-06-30 at 14:48 +0800, Chen Qi wrote:
> Upgrade shadow from 4.1.4.3 to 4.2.1.
>
> Changes during this upgrade are as following.
>
> 1. Remove the "merged" patches. These patches are either merged or
> the same functionality has been implemented upstream.
>
> add_root_cmd_groupmems.patch
> add_root_cmd_options.patch
> fix-etc-gshadow-reading.patch
> shadow-4.1.4.2-env-reset-keep-locale.patch
> shadow-4.1.4.2-groupmod-pam-check.patch
> shadow-4.1.4.2-su_no_sanitize_env.patch
> shadow.automake-1.11.patch
> shadow_fix_for_automake-1.12.patch
> useradd.patch
>
> 2. Remove the unneeded patch.
> The following patch has been removed because the logic in the related
> codes of the new version has been changed. In specific, the codes now
> can handle the 'NULL' return value. So there's no need for the following
> patch.
>
> slackware_fix_for_glib-2.17_crypt.patch
>
> 3. Teak the current patch to match the new version.
>
> allow-for-setting-password-in-clear-text.patch
>
> 4. Add a patch to fix compilation failure.
>
> usermod-fix-compilation-failure-with-subids-disabled.patch
>
> 5. Add a patch to fix the installation failure.
>
> fix-installation-failure-with-subids-disabled.patch
>
> 5. Add a patch to fix the failure at rootfs time if extrausers is inherited.
>
> commonio.c-fix-unexpected-open-failure-in-chroot-env.patch
>
> 6. Fix the bad section in the recipe.
>
> 7. Disable the new subids feature in the new version as it doesn't support
> cross compilation for now.
>
> 8. Modify the pkg_postinst to `exit 1' if the `pwconv' or `grpconv' fails.
> Also, fix the arguments to use '--root $D' instead of '--root=$D'.
I think this introduces the following issue:
https://autobuilder.yoctoproject.org/main/builders/nightly-qa-logrotate/builds/154/steps/BuildImages/logs/stdio
since the shutdown group is probably now installed in the core?
Cheers,
Richard
next prev parent reply other threads:[~2014-07-03 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 6:48 [PATCH 0/1] shadow: upgrade from 4.1.4.3 to 4.2.1 Chen Qi
2014-06-30 6:48 ` [PATCH 1/1] " Chen Qi
2014-07-03 15:52 ` Richard Purdie [this message]
2014-07-03 16:27 ` Richard Purdie
2014-07-03 16:36 ` Richard Purdie
2014-07-04 2:21 ` ChenQi
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=1404402757.6362.82.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Qi.Chen@windriver.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox