From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Peter A. Bigot" <pab@pabigot.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: opkg/rpm inconsistencies in multilib image installations
Date: Sun, 16 Nov 2014 12:59:05 +0000 [thread overview]
Message-ID: <1416142745.28563.2.camel@linuxfoundation.org> (raw)
In-Reply-To: <5467EA52.6020008@pabigot.com>
On Sat, 2014-11-15 at 18:05 -0600, Peter A. Bigot wrote:
> On 11/15/2014 10:21 AM, Peter A. Bigot wrote:
> > tl;dr: multilib apparently defines its own root directory underneath
> > ${IMAGE_ROOT} which includes copies of /etc files like passwd that are
> > not known to pseudo. opkg and rpm differ in whether useradd scripts
> > are run when a multilib package is installed, resulting in failures to
> > add users/groups during multilib install when using opkg because a
> > sanity check thinks they already exist because pseudo is looking
> > somewhere else.
>
> Actually, I'm going to retract this whole thing, since I'm now unable to
> reproduce any of the problems described here. Possibly because of
> changes to the pseudo patches that fixed problems I thought were
> unrelated to this behavior.
>
> Sorry for the noise.
FWIW you are right in that the way multilib works with rpm is different
to ipk/deb, you can end up with two different rootfs directories which
are then reconciled. I do have some concerns about what would happen to
the passwd/group files in this scenario since they could easily become
out of sync. I suspect we'd have to create a pathological configuration
to manage that but its probably possible. I *think* the system would at
least error out if that pathological case occured.
That said, I suspect this problem exists before your patchset so isn't a
new issue.
Cheers,
Richard
next prev parent reply other threads:[~2014-11-16 12:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-15 16:21 opkg/rpm inconsistencies in multilib image installations Peter A. Bigot
2014-11-16 0:05 ` Peter A. Bigot
2014-11-16 12:59 ` Richard Purdie [this message]
2014-11-16 22:52 ` Mark Hatle
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=1416142745.28563.2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=pab@pabigot.com \
/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