From owner-freebsd-stable@FreeBSD.ORG Wed Dec 7 21:35: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 B769D16A41F; Wed, 7 Dec 2005 21:35:50 +0000 (GMT) (envelope-from security@jim-liesl.org) Received: from mta9.adelphia.net (mta9.adelphia.net [68.168.78.199]) by mx1.FreeBSD.org (Postfix) with ESMTP id A5B6743D55; Wed, 7 Dec 2005 21:35:49 +0000 (GMT) (envelope-from security@jim-liesl.org) Received: from daemon.jim-liesl.org ([70.33.46.68]) by mta9.adelphia.net (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP id <20051207213548.QWPE5128.mta9.adelphia.net@daemon.jim-liesl.org>; Wed, 7 Dec 2005 16:35:48 -0500 Received: from daemon.jim-liesl.org (localhost.clspco.adelphia.net [127.0.0.1]) by daemon.jim-liesl.org (Postfix) with ESMTP id A8581612D; Wed, 7 Dec 2005 14:38:50 -0700 (MST) Received: from [127.0.0.1] (daemon.clspco.adelphia.net [192.168.1.15]) by daemon.jim-liesl.org (Postfix) with ESMTP id 437A360E1; Wed, 7 Dec 2005 14:38:50 -0700 (MST) Message-ID: <43975511.5070002@jim-liesl.org> Date: Wed, 07 Dec 2005 14:33:05 -0700 From: secmgr User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Barton 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> In-Reply-To: <20051206163732.K60888@znfgre.qbhto.arg> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP 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: Wed, 07 Dec 2005 21:35:51 -0000 Doug Barton wrote: > How does this change to UPDATING in RELENG_6 look to you: > > Index: UPDATING > =================================================================== > RCS file: /home/ncvs/src/UPDATING,v > retrieving revision 1.416.2.7 > diff -u -r1.416.2.7 UPDATING > --- UPDATING 1 Nov 2005 23:44:40 -0000 1.416.2.7 > +++ UPDATING 7 Dec 2005 00:42:04 -0000 > @@ -229,7 +229,13 @@ > page for more details. > > Due to several updates to the build infrastructure, source > - upgrades from versions prior to 5.3 no longer supported. > + upgrades from versions prior to 5.4-STABLE are not likely > + to succeed. > + > + 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 > This is an open source project. The only way that things improve is if > people help make it better. It's also worth pointing out that this > issue of upgrading to the latest version of the branch you're in has > been "common knowledge" for, basically, always; so if the folks that > wrote the release notes neglected to include it, it's understandable. > (Although, as you point out, potentially frustrating for new(er) users.) 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. >> If RE wants to change the requirements for upgrading, then how >> bleeping hard would it be to update either release notes or errata. >> It's not so much that I now need to do multiple upgrades (ok, that IS >> pretty annoying), it's that I'd never of known unless I followed this >> thread. > > > Ok, so, after you calm down a bit, why don't you write a message to > re@freebsd.org and mention this issue. My frustration comes from the fact that this seems to be getting worse, not better. 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". In the case of the vinum/gvinum/gmirror trainwreck, I got silence, even though I strongly suspect multiple people knew there were problems, but just didn't want to talk about them. I'd gladly help document some of this, but I'm not the one who knows where the skeletons are snoozing (at least till I trip on a femur) So whats the big issue with letting the rest of us in on the secrets? I'm not looking for a book, just a line or two saying "here be dragons" somewhere /other /than the basement of the planing department in the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying 'Beware of the Leopard' (apologies to Doug Adams).