Re: core-image-full-cmdline build failure

[Robert Yang <liezhi.yang@windriver.com>]

On 08/19/2014 07:42 PM, Paul Barker wrote:
> 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

For rpm, I think yes ? The "pre" depends on base-passwd:
$ rpm -qpR -v tmp/deploy/rpm/core2_64/rpcbind-0.2.1-r0.core2_64.rpm | grep base-pass
manual: base-passwd
pre: base-passwd
post: base-passwd
preun: base-passwd
postun: base-passwd

But I can't find such info in ipk.

// Robert

> within opkg. If not, I think the above solution of listing certain packages for
> early installation would be best.
>
> Thanks,
>
>
>