How about not breaking apache? I was a little beyond pissed when I had to sit there for 2 hours trying to figure out why my apache was broken, and who was going to get put on my list of being kicked in the junk. Just for some stupid config file changes. I find it very hard to believe you guys couldn't come up with a better way to do it. Even if that means doing evil stuff in one of the stages that isn't sandboxed.
--Iggy On Sat, 2005-04-09 at 15:59 +0200, Christian Parpart wrote: > Hi guys, > > refering to [1] and [2] I must see, that we've been in testing phase for > quite > a long time now. Our eclass' changes reflect only to masked and/or testing > ebuilds, though, marking stable ebuilds somewhat obsolete. > > Although, apache httpd is bumping 2.0.54 very soon and our latest *stable* is > just 2.0.52-r1 (and yet obsolete in all aspects). > > Before bumping a new 2.0.54 release of apache2, I would like to catch all > problems we maybe have to fix right before going stable. > > Though, ... > > please test apache-2.0.53 and/or apache-1.3.33-r2 (including your favorite > apache modules) on your system(s) and please report any oddies you > experience. > > Thanks in advance, > Christian Parpart. > > [1] http://packages.gentoo.org/ebuilds/?apache-2.0.53 > [2] http://packages.gentoo.org/ebuilds/?apache-1.3.33-r2 > -- gentoo-dev@gentoo.org mailing list
