All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter A. Bigot" <pab@pabigot.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/3] pseudo: default --without-passwd-fallback
Date: Sat, 15 Nov 2014 10:20:46 -0600	[thread overview]
Message-ID: <54677D5E.5000800@pabigot.com> (raw)
In-Reply-To: <CAJTo0LZMvL-7bTvf_ou6PHmMpZXa81GWb3murA6t5EfceQXOow@mail.gmail.com>

On 11/14/2014 10:16 AM, Burton, Ross wrote:
> Hi Peter,
>
> Something in this series isn't working nicely with multilib enabled.
>
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=ross/pseudo 
> is the branch I was testing it in, hopefully I pulled in all the right 
> pieces.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/102 
> is current master building for multilib and succeeding.
>
> https://autobuilder.yoctoproject.org/main/builders/nightly-multilib/builds/105 
> is ross/pseudo which fails at rootfs time.
>
> Will you be able to investigate this? (or tell me I merged the wrong 
> patches).

I've identified an anomaly in how opkg sets up installation for 
multilib, about which I've starting a new discussion: it's visible with 
the pseudo changes because of the way pseudo looks for existing 
users/groups.

While investigating, I did find a misunderstanding that requires a 
couple subtle changes to the patch set.  I've updated contrib 
pabigot/pseudo to incorporate the changes so far, but there's another 
issue I also want to investigate.

Until the opkg/rpm inconsistency is resolved, please hold off on this 
series.  There are a couple minor updates in contrib pabigot/pseudo that 
will become part of an eventual V2.

Peter



  parent reply	other threads:[~2014-11-15 16:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-01 17:04 [PATCH 0/3] prevent pseudo host passwd/group contamination Peter A. Bigot
2014-11-01 17:04 ` [PATCH 1/3] pseudo: default --without-passwd-fallback Peter A. Bigot
2014-11-14 16:16   ` Burton, Ross
2014-11-14 16:47     ` Peter A. Bigot
2014-11-14 17:08       ` Peter A. Bigot
2014-11-14 17:34       ` Burton, Ross
2014-11-15 16:20     ` Peter A. Bigot [this message]
2014-11-01 17:04 ` [PATCH 2/3] pseudo: provide fallback passwd and group files Peter A. Bigot
2014-11-12  7:36   ` zhangxiao
2014-11-12 11:15     ` Peter A. Bigot
2014-11-13  2:31       ` zhangxiao
2014-11-13  3:04         ` Peter A. Bigot
2014-11-13  3:28           ` zhangxiao
2014-11-01 17:04 ` [PATCH 3/3] bitbake.conf: pseudo fall back to last-resort passwd files Peter A. Bigot
2014-11-03 18:55 ` [PATCH 0/3] prevent pseudo host passwd/group contamination Peter Seebach
2014-11-03 23:16   ` Burton, Ross

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=54677D5E.5000800@pabigot.com \
    --to=pab@pabigot.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.