Date: Sat, 19 May 2007 01:22:40 -0700 (PDT) From: KAYVEN RIESE <kayve@sfsu.edu> To: linimon@lonesome.com (Mark Linimon) Cc: Chris <chrcoluk@gmail.com>, freebsd-stable@freebsd.org, Craig Boston <craig@feniz.gank.org> Subject: Re: fast rate of major FreeBSD releases to STABLE Message-ID: <Pine.SOC.4.64.0705190121120.17361@libra.sfsu.edu> In-Reply-To: <20070517200615.GA19092@soaustin.net> References: <3aaaa3a0705170830g46487cc7occc8a51b82a9118b@mail.gmail.com> <20070517172415.06DEF45042@ptavv.es.net> <20070517183510.GB42562@nowhere> <20070517200615.GA19092@soaustin.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 17 May 2007, linimon@lonesome.com (Mark Linimon) wrote: > On Thu, May 17, 2007 at 01:35:10PM -0500, Craig Boston wrote: > > The alternative would have been to commit what we had and _then_ found > out all the bugs in the upgrade process (note: you won't be able to just > blindly use portupgrade -af; you will need to read the UPDATING file for > the proper procedure. This is the unusual case of being such a sweeping > change that the port management tools are not completely up to the task.) okay could this freeze an explanation for the fact that my x is totally hosed? i know any random joe can't necessarily answer that.. but assuming it is true.. umm.. how long is this freeze going to last then? > >> I don't know if portmgr@ has approved any commits during the xorg freeze >> or not. > > Nope. There are simply too many ports that have interdependencies among > the xorg ports. > > mcl > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SOC.4.64.0705190121120.17361>