On Thursday, October 3, 2002, at 01:23 AM, Frederic Brehm wrote:
> At 06:04 AM 10/2/2002, Ken Williams wrote: >> Original problem: I have a binary file that I'd like to store >> in CVS. It's a file used on Mac OS X, and needs to have >> type/creator codes set properly in the filesystem. These >> codes don't survive a pass through the CVS repository (they >> are empty when the file is checked out). > > Use your build system (make?) to fix the type/creator codes. I'm not using a build system. I'm just sharing project data. This file is a database that the people working on this project need to access. We each update it often, potentially, so we use 'cvs watch on' and 'cvs edit' to manage concurrency. In this way CVS is a good tool for sharing it, *except* for the fact that the file breaks every time we do updates. >> Second problem: now my CVSROOT/cvswrappers file is unusable >> because of the above error, and I can't commit changes in >> order to fix it - because of the same error. How can I fix it >> if I can't commit changes? > > When something like this happens to me, I resort to brute force > (a.k.a. CVS voodoo). Replace the file > $CVSROOT/CVSROOT/cvswrappers with the fixed version. Then > commit your changes. You'll need direct access to the > repository files to do this. Darn, I suspected I might have to do this. If I had the project on Sourceforge or someplace I didn't have direct access to the repository, I guess I'd be screwed. Anyway, I'll give it a shot. -Ken _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
