RE: Repository troubles - expert help needed
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
Entries for multiple $CVSROOT
Hi, I wish to enable access to multiple $CVSROOT entries through the pserver. I have introduced the following line through the inetd.conf file : cvspserver stream tcp nowait root \ /home/cvs/cvsroots.shpserver The file /home/cvs/cvsroots.sh has the following entry: #!/usr/bin/ksh /home/cvs/local/bin/cvs cvs -f \ --allow-root=/home/cvsdepot --allow-root=/home/cvstest I have also made corresponding entries in the passwd files. But while trying to through WinCvs I get an error message : /home/cvstest: no such repository cvs login: authorization failed: server serverA rejected access to /home/cvstest for user userA What could be the problem ? Best Regards Srijit. = __ Do You Yahoo!? Yahoo! Health - Feel better, live better http://health.yahoo.com ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs history: warning: history line invalid
Martin d'Anjou writes: cvs history: warning: history line 51999 invalid cvs history: warning: history line 61598 invalid cvs history: warning: history line 61602 invalid [...] I do not know how any of it happened. How can I fix this problem? You can use any text editor of your choice to try to repair the damaged lines, or just delete them. You will need to make sure that no one is using CVS while you do that, though. Is your repository on a shared filesystem of some sort? If so, I strongly urge you to use client/ server CVS with the repository locally mounted on the server instead -- we've had lots of reports of that kind of corruption caused by interoperability bugs in network filesystems. If that's not the case, I'd say your system has bugs in its implementation of append-mode files. -Larry Jones Well, it's all a question of perspective. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
checking out automatic script problem.
Shalom. My CVSROOT is on UNIX, and I am using CVS also from WINDOWS I have written a simple script to run when checking out a specific module the script changes few files of the module. on UNIX it works wonderfully, but when I check out a module from windows , it claims to not find the files it supposes to change. From what I understand , the files are copied to the working directory on WINDOWS, while the script is executed in a temporary directory on UNIX, and therefore, the path to the files is wrong. Any suggestions? Thanx Ofira :-) Have a good day. Ofira Shaer ext. 4518 ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs history: warning: history line invalid
Larry Jones wrote: using CVS while you do that, though. Is your repository on a shared filesystem of some sort? Yes. We don't use client-server for now. If so, I strongly urge you to use client/ server CVS with the repository locally mounted on the server instead -- The filesystem is only running filesystem stuff, nothing else. I need to check with my network admin if we're allowed to run a CVS daemon on the file server itself. What if I picked a server closer to the fileserver instead? we've had lots of reports of that kind of corruption caused by interoperability bugs in network filesystems. Wouldn't all our files be corrupted? What makes CVS (in non client-server mode) so sensitive? If that's not the case, I'd say your system has bugs in its implementation of append-mode files. How can I identify if the problem lies with CVS or with filesystem interoperability? Thanks, Martin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs history: warning: history line invalid
At 12:54 -0400 7/24/02, Martin d'Anjou wrote: The filesystem is only running filesystem stuff, nothing else. I need to check with my network admin if we're allowed to run a CVS daemon on the file server itself. What if I picked a server closer to the fileserver instead? We have a similar setup. The file server (on a Sun) serves files using NFS and SAMBA. There is a CVS repository shared by people using Solaris, Linux, Irix, and all the various flavors of Windows. The file server does not allow any logins except for the administrator, and does not run a CVS server process. We chose a single machine (it also happens to be a Sun) under our control to use as our CVS server. Everyone has a login on that machine and uses :ext:user@cvsserver:/path/to/repository for CVSROOT. The cvsserver machine uses NFS to get to the repository. This works well. We used to let everyone access the repository using NFS until one file got corrupted. To enforce the transition to the new CVSROOT, we put a commitinfo check to prevent people from using any other CVSROOT definition. This caught some people who were infrequent users of the repository and didn't get the initial word to change their definition of CVSROOT. I suspect that even if the file server and the cvsserver machines were different (e.g., solaris and linux), that it would be safe to use this way because the CVS repository is being accessed from a single machine. Maybe someone else on the list can comment. Fred -- Fred Brehm, Sarnoff Corporation, [EMAIL PROTECTED] http://www.sarnoff.com/digital_video_informatics/vision_technology/index.asp ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
Re: cvs history: warning: history line invalid
Frederic Brehm writes: I suspect that even if the file server and the cvsserver machines were different (e.g., solaris and linux), that it would be safe to use this way because the CVS repository is being accessed from a single machine. Maybe someone else on the list can comment. It is not safe, the problems we've seen have all been interoperability bugs. Most vendors do a very good job of making sure that their NFS server software and NFS client software work together correctly, but most of them just assume their client and server software will also work correctly with other vendors' software, and that is demonstrably not the case. If you absolutely have to use an NFS-mounted repository, your best bet is to use identical platforms for the NFS client and server. Second best is to use one of the turn-key file-server platforms as the server and a popular (i.e., well tested) platform for the client. -Larry Jones I like maxims that don't encourage behavior modification. -- Calvin ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
How to diff Microsoft word file in CVS?
Hello all: I want to use CVS to manage our document(MS word format) and track it. Can anyone tele me how to diff Microsoft word file in CVS? Thank you very much. rabbit ___ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
