Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] V2 Fix libpam's chmod
Date: Fri, 02 Mar 2012 13:26:38 +0000	[thread overview]
Message-ID: <1330694798.18076.3.camel@ted> (raw)
In-Reply-To: <81a428ea0e7515ab09e707fbdaba9b1a1b5050b6.1330684260.git.liezhi.yang@windriver.com>

On Fri, 2012-03-02 at 18:34 +0800, Robert Yang wrote:
> The libpam's has an error when generating the rootfs:
> 
> chmod: cannot access `/usr/sbin/unix_chkpwd': No such file or directory
> 
> This is because the following code in libpam_1.1.5.bb:
> 
> pkg_postinst_pam-plugin-unix () {
>     # below is necessary to allow unix_chkpwd get user info from shadow file
>     # on lsb images
>     chmod 4755 ${sbindir}/unix_chkpwd
> }
> 
> This is to set the setuid permission for unix_chkpwd (the lsb test
> requires this), but it lacks a "${D}", and we can do this in the install
> stage.
> 
> [YOCTO #2049]
> 
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>

Robert, in future patches could you use a subject line like:

[PATCH 1/1 v2] Fix libpam's chmod

instead of:

[PATCH 1/1] V2 Fix libpam's chmod

so that when the patches get applied, the V2 is stripped off?

The reason is that the value isn't particularly within the repository
once merged and doesn't look good when looking through commit history.

Thanks!

Richard




  parent reply	other threads:[~2012-03-02 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 10:34 [PATCH 0/1] V2 Fix libpam's chmod Robert Yang
2012-03-02 10:34 ` [PATCH 1/1] " Robert Yang
2012-03-02 12:25   ` Richard Purdie
2012-03-02 13:26   ` Richard Purdie [this message]
2012-03-02 13:31     ` Koen Kooi
2012-03-02 13:39       ` Richard Purdie
2012-03-02 14:05         ` Koen Kooi

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=1330694798.18076.3.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --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