From owner-freebsd-current Thu Dec 5 10:44: 8 2002 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 6DF8F37B404 for ; Thu, 5 Dec 2002 10:44:07 -0800 (PST) Received: from neptune.he.net (neptune.he.net [216.218.166.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id BE26C43EDC for ; Thu, 5 Dec 2002 10:44:06 -0800 (PST) (envelope-from fluid@sfmidimafia.com) Received: from borges (stalwart.codysbooks.com [209.133.54.175]) by neptune.he.net (8.8.6/8.8.2) with SMTP id KAA15102; Thu, 5 Dec 2002 10:44:08 -0800 Date: Thu, 5 Dec 2002 10:44:01 -0800 From: "Scott R." To: Forrest Aldrich Cc: freebsd-current@FreeBSD.ORG Subject: Re: CVSup Delete failures Message-Id: <20021205104401.62e36e1f.fluid@sfmidimafia.com> In-Reply-To: <5.2.0.9.2.20021205130114.01c67f70@192.168.1.1> References: <5.2.0.9.2.20021205130114.01c67f70@192.168.1.1> Organization: SFMM X-Mailer: Sylpheed version 0.8.6 (GTK+ 1.2.10; i386-portbld-freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, 05 Dec 2002 13:03:09 -0500 Forrest Aldrich wrote: > FYI, over the last few days, I've been seeing this error while doing a > > CVSUP of the code for both FreeBSD-STABLE (4.7) and Current: > > Delete src/contrib/gcc/INSTALL > Cannot delete "/usr/local/src/freebsd/5.0/src/contrib/gcc/INSTALL": > Directory not empty > > If I manually delete that directory, it gets recreated, and then this > error pops back on the next run. Permissions on the directories > aren't the issue, that I can tell -- nothing really changes manually > here in the src directories. FWIW, this is a "me too." I cvsup-ed the sources yesterday and got complaints about the same directory. I manually deleted it and re-cvsup-ed and the directory and all its contents were restored as before. Run again and the complaints still happened. I saw a couple of other reports of this behavior as well so I think it's unlikely that this is local to your setup or that we all just happened to make the same *exact* mistake somewhere along the line. Just for fun, I ran 'make buildworld' anyway and everything went without a hitch, so this anomoly doesn't seem to affect building/installing the system. -Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message