From owner-freebsd-questions Thu Jul 27 21:51:51 2000 Delivered-To: freebsd-questions@freebsd.org Received: from sable.cc.vt.edu (sable.cc.vt.edu [198.82.161.196]) by hub.freebsd.org (Postfix) with ESMTP id 6336537BFBD for ; Thu, 27 Jul 2000 21:51:48 -0700 (PDT) (envelope-from dafishe4@vt.edu) Received: from mail.vt.edu (gkar.cc.vt.edu [198.82.161.190]) by sable.cc.vt.edu (8.9.3/8.9.3) with ESMTP id AAA12936 for ; Fri, 28 Jul 2000 00:51:46 -0400 (EDT) Received: from zathras.cc.vt.edu ([198.82.162.117]) by gkar.cc.vt.edu (Sun Internet Mail Server sims.3.5.2000.03.23.18.03.p10) with ESMTP id <0FYE0032G5I9O9@gkar.cc.vt.edu> for freebsd-questions@freebsd.org; Fri, 28 Jul 2000 00:51:45 -0400 (EDT) Date: Fri, 28 Jul 2000 00:51:36 -0400 From: dafishe4 Subject: cvsup and checkout problems To: freebsd-questions@freebsd.org Message-id: <398123E5@zathras.cc.vt.edu> MIME-version: 1.0 X-Mailer: WebMail (Hydra) SMTP v3.61 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7bit X-WebMail-UserID: dafishe4 X-EXP32-SerialNo: 00002964 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG i'm having some trouble using cvsup to update my version of freebsd to 4.1. i created a cvsuptfile: src-cvsupfile *default tag=RELENG_4 *default release=cvs *default host=cvsup3.freebsd.org *default base=/usr/local/etc/cvsup *default prefix=/usr/cvsuproot *default delete *default use-rel-suffix *default compress src-all next i ran: cvsup -g -L2 /usr/local/etc/cvsup/src-cvsupfile this appeared to work fine...however i didn't get exactly what i expected. none of the files in /usr/cvsuproot/src end in ,v. anyway next i ran: cvs checkout -d /usr/src src this appeared to run ok, but it only created the directory structure. every directory has a CVS directory...but there are no files. i've used cvsup to keep my ports tree up-to-date...and never had any problems like this. any help would be appreciated. thanks. -- daniel fisher To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message