From: ChenQi <Qi.Chen@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/1] rootfs_rpm.bbclass: fix the unexpected postinst error
Date: Tue, 29 Jan 2013 17:03:06 +0800 [thread overview]
Message-ID: <5107904A.3000802@windriver.com> (raw)
In-Reply-To: <5229d2b8caba239e8140288a51b2c9c2d6487567.1358840606.git.Qi.Chen@windriver.com>
Really really sorry that this patch introduces a bug :(
(It built and booted correctly, so I thought everything's OK. I didn't
check the do_rootfs log.)
A follow-up patch has been sent.
Sorry for the inconvenience.
Chen Qi
On 01/22/2013 04:44 PM, Qi.Chen@windriver.com wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> If the /etc/rpm-postinsts/ directory was empty, the following error
> would occur at system startup.
>
> ERROR: postinst /etc/rpm-postinsts/* failed
>
> This patch fixes this issue.
>
> [YOCTO #3767]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
> ---
> meta/classes/rootfs_rpm.bbclass | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/rootfs_rpm.bbclass b/meta/classes/rootfs_rpm.bbclass
> index 7d789cc..accd7d9 100644
> --- a/meta/classes/rootfs_rpm.bbclass
> +++ b/meta/classes/rootfs_rpm.bbclass
> @@ -108,7 +108,8 @@ fakeroot rootfs_rpm_do_rootfs () {
> i=\$i
> cat > ${IMAGE_ROOTFS}${sysconfdir}/rcS.d/S${POSTINSTALL_INITPOSITION}run-postinsts << EOF
> #!/bin/sh
> -for i in /etc/rpm-postinsts/*; do
> +for i in `ls /etc/rpm-postinsts/`; do
> + i=/etc/rpm-postinsts/$i
> echo "Running postinst $i..."
> if [ -f $i ] && $i; then
> rm $i
prev parent reply other threads:[~2013-01-29 9:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 8:44 [PATCH 0/1] rootfs_rpm.bbclass: fix the unexpected postinst error Qi.Chen
2013-01-22 8:44 ` [PATCH 1/1] " Qi.Chen
2013-01-29 9:03 ` 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=5107904A.3000802@windriver.com \
--to=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