From owner-freebsd-security Thu Apr 19 18:41: 4 2001 Delivered-To: freebsd-security@freebsd.org Received: from mail.wlcg.com (mail.wlcg.com [207.226.17.4]) by hub.freebsd.org (Postfix) with ESMTP id 53D5D37B422 for ; Thu, 19 Apr 2001 18:41:00 -0700 (PDT) (envelope-from rsimmons@wlcg.com) Received: from localhost (rsimmons@localhost) by mail.wlcg.com (8.11.3/8.11.3) with ESMTP id f3K1fQa84146; Thu, 19 Apr 2001 21:41:26 -0400 (EDT) (envelope-from rsimmons@wlcg.com) Date: Thu, 19 Apr 2001 21:41:22 -0400 (EDT) From: Rob Simmons To: Brian Tiemann Cc: Kris Kennaway , Ben Vaughn , Chris Faulhaber , Subject: Re: Another glob problem In-Reply-To: <3ADF8EFB.1B6EBA04@packeteer.com> Message-ID: <20010419213925.S83948-100000@mail.wlcg.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 Make sure that you remove everything below /usr/sup/src-all/ There should be a file there called checkouts.cvs that could hose up a fresh checkout. Robert Simmons Systems Administrator http://www.wlcg.com/ On Thu, 19 Apr 2001, Brian Tiemann wrote: > Yes, I cvsupped immediately before rebuilding. That's the entire > problem. > > The current best attempt has been to remove /usr/src and /usr/obj, > cvsup to checkout a fresh 4-STABLE tree as of this afternoon, and try to > build libc. But that's not working. So while what's causing libc to not > compile is probably not related to the patch, what it means is that > we're all effectively left without a solution to the ftpd overflow > problem until the build error in mpool.c is dealt with. > > I cvsup 4-STABLE every night. I sort of thought that was what "tracking > -STABLE" meant. It's so I don't have to worry about downloading patches. > > Brian > > > Kris Kennaway wrote: > > > > On Thu, Apr 19, 2001 at 06:10:11PM -0700, Brian Tiemann wrote: > > > Well, that's great, but something needs to be looked at for those of us > > > tracking 4-STABLE. Thanks... > > > > If you're tracking -stable, why not just cvsup? We can't possibly > > test the patches with every possible different point on the RELENG_4 > > continuum, so we kind of assume that if you've cvsupped once to get to > > a non-release version of -stable you can do it again. Having said > > that, I can't think of any differences in libc which would have caused > > this to fail between 4.2-REL and some later version of 4.2-STABLE. > > > > Kris > > > > ------------------------------------------------------------------------ > > Part 1.2Type: application/pgp-signature > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (FreeBSD) Comment: For info see http://www.gnupg.org iD8DBQE635PGv8Bofna59hYRAy1gAJ0bPosUHIAVItNcyQ1wmk7rZvXHnACeK1a1 z6/tCKdyZo19UrSbvaCaxck= =z8cs -----END PGP SIGNATURE----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message