RE: Repository troubles - expert help needed

[Anders Truelsen]

Hi Mike

An option is to simply erase the bad ,v files from the repository and
add them again from the client. This will create two new ,v files that
should be sound.
This will of cause nuke any history on those files including tags and
branches, but I suppose you can live with that.

As always, when manipulating the repository directly:
PROCEED WITH CARE!

Good Luck
anders

-Original Message-
From: Mike Ayers [mailto:[EMAIL PROTECTED]] 
Sent: 24. juli 2002 02:13
To: [EMAIL PROTECTED]
Subject: Repository troubles - expert help needed


I am having serious problems, and need help.  I suspect that my
repository is 
corrupted.  I would like to know what to do to fix it.

As part of the project documentation, I checked in the WinCVS
user's guide. 
This is 1 html file, wincvs11.htm, and about 60 images named Image*.jpg 
(numbered 1-63 with a few missing).  The problem is with Image55.jpg and

possibly Image56.jpg.  I found that I could get logs on Image57.jpg and 
Image54.jpg, but not those two.  I also could get logs on other randomly

sampled files.  It seems that any operation on the directory will fail
when it 
gets to Image55.jpg:

cvs update -P (in directory C:\dssi\cameras\cam1\tools\doc\WinCVS\)
cvs update: Updating .
cvs update: nothing known about Image55.jpg

I am seeing a process crash (I suspect that it's the spawned CVS
process) 
whenever I try to update the directory.  After the crash, there is a new
file 
left in the repository such as:

#cvs.rfl.fluffy(mike).1208

My machine is fluffy and my username is mike.

When I cd into the repository directory and `more` the files, I
notice that all 
the files have headers:

SNIP
head1.1;
access;
symbols
 dssi-cam1-0_3:1.1
 dssi-cam1-0_2:1.1;
locks; strict;
comment @# @;
expand  @b@;


1.1
date2002.06.25.15.30.51;author mike;state Exp;
branches;
next;


desc
@@


1.1
log
@Cumulative update
@
text
/SNIP

EXCEPT Image55.jpg,v and Image56.jpg,v!  I think I'm getting
warm here...

The real issue, though, is how to correct this problem without
disturbing the 
rest of the repository.

Gurus?


aTdHvAaNnKcSe,

/|/|ike


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs

Repository troubles - expert help needed

[Mike Ayers]

I am having serious problems, and need help.  I suspect that my repository is 
corrupted.  I would like to know what to do to fix it.

As part of the project documentation, I checked in the WinCVS user's guide. 
This is 1 html file, wincvs11.htm, and about 60 images named Image*.jpg 
(numbered 1-63 with a few missing).  The problem is with Image55.jpg and 
possibly Image56.jpg.  I found that I could get logs on Image57.jpg and 
Image54.jpg, but not those two.  I also could get logs on other randomly 
sampled files.  It seems that any operation on the directory will fail when it 
gets to Image55.jpg:

cvs update -P (in directory C:\dssi\cameras\cam1\tools\doc\WinCVS\)
cvs update: Updating .
cvs update: nothing known about Image55.jpg

I am seeing a process crash (I suspect that it's the spawned CVS process) 
whenever I try to update the directory.  After the crash, there is a new file 
left in the repository such as:

#cvs.rfl.fluffy(mike).1208

My machine is fluffy and my username is mike.

When I cd into the repository directory and `more` the files, I notice that 
all 
the files have headers:

SNIP
head1.1;
access;
symbols
 dssi-cam1-0_3:1.1
 dssi-cam1-0_2:1.1;
locks; strict;
comment @# @;
expand  @b@;


1.1
date2002.06.25.15.30.51;author mike;state Exp;
branches;
next;


desc
@@


1.1
log
@Cumulative update
@
text
/SNIP

EXCEPT Image55.jpg,v and Image56.jpg,v!  I think I'm getting warm here...

The real issue, though, is how to correct this problem without disturbing the 
rest of the repository.

Gurus?


aTdHvAaNnKcSe,

/|/|ike


___
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs