From owner-freebsd-current@FreeBSD.ORG Tue Mar 23 08:21:52 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 420B416A4CE for ; Tue, 23 Mar 2004 08:21:52 -0800 (PST) Received: from relay.epsb.ca (relay.epsb.ca [198.161.119.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1017343D4C for ; Tue, 23 Mar 2004 08:21:52 -0800 (PST) (envelope-from Sean.Page@epsb.ca) Received: from exchange03.epsb.ca (exchange03.epsb.ca [10.0.5.11]) by relay.epsb.ca (8.12.8p2/8.12.8) with ESMTP id i2NGLnKD099870; Tue, 23 Mar 2004 09:21:49 -0700 (MST) (envelope-from Sean.Page@epsb.ca) Received: by exchange03.epsb.ca with Internet Mail Service (5.5.2653.19) id <1NR26DWB>; Tue, 23 Mar 2004 09:24:25 -0700 Message-ID: From: Sean Page To: "'noackjr@alumni.rice.edu'" Date: Tue, 23 Mar 2004 09:22:30 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain cc: "'current@freebsd.org'" Subject: RE: Strange Buildworld problem X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 23 Mar 2004 16:21:52 -0000 > > SUP_UPDATE= yes > SUP= /usr/local/bin/cvsup > SUPFLAGS= -g -L 2 > SUPHOST= cvsup.ca.freebsd.org > #SUPHOST= cvsup4.freebsd.org > SUPFILE= /usr/share/examples/cvsup/stable-supfile Why are you using stable-supfile? Unless you changed it, this file tracks RELENG_4 (4.9-STABLE), as 5.x has not become -STABLE yet. Even if you did change it, your next installworld will clobber it back to RELENG_4. A better bet is to copy the supfile someplace safe and modify to track RELENG_5_2 or '.' or whatever... > #SUPFILE= /usr/share/examples/cvsup/security-supfile This looks more promising (you seem to have created this file). I was involved in a discussion with re@ about supfiles a while back (even submitted patches), but nothing ever came of it. The consensus seemed to be on creating a "release-supfile" to track the security release branch. Jon Hi Jon, Thanks for the comment. Naturally I changed the file to track '.', and haven't had a problem in the past with it being clobbered unless I rebuilt the cvsup port. A good suggestion none the less, I've renamed the cvsup file to current-supfile and updated make.conf accordingly. In the mean time I still can't get a buildworld happening :( If you have any further ideas, I'm open to suggestions. Thanks again, Sean.