From: ChenQi <Qi.Chen@windriver.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-commits@lists.openembedded.org,
openembedded-core@lists.openembedded.org
Subject: Re: [oe-commits] Chen Qi : useradd.bbclass: add a new base class and code refactor
Date: Fri, 16 Aug 2013 09:38:31 +0800 [thread overview]
Message-ID: <520D8297.1040405@windriver.com> (raw)
In-Reply-To: <20130815174752.GE17945@jama>
On 08/16/2013 01:47 AM, Martin Jansa wrote:
> On Wed, Jul 24, 2013 at 10:26:48AM +0000, git@git.openembedded.org wrote:
>> Module: openembedded-core.git
>> Branch: master
>> Commit: 2a57bb7e9a7e154578aa7cb9aeebdf398a54ec00
>> URL: http://git.openembedded.org/?p=openembedded-core.git&a=commit;h=2a57bb7e9a7e154578aa7cb9aeebdf398a54ec00
>>
>> Author: Chen Qi <Qi.Chen@windriver.com>
>> Date: Fri Jul 19 09:52:25 2013 +0800
>>
>> useradd.bbclass: add a new base class and code refactor
>>
>> Add a new base class, useradd_base.bbclass, which is mainly a
>> collection of basic functions for user/group settings.
>>
>> The useradd_base.bbclass is intended to be inherited by useradd.bbclass
>> and the extrausers.bbclass to avoid code cuplication.
> This code is calling bbwarn in postinst scripts, but only implementation
> I've found is in logging.bbclass and isn't included in postinst shell
> code causing:
>
> /tmp/opkg-HtXU0e/dbus-1-Ea0TSc/preinst: 15:
> /tmp/opkg-HtXU0e/dbus-1-Ea0TSc/preinst: bbwarn: not found
Hi Martin,
I'm really sorry for this trouble. I didn't notice this when I first
made the patch.
I'll send out a patch to fix this.
Thanks for reporting this.
Best Regards,
Chen Qi
prev parent reply other threads:[~2013-08-16 1:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20130724102648.6C85050201@opal>
2013-08-15 17:47 ` [oe-commits] Chen Qi : useradd.bbclass: add a new base class and code refactor Martin Jansa
2013-08-16 1:38 ` ChenQi [this message]
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=520D8297.1040405@windriver.com \
--to=qi.chen@windriver.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-commits@lists.openembedded.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