[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
"move away" again...
From: |
Spiro Trikaliotis |
Subject: |
"move away" again... |
Date: |
Wed, 12 Jul 2006 13:46:55 +0200 |
User-agent: |
Mutt/1.5.9i |
Hello,
I just good some behaviour which seems very weird to me. For of all,
look at this output:
address@hidden:~/cbm/vice$ cvs version
Client: Concurrent Versions System (CVS) 1.12.13 (client/server)
Server: Concurrent Versions System (CVS) 1.12.9 (client/server)
address@hidden:~/cbm/vice$ cat CVS/Root
:ext:cvs:/var/lib/cvs
address@hidden:~/cbm/vice$ cvs -d :ext:cvs:/var/lib/cvs/ up
address@hidden:~/cbm/vice$ cvs up
cvs update: move away `build/Makefile.am'; it is in the way
C build/Makefile.am
cvs update: move away `build/Makefile.in'; it is in the way
C build/Makefile.in
cvs update: move away `build/mingw32/linux-cross.sh'; it is in the way
[... snipp ...]
What you can see: Depending upon if I use "cvs up" or if I specifiy the
repository with -d "by hand", cvs up behaves differently: Directly,
without specifying the patch, I got the "move away" message; but with
specifying the path, I do not get it.
Interestingly, the path stored in CVS/Root is exactly the same as the
one I am specifying on the command-line; this is something which I do
not understand.
Oh, I stand corrected. After having written this and I tested something
more, I found the reason: CVS/Root was written without a last slash
(/var/lib/cvs, not /var/lib/cvs/). Editing the file by hand fixed the
problem.
Now, the important questions for me:
1. should it work without the trailing slash, or shouldn't it?
2. if it should not work, why did cvs wrote that wrong CVS/Root in the
first place?
Best regards,
Spiro.
PS: Waiting for all of the "I'm out of town" replies... :(((
--
Spiro R. Trikaliotis http://opencbm.sf.net/
http://www.trikaliotis.net/ http://www.viceteam.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- "move away" again...,
Spiro Trikaliotis <=