From owner-freebsd-stable@FreeBSD.ORG Thu Dec 8 21:42:50 2005 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 978A416A420 for ; Thu, 8 Dec 2005 21:42:50 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.12]) by mx1.FreeBSD.org (Postfix) with SMTP id 93BD343D49 for ; Thu, 8 Dec 2005 21:42:47 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 86787 invoked by uid 399); 8 Dec 2005 21:42:46 -0000 Received: from localhost (HELO ?192.168.0.3?) (dougb@dougbarton.us@127.0.0.1) by localhost with SMTP; 8 Dec 2005 21:42:46 -0000 Message-ID: <4398A8D5.7050404@FreeBSD.org> Date: Thu, 08 Dec 2005 13:42:45 -0800 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Thunderbird 1.5 (X11/20051206) MIME-Version: 1.0 To: secmgr References: <200512051518.43896.vizion@vizion.occoxmail.com> <20051206120026.GC62078@ip.net.ua> <200512061148.01012.vizion@vizion.occoxmail.com> <200512061320.45584.vizion@vizion.occoxmail.com> <20051206212850.GA79286@xor.obsecurity.org> <43960445.4050202@jim-liesl.org> <20051206214613.GA79648@xor.obsecurity.org> <43962B8E.1090407@jim-liesl.org> <20051206163732.K60888@znfgre.qbhto.arg> <43975511.5070002@jim-liesl.org> In-Reply-To: <43975511.5070002@jim-liesl.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-stable@freebsd.org Subject: Re: Upgrading 5.3 > 6.0 buildworld failure now in libmagic X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Dec 2005 21:42:50 -0000 secmgr wrote: > Doug Barton wrote: >> + When upgrading from one major version to another, it is >> + generally best to upgrade to the latest code in the branch >> + currently installed first, then do another upgrade to the >> + new branch. >> > Or as another poster said, just say latest RELENG_5 prior to upgrade Based on recommendations from this thread and from kris, I changed the wording to be more generic, and added the same text to the UPGRADING file in HEAD, and RELENG_6. > Well, if it's common knowledge, lets see it documented. We're only > talking a few lines in the handbook or the release notes, not an entire > chapter. I did my bit. I'm sure that the freebsd-doc folks are eagerly anticipating your patches, since this is such an easy thing to add. :) > > My frustration comes from the fact that this seems to be getting worse, > not better. From your perspective that may be true, however from a more general perspective I don't agree. C'est la vie. > In addition, every time I bring this up, I'm told (usually > by someone with a freebsd.org address) that, "oh we all know/knew about > that" or, "it's common knowledge". I have been very careful to say that I agree that our documentation can always be improved. I've also been very careful to say that the only way this will happen is if someone steps up to do it. I realize that's not the answer you're looking for, but it's the only one we have, and all the elegantly phrased rants, descriptions of what we should be doing for you (and how we should be doing it), and other things that you (pl.) wish were so won't change that. Doug -- This .signature sanitized for your protection