From: Hongxu Jia <hongxu.jia@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: [PATCH V2 0/4] fix LSB Command Check failed
Date: Fri, 13 Sep 2013 16:14:40 +0800 [thread overview]
Message-ID: <cover.1379059861.git.hongxu.jia@windriver.com> (raw)
Change in V2: Rebase to current branch.
*Problem
LSB Command Check failed
...
su 1 failed
install_initd 1 failed
remove_initd 1 failed
...
The journal shows the command didsn't exist.
...
Looking for command su
Looking for command install_initd
Looking for command remove_initd
...
//Hongxu
The following changes since commit dd36930f3f37b2e0e1258de28ac1b1fa99cf196f:
bitbake: data_smart: Account for changes in append/prepend/remove in the config hash (2013-09-12 17:03:17 +0100)
are available in the git repository at:
git://git.pokylinux.org/poky-contrib hongxu/fix-lsb-cmdchek
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=hongxu/fix-lsb-cmdchek
Hongxu Jia (4):
LSB Command Check: fix install_initd and remove_initd not found
busybox: move su to /bin for lsb command check test
shadow: move su to /bin for lsb command check test
util-linux: move su to /bin for lsb command check test
.../busybox/busybox-1.21.1/su-usr-bin.patch | 26 ----------------------
meta/recipes-core/busybox/busybox_1.21.1.bb | 1 -
meta/recipes-core/util-linux/util-linux.inc | 4 ++--
meta/recipes-extended/lsb/lsb_4.1.bb | 4 ++--
meta/recipes-extended/shadow/shadow_4.1.4.3.bb | 3 ++-
5 files changed, 6 insertions(+), 32 deletions(-)
delete mode 100644 meta/recipes-core/busybox/busybox-1.21.1/su-usr-bin.patch
--
1.8.1.2
next reply other threads:[~2013-09-13 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 8:14 Hongxu Jia [this message]
2013-09-13 8:14 ` [PATCH 1/4] LSB Command Check: fix install_initd and remove_initd not found Hongxu Jia
2013-09-13 8:14 ` [PATCH 2/4] busybox: move su to /bin for lsb command check test Hongxu Jia
2013-09-13 8:14 ` [PATCH 3/4] shadow: " Hongxu Jia
2013-09-13 8:14 ` [PATCH 4/4] util-linux: " Hongxu Jia
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=cover.1379059861.git.hongxu.jia@windriver.com \
--to=hongxu.jia@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