[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
cvs-1.11.1p1: cvs [export aborted]: cannot export into a workingv
From: |
Wade Carpenter |
Subject: |
cvs-1.11.1p1: cvs [export aborted]: cannot export into a workingv |
Date: |
Thu, 28 Mar 2002 00:26:19 -0800 |
Hello,
I just wanted to add to this thread from January that if the user's CVSROOT
is incorrectly set, this error will come up as well.
For example, if you are not in client-server mode and your
CVSROOT=/home/cvs/cvsroot/ (note the trailing '/') then everything will
work fine, with the exception of 'export'. Changing back CVSROOT to the
proper CVSROOT=/home/cvs/cvsroot will correct the error.
I was thinking a sanity check could be added when parsing CVSROOT to check
for the extraneous trailing '/'?
Regards,
Wade
Original Message:
Seelbach, Wolfgang Seelbach@proalpha.de
Thu, 24 Jan 2002 15:05:00 +0100
Hi!
With cvs 1.11.1p1 in "client-server-mode" (CVSROOT=:pserver:...) an
"export" always fails:
# cvs export -D 2002-02-02 aModule
==> cvs [export aborted]: cannot export into a working directory
The source of this error message is checkout.c, function build_one_dir:
in "client-server-mode" the "current working dir" is a temporary directory
on the "cvs-server". This directory contains also subdirectories named
"CVS". We solved the problem with the changes which can be found in
the accompanying file cvs-1.11.1p1.checkout.c.cdiff.
<<cvs-1.11.1p1.checkout.c.cdiff>>
This should be regarded as a "hot fix". A closer review of function
build_one_dir of checkout.c might be necessary or suggestive.
> Regards,
>
> Wolfgang Seelbach
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- cvs-1.11.1p1: cvs [export aborted]: cannot export into a workingv,
Wade Carpenter <=