From owner-freebsd-questions Sat Feb 20 14:34:43 1999 Delivered-To: freebsd-questions@freebsd.org Received: from send203.yahoomail.com (send203.mail.yahoo.com [128.11.68.127]) by hub.freebsd.org (Postfix) with SMTP id 6778F11190 for ; Sat, 20 Feb 1999 14:34:41 -0800 (PST) (envelope-from keraba@yahoo.com) Message-ID: <19990220223613.15756.rocketmail@send203.yahoomail.com> Received: from [207.217.245.32] by send203.mail.yahoo.com; Sat, 20 Feb 1999 14:36:13 PST Date: Sat, 20 Feb 1999 14:36:13 -0800 (PST) From: Keraba Subject: Upgrading to 3.1R using cvs update To: freebsd-questions@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm trying to upgrade to 3.1R and hoping to take advantage of the fact that I have all the 3.0R source code by pulling across only the updates over my slow modem link. Unfortunately I don't know if 'cvs update' can do what I want. When I attempt to update using cvs -d anoncvs@anoncvs.freebsd.org update -r RELEASE_3_1_0 (in a ports directory since that's where the tag is valid) it says cvs [server aborted]: cannot write /cvs/CVSROOT/val-tags: Permission denied This is apparently because cvs needs "to keep track of what tags are valid tag names". [Cederqvist v1.9 4.4.2] Is there a flag I can give cvs to tell it not to try to open this file (read-write) ? In other words, force it to trust the tag I've given ? If not, it would seem there's no way to use update and tags with anonymous cvs. (Alternatively I could give it a timestamp to update my files to but this presents the problems of how to figure out exactly when the last 3.1R check-in was made, avoiding check-ins right after the release and getting files on branches.) If cvs can't do this, can cvsup take advantage of the 3.0R source present ? _________________________________________________________ DO YOU YAHOO!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message