From owner-freebsd-ports Sun Sep 29 15:17:40 1996 Return-Path: owner-ports Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id PAA02916 for ports-outgoing; Sun, 29 Sep 1996 15:17:40 -0700 (PDT) Received: from austin.polstra.com (austin.polstra.com [206.213.73.10]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id PAA02878 for ; Sun, 29 Sep 1996 15:17:36 -0700 (PDT) Received: from austin.polstra.com (jdp@localhost) by austin.polstra.com (8.7.6/8.7.3) with ESMTP id PAA00127; Sun, 29 Sep 1996 15:17:30 -0700 (PDT) Message-Id: <199609292217.PAA00127@austin.polstra.com> To: Andreas Klemm cc: ports@freebsd.org Subject: Re: building modula3 port In-reply-to: Your message of "Sun, 29 Sep 1996 15:57:24 +0200." Date: Sun, 29 Sep 1996 15:17:29 -0700 From: John Polstra Sender: owner-ports@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > A bug in cvsup ?! > > Look: > > freefall.freebsd.org has the following patches for graphics/xpaint > in the patches subdir: > > andreas@freefall 67% ll > total 10 > drwxrwxr-x 2 swallace ncvs 512 Sep 29 15:59 ./ > drwxrwxr-x 5 swallace ncvs 512 Sep 29 15:59 ../ > -r--r--r-- 1 asami ncvs 2423 Jun 15 02:51 patch-aa,v > ... > Just recently I used your cvsup to update my local cvs repository. > This is the xpaint/patches directory in my local CVS directory: > > andreas@klemm{744} /local/CVS/ports/graphics/xpaint/patches ll > total 8 > -r--r--r-- 1 root wheel 2423 15 Jun 02:51 patch-aa,v > -r--r--r-- 1 root wheel 886 2 Jan 1995 patch-ab,v > -r--r--r-- 1 root wheel 1834 29 Mär 1995 patch-ac,v > -r--r--r-- 1 root wheel 733 2 Jan 1995 patch-ad,v > -r--r--r-- 1 root wheel 1006 2 Jan 1995 patch-ae,v > > The patch-aa seems to be the same, but the patch-ab - patch-ae files > weren't removed. I think I know what's going on. It's not really a bug. First of all, what _are_ those files "patch-a[b-d],v" on your system? Are they really patches for xpaint? Why don't they exist in the CVS repository? Even if they had been removed with "cvs rm", they should still exist in the Attic. I will assume that they really are old patches, and that somebody erroneously deleted them from the CVS repository, instead of using "cvs rm" as they should have done. Still, I think CVSup did the right thing. Here is what I think was the sequence of events: 1. The patches existed both in the main repository, and in your local copy. 2. Somebody deleted the patches from the main repository, but they remained in your local repository. 3. You started using CVSup for the first time. In that case, CVSup would consider "patch-a[b-e],v" to be extra, unknown files in your local repository. It didn't create them, and there's no trace of them in the master repository. It doesn't know anything about them -- and so it won't delete them. It will never delete anything that it doesn't know about. That's what I think happened. John -- John Polstra jdp@polstra.com John D. Polstra & Co., Inc. Seattle, Washington USA "Self-knowledge is always bad news." -- John Barth