"multiple revisions locked" problem

[Naveen Srinivasa Murthy]

>When u do a lock -> edit -> modify file -> commit on a cvs file
>for the first time, we get an error saying "Multiple revisions
>locked, please specify one."
>
>amazingly, i checked on lots of mailing lists. There seems to be
>no word about any patch/fix for CVS to solve the problem.
>
>can anyone help? Is there a fix/workaround for this?
>
>thanks
>Naveen




From address@hidden Tue Dec 04 17:18:39 2001
Received: from [64.242.150.16] (helo=mailhub.ejasent.com)
        by fencepost.gnu.org with esmtp (Exim 3.22 #1 (Debian))
        id 16BNtd-0007if-00
        for <address@hidden>; Tue, 04 Dec 2001 17:18:38 -0500
Received: from ejasent.com (192.168.10.10 [192.168.10.10]) by 
mailhub.ejasent.com with SMTP (Microsoft Exchange Internet Mail Service Version 
5.5.2653.13)
        id XJ6BQ8T8; Tue, 4 Dec 2001 14:16:30 -0800
Message-ID: <address@hidden>
Date: Tue, 04 Dec 2001 14:16:21 -0800
From: David Taylor <address@hidden>
Organization: Ejasent Inc.
X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en, zh, zh-TW, zh-CN
MIME-Version: 1.0
To: Wolfgang Kormann <address@hidden>
CC: address@hidden
Subject: Re: copy repository to a new cvs-server
References: <address@hidden>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: address@hidden
Errors-To: address@hidden
X-BeenThere: address@hidden
X-Mailman-Version: 2.0.5
Precedence: bulk
List-Help: <mailto:address@hidden>
List-Post: <mailto:address@hidden>
List-Subscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Id: Announcements and discussions for the CVS version control system 
<info-cvs.gnu.org>
List-Unsubscribe: <http://mail.gnu.org/mailman/listinfo/info-cvs>,
        <mailto:address@hidden>
List-Archive: <http://mail.gnu.org/pipermail/info-cvs/>

Wolfgang Kormann wrote:

> hi,
> I have a new cvs-server and I want to copy the whole repository
> from the old to the new server. The newest cvs-version is installed
> and running on the new one.
> What is the best way to do this?
>

See http://mail.gnu.org/pipermail/info-cvs/2001-June/016556.html