From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Too many problems with groupadd when creating stage3
Date: Wed, 28 Oct 2009 16:42:49 -0400 [thread overview]
Message-ID: <200910281642.50050.vapier@gentoo.org> (raw)
In-Reply-To: <1256082969.3454.18.camel@inertia.twi-31o2.org>
[-- Attachment #1: Type: Text/Plain, Size: 1269 bytes --]
On Tuesday 20 October 2009 19:56:09 Chris Gianelloni wrote:
> On Thu, 2009-10-15 at 13:52 -0400, Mike Frysinger wrote:
> > On Thursday 15 October 2009 13:50:40 Mike Frysinger wrote:
> > > or just fix catalyst
> >
> > erm, that's probably wrong. catalyst does what it's told as directed by
> > the portage tree profiles. so the profiles probably need tweaking to
> > produce a sane stage2.
>
> Tried it. If you'd prefer, I can pull up the list of bugs where we hit
> this on nearly every release, but since a viable solution was never
> reached, I don't see how it would help.
>
> Our main "fix" was to not build stages for desktop profiles, or to use a
> complete stage3 tarball as input for another stage3, but that's equally
> as broken.
>
> I'd *gladly* fix catalyst to work around this, if I had a clue how to do
> so. Hacking profiles ended up yielding nothing workable, just so
> everyone knows.
not sure why we're still even using this stage[123] system. seems like
catalyst could be implemented in all of three commands:
ROOT=/tmp/stage3_pre emerge system -e
chroot /tmp/stage3 env ROOT=/tmp/stage3 emerge system -e
then we wouldnt need these USE="build bootstrap" hacks nor would we need the
packages.build cruft
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-10-28 20:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-15 14:32 [gentoo-catalyst] Too many problems with groupadd when creating stage3 Juan Luis Pérez Pérez
2009-10-15 15:07 ` Peter Stuge
2009-10-15 16:42 ` Mike Frysinger
2009-10-15 16:48 ` Peter Stuge
2009-10-15 17:30 ` Mike Frysinger
2009-10-15 17:45 ` Peter Stuge
2009-10-15 17:50 ` Mike Frysinger
2009-10-15 17:52 ` Mike Frysinger
2009-10-20 23:56 ` Chris Gianelloni
2009-10-28 20:42 ` Mike Frysinger [this message]
2009-10-29 12:34 ` Andrew Gaffney
2009-10-29 13:56 ` Mike Frysinger
2009-10-30 2:10 ` Andrew Gaffney
2009-10-30 1:36 ` Peter Stuge
2009-10-30 2:11 ` Andrew Gaffney
2009-10-20 23:53 ` Chris Gianelloni
2009-10-23 4:27 ` Peter Stuge
2009-10-15 17:49 ` Juan Luis Pérez Pérez
2009-10-15 16:53 ` Juan Luis Pérez Pérez
2009-10-15 17:16 ` Peter Stuge
2009-10-16 14:00 ` [gentoo-catalyst] " Juan Luis Pérez Pérez
2009-10-16 17:07 ` Juan Luis Pérez Pérez
2009-10-20 23:58 ` Chris Gianelloni
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=200910281642.50050.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-catalyst@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