RE: Unable to increment revision number

[Christopher Cheng]

I was trying to run the script with perl on windows. It says "can't
stat".... 


C:\Java\espresso>perl validate_repo.pl -v
Verbose Mode Turned On
Processing:
:pserver;username=myusername;password=mypassword;hostname=192.168
.0.200:\cvsroot\espresso
Can't stat
:pserver;username=christopher.cheng;password=ccheng;hostname=192.168.
0.200:\cvsroot\espresso: No such file or directory
 at validate_repo.pl line 273
Total Files: 0  Corrupted files: 0  Invalid revs: 0  Extra files: 0  Ignored
Files: 0 Total Revisions: 0  Interesting Revisions: 0


I also tried to run with 
"--cvsroot=:pserver;username=myusername;password=mypassword;hostname=192.168
.0.200:\cvsroot"

Still no luck...



-----Original Message-----
From: Jim Hyslop [mailto:address@hidden 
Sent: Wednesday, September 14, 2005 2:47 AM
To: Christopher Cheng
Cc: 'Larry Jones'; 'Dave Korn'; address@hidden
Subject: Re: Unable to increment revision number

Christopher Cheng wrote:
> Thanks for the guide, I will definitely try that. By the way, I tried to
> edit the file myself. I am able to run 'cvs log -h'
> 
> RCS file: /cvsroot/espresso/web/WEB-INF/conf/struts-references.xml,v
> Working file: struts-references.xml
> head: 1.23
> branch:
> locks: strict
> access list:
> symbolic names:
>       r1-1-1: 1.19.0.2
>       r1-1: 1.19.0.4
> keyword substitution: kv
> total revisions: 24
>
============================================================================
> 
> 
> However, 'cvs update -A' still doesn't get me 1.23. That's very strange.
Any
> idea?

There may be more corruption remaining in the file - hopefully you have 
not introduced any further problems. I hope you backed up the file 
before changing it.

Stop what you are doing now, download the validate_repo script and run 
it. Since you're running CVSNT, I'm guessing you're using Windows, in 
which case you will also have to download and install Cygwin, or some 
other UNIX-like shell, to run the script.

*Please* take the time to do this now, before your repository becomes 
more corrupted.

Earlier, Larry mentioned:
> If you have a recent backup that isn't also
> corrupted, you should probably restore it.

Do you have recent backup of the repository? If so, you will likely be 
further ahead to restore the corrupt file(s) from your backup, rather 
than trying to muddle your way through the RCS file, which risks further 
corruption.

-- 
Jim