[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: cvs aborted !!
RE: cvs aborted !!
Tue, 4 Sep 2001 10:14:13 -0500
I was checking yesterday the same command for a different file and after
that the file is corrupt, I was thinking that this command "cvs admin
-orev1::rev2" is only useful for text files, not for binaries, the reason
that I say that is because after I did this command, the revision are
deleted, but I check the files,v in my repository and cvs tried to put the
difference code between the last version and last but one, obviously cvs
fail when trying to put the difference because are binaries files, check
@Binary files /cvswork/cvsBAAa10995 and /cvswork/cvsAAAa10995 differ
I not really sure if I say the correct, what are you think ?
From: address@hidden [mailto:address@hidden
Sent: Monday, September 03, 2001 3:04 PM
Subject: Re: cvs aborted !!
Zanabria, Moises writes:
> Oopps :(, actually this problem it happened after I deleted some revisions
> for this file with "cvs admin -o rev2::rev32 SRMActuateReports.dll" ,
That, by itself, wouldn't corrupt the RCS file.
> actually I did this command only for this file, the file is still there, I
> can run cvs co, but I can not run cvs log, cvs status , return the
That implies that the damage is to one of the delta sections. By
checking out previous versions (you can use -p and send the output to
/dev/null) and seeing which work and which don't, you can determine
which delta is damaged.
> that I sent in my last email, regarding your questions:
> For the second, are you accessing your repository with some kind of
> shared filesystem (like Windows file sharing, Samba, or NFS)? Yes, I use
I strongly suggest moving your repository to a local disk (or moving
your CVS server to the machine where the current repository exists).
Good gravy, whose side are you on?! -- Calvin