From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup
Date: Tue, 08 Nov 2011 08:24:03 -0800 [thread overview]
Message-ID: <4EB957A3.50203@intel.com> (raw)
In-Reply-To: <1320761372.10843.36.camel@ted>
On 11/08/2011 06:09 AM, Richard Purdie wrote:
> On Mon, 2011-11-07 at 15:36 -0800, Scott Garman wrote:
>> Fix bug where only packages named PN included base-passwd in
>> RDEPENDS.
>>
>> This fixes [YOCTO #1727]
>>
>> Signed-off-by: Scott Garman<scott.a.garman@intel.com>
>> ---
>> meta/classes/useradd.bbclass | 6 +++++-
>> 1 files changed, 5 insertions(+), 1 deletions(-)
>
> Merged to master, thanks.
>
> As an aside, does the USERADDPN variable serve any purpose now or can we
> remove it?
Indeed it does. I'll prepare a patch for that and also to remove the
temporary workaround USERADDPN entry Koen added to the avahi recipe once
you've accepted Eric's other patch.
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2011-11-08 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 23:36 [PATCH 0/1] useradd.bbclass: fix how RDEPENDS is setup [v3] Scott Garman
2011-11-07 23:36 ` [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup Scott Garman
2011-11-08 14:09 ` Richard Purdie
2011-11-08 16:24 ` Scott Garman [this message]
2011-11-08 16:58 ` Richard Purdie
-- strict thread matches above, loose matches on Subject: below --
2011-11-06 23:27 [PATCH 0/1] useradd.bbclass: fix how RDEPENDS is setup [v2] Scott Garman
2011-11-06 23:27 ` [PATCH 1/1] useradd.bbclass: fix how RDEPENDS is setup Scott Garman
2011-11-06 19:31 [PATCH 0/1] " Scott Garman
2011-11-06 19:31 ` [PATCH 1/1] " Scott Garman
2011-11-06 20:25 ` Phil Blundell
2011-11-06 23:07 ` Scott Garman
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=4EB957A3.50203@intel.com \
--to=scott.a.garman@intel.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