Fabien Bagard writes: > > There are binaries files which are often commited on each others (Same > file, with different tags) > But some days ago, when trying to use a binary pulled out with an old > tag, this user found his binary file corrupted. > > Then he checked the freshly pulled binary with an old local copy (same > tag). Surprise (Or not) files were different ! > > Does someone have any hints on what happened ?
Normally, this happens because either the repository file or the working file isn't correctly marked as binary. Since this is an old revision, it could have been the working file that was checked in to create that revision that wasn't set correctly, or it might have been that the repository file wasn't set correctly then (even though it might be now). You can use ``cvs log'' to determine the setting on the repository file and ``cvs status'' in the affected working directory to determine the setting on the working file. -- Larry Jones Wheeee. -- Calvin _______________________________________________ Bug-cvs mailing list Bug-cvs@nongnu.org http://lists.nongnu.org/mailman/listinfo/bug-cvs
