From owner-freebsd-current  Tue Mar  4 21:02:57 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id VAA23215
          for current-outgoing; Tue, 4 Mar 1997 21:02:57 -0800 (PST)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA23207
          for <freebsd-current@freefall.freebsd.org>; Tue, 4 Mar 1997 21:02:34 -0800 (PST)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.3/8.6.9) id PAA07659; Wed, 5 Mar 1997 15:59:11 +1100
Date: Wed, 5 Mar 1997 15:59:11 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199703050459.PAA07659@godzilla.zeta.org.au>
To: chuckr@glue.umd.edu, freebsd-current@freefall.freebsd.org
Subject: Re: cvs tree breakage (ctm)
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>I maintain my cvs tree via ctm, and for the first time, I have some
>breakage here.  I'd heard about some breakage that occurred via src-cur,
>but since that wasn't cvs, I ignored it.  Can't do that now, and can't
>update from cvs -- I get this error:
>
>cvs update: in directory contrib/ipfilter/BSD:
>cvs [update aborted]: there is no repository /home/ncvs/src/contrib/ipfilter/BSD
>
>I know this must be caused via ctm, because I have poor net connectivity,
>so reloading the cvs tree would be really hard on me, and so I am
>scrupulous about never touching my cvs tree with anything but ctm_rmail.

This is apparently caused by the repository being cleaned up too fast.
It has nothing to do with ctm.  The problem is normally minimised by not
removing directories in the repository for months or years.

Fix: rm -rf contrib/ipfilter/BSD, etc.

Bruce