core-image-full-cmdline build failure

core-image-full-cmdline build failure

[Paul Barker]

[-- 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 --]

Re: core-image-full-cmdline build failure

[Robert Yang]

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,
>
>
>

Re: core-image-full-cmdline build failure

[Paul Barker]

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

On Aug 19, 2014 12:55 PM, "Robert Yang" <liezhi.yang@windriver.com> wrote:
>
> On 08/19/2014 07:42 PM, Paul Barker wrote:
>>
>> 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.
>

Ok, looking at the opkg code it should satisfy dependencies before running
the preinst script. I'll have to look into this further later and find out
exactly what is going wrong.

-- 
(Sent from mobile)

Paul Barker

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

[-- Attachment #2: Type: text/html, Size: 1451 bytes --]

Re: core-image-full-cmdline build failure

[Paul Barker]

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

On Tue, Aug 19, 2014 at 02:47:14PM +0100, Paul Barker wrote:
> On Aug 19, 2014 12:55 PM, "Robert Yang" <liezhi.yang@windriver.com> wrote:
> >
> > On 08/19/2014 07:42 PM, Paul Barker wrote:
> >>
> >> 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.
> >
> 
> Ok, looking at the opkg code it should satisfy dependencies before running
> the preinst script. I'll have to look into this further later and find out
> exactly what is going wrong.
> 

Yea, I broke opkg. Also getting confused, I thought I'd switched back from the
development snapshot of opkg to the released version but I hadn't.

*facepalm*

opkg-0.2.2 works, opkg-0.2.3-SNAPSHOT doesn't work as it fails to install things
in the correct order. I'll have to fix this before releasing opkg-0.2.3.

-- 
Paul Barker

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

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