public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ned Ludd <solar@gentoo.org>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] Re: emerge --root : users not created
Date: Thu, 17 Jun 2010 12:39:16 -0700	[thread overview]
Message-ID: <1276803556.19773.1.camel@hangover> (raw)
In-Reply-To: <4C1A5413.8080606@verizon.net>

On Thu, 2010-06-17 at 12:57 -0400, P. Levine wrote:
> On 06/14/2010 04:09 AM, Sven Rebhan wrote:
> > 2010/6/11 Marcus Priesch <marcus@priesch.priv.at>:
> >> Hi sven,
> >>
> >> wouldnt it be enough to have the patch included in gentoo's shadow
> >> ebuild - as i think its mainly relevant for gentoo folks - at least in
> >> the meantime, until the patch gets accepted upstream ?!
> > 
> > Well, talk to the Gentoo maintainer of the shadow suite. :-) IIRC, it was
> > clearly said, that the patch has to go through mainstream, but you can
> > try nevertheless. IMHO the patch really _should_ go upstream and be
> > reviewed there as it might be relevant for security stuff.
> > 
> >> as i assume this patch alone is not enough - as it needs tweaking the
> >> eclass providing the eadduser & co functions also ... and therefore it's
> >> hard to put in an overlay ... or ?!?!
> > 
> > The procedure would be:
> > 1. Get the patch accepted either upstream or in the portage tree.
> > 2. Find a good check to distinguish --chroot enabled and disabled shadow
> > 3. Modify the eclass accordingly.
> > 
> > So, start with 1. and the rest will happen automatically... ;-)
> > 
> > Sven
> > 
> > 
> 
> I'm currently trying to upgrade the patch to the latest shadow svn head.
> 
> I'm having a problem that I might have to post on gentoo bugs, but I'd
> like to post it here to make sure I'm not overlooking anything.  I
> started a new cross-build of armv4l-softfloat-linux-gnueabi with
> crossdev.  After installing the toolchain, using emerge-wrapper --init,
> modifying make.conf, etc..., all emerges with
> ROOT=/usr/armv4l-softfloat-linux-gnueabi/ in the environment cause
> portage to use the --quiet flag.  I don't have the flag in
> PORTAGE_RSYNC_EXTRA_OPTS.  I've tried deleting /var/cache/edb and
> ${ROOT}var/cache/edb, to no avail.  I can't use FEATURES="python-trace"
> to debug because the --quiet flag seems to override it.  All thats
> visible is "myopts {'--quiet': True, '--buildpkg': True, '--verbose':
> True, '--oneshot': True, '--debug': True, '--root-deps':'rdeps'}".  I
> already searched gentoo bugs.  Does anyone know if there was a change in
> portage that would cause this, or am I overlooking something?
> 
> -P. Levine


Check to see if the version of crossdev you are using has the -q flag
in /usr/bin/cross-emerge. If so you can remove it from there.

-- 
Ned Ludd <solar@gentoo.org>
Gentoo Linux




  reply	other threads:[~2010-06-17 20:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-10 10:39 [gentoo-embedded] Re: emerge --root : users not created Marcus Priesch
2010-06-11  8:17 ` Sven Rebhan
2010-06-11 15:08   ` Marcus Priesch
2010-06-14  8:09     ` Sven Rebhan
2010-06-17 16:57       ` P. Levine
2010-06-17 19:39         ` Ned Ludd [this message]
2010-06-17 21:52           ` P. Levine
2010-06-20 11:06   ` P. Levine
2010-06-21  9:24     ` Sven Rebhan
  -- strict thread matches above, loose matches on Subject: below --
2010-02-09  5:48 P. Levine

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=1276803556.19773.1.camel@hangover \
    --to=solar@gentoo.org \
    --cc=gentoo-embedded@lists.gentoo.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