On Wed, 2005-11-30 at 09:22 -0500, Michael Cummings wrote: > Chris Gianelloni wrote: > > Here's the deal. We have a new user that installs Gentoo. After > > installing Gentoo, he tries to "emerge nagios" and it dies on building > > apache over a bug that has been known for some time and still isn't > > resolved. How exactly does that make us look? How exactly does that > > make Release Engineering look when a "default install" cannot even > > install apache properly? APACHE!!! Whether we are responsible for > > apache or not, we *are* responsible for the release. Having things > > completely broken in the default install is *not* acceptable. The bug > > was reported in June and while there has been some action in the bug, no > > fix has been issued. Again, this is *not* acceptable. Now, because of > > this, it is my determination that we have a serious problem that *will* > > affect the 2006.0 release, and I am trying to do something proactive to > > prevent it. > > > > Case in point: I built a fresh, iso downloaded this weekend from w.g.o, > and i failed to bring portage up to date before installing the stable > apache2 - and what i got was broken because it was lacking the enewuser > for apache (it built, installed, etc. - just couldn't run without either > manually adding the user or syncing the dead-end box). And this was on a > 100% stable box using the iso at > http://bouncer.gentoo.org/?product=gentoo-2005.1-install-minimum&os=x86 > (link off the where page).
Thanks for the reminder... bug #114020... :P Anyway, what I am suggesting would not have resolved this issue for you. > OK, so I'm not bright for not syncing before starting emerging - but i > can't imagine a new to gentoo user, not quite up with the "portage > changes by the nanosecond" would think to sync after building from a livecd. A new user would likely be reading the Handbook, which has the user perform an emerge --sync (except for GRP). -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
