Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Barker <paul@paulbarker.me.uk>
To: OE Core <openembedded-core@lists.openembedded.org>
Subject: core-image-full-cmdline build failure
Date: Tue, 19 Aug 2014 11:42:29 +0000	[thread overview]
Message-ID: <20140819114229.GE7174@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1294 bytes --]

Hi all,

I'm getting consistent failures trying to build core-image-full-cmdline with an
up-to-date oe-core (d0be4b3) and bitbake (38d4f65). The useradd commands for
rpcbind and openssh-sshd are running before the base-passwd package has been
installed and so are not finding /etc/passwd.

I've hacked together a local fix for this by modifying the do_rootfs command to
install base-passwd before installing other packages. If this is a common
failure and it's not just me seeing it, would it be worth expanding the package
types listed in the install manifest? Currently we have 'mip' for must install
package, 'aop' for attempt only, etc. If we need to ensure certain packages are
installed first, perhaps we could add something like 'ep' for early package.

Looking into the rpcbind package, the useradd commands are performed in a
preinst script so I don't think the problem is opkg running the script too
early. Do other package managers guarantee that a package's dependencies are
installed before the preinst script is ran? If so, I may need to re-order things
within opkg. If not, I think the above solution of listing certain packages for
early installation would be best.

Thanks,

-- 
Paul Barker

Email: paul@paulbarker.me.uk
http://www.paulbarker.me.uk

[-- Attachment #2: Type: application/pgp-signature, Size: 484 bytes --]

             reply	other threads:[~2014-08-19 11:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 11:42 Paul Barker [this message]
2014-08-19 11:55 ` core-image-full-cmdline build failure Robert Yang
2014-08-19 13:47   ` Paul Barker
2014-08-19 15:02     ` Paul Barker

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=20140819114229.GE7174@gmail.com \
    --to=paul@paulbarker.me.uk \
    --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