CVS update does not mark two binary files as modified

Ok as this was very strange I just added a dummy clip to both fla files to totally be sure they were modified files and cvs update still don't mark them as modified.

If there is not a CVS command to force to mark them as modified I don't know what to do.

I just commited and I suppose those two files where not updated.

Is there any solution for next time? Or my only solution is to remove and readd them?

I hope there is another solution, rather than deleting, and adding them again.
Could Working with Binary Files within CVS be of any help for you?

I added all files without the kb argument because I thought it was added to binary files taking into account file extension. I thought I had confirmed the kb flag was present with a CVS command that showed me many information about files (its branch, its tag if present, its flags, its name, ...). Those files were working fine till that last commit. The update flag was being set properly by every cvs update.

I don't remember which command I used to see the more verbose output that showed me the binary flag if present. Maybe was some parameter to cvs update. I'll try to find that command again to check the files and if they dont have the binary flag I'll add it and check if that solves the problem.

Thanks for the howto link.

Ok I found the command:

Confirmed the kb flag is not present on .fla files. I'm going to try to add that flag with CVS admin.

The files that were added correctly with kb flag were .jpg, .mp3, .swf files.

I think it is fixed.

Thanks a lot.

I'm going to take the opotunity to ask two not very important questions:

• Every time I update a text file, for example the .module file, I edit the line
  $Id: blablablablabla Exp $
  to
  $Id$
  Is that necesary or that line would be updated no matter if I restore it to $Id$ or not?
• Is there a way to edit a commit message?

Every time I update a text file, for example the .module file, I edit the line

$Id: blablablablabla Exp $

to

$Id$

You can leave the CVS ID tag as it is, and CVS will change it automatically. So far, I have never edited the CVS tag, and I always got that correctly changed.

Is there a way to edit a commit message?

cvs commit -m "Commit message.".

I didnt understood the commit edit exactly. You mean if I go to a specific tag version or branch version I can update the commit message just doing a commit and as there are no changes on files the only change would be the commit message?

Or for example if I commit and the message has an error, and inmediatly new commit with the corrected message would update the message?

I didnt understood the commit edit exactly.

Or maybe I didn't understand what you were asking. If you meant to change a commit message (the same that appear in CVS log messages) after you already committed the code changes, then there is no way to change it.
What I reported is how to set a log message while committing the code changes.

Automatically closed -- issue fixed for 2 weeks with no activity.

I have to reopen this issue because I'm again on same problem.

Now is only one binary file that I'm sure I have modified but CVS refuse to see it so. The sticky for binary file now is not a solution because the file has it.

So, I would like to ask if someone knows what exactly CVS uses to check if a binary file is locally modified, maybe the file size?. I ask this to try to investigate why it is happening, the change is minor and it is possible the file sizes being the same because really the changes in the file are two objects that has new values on its x,y,rotation parameters, and maybe that kind of binary files (fla files) uses the exactly same num of bytes for those values and the change is not making any file size difference. I haven't confirmed same file sizes yet but I would like to know if that is a possibility.

If it is so I could try to include a dummy comment text on one frame (maybe just the next version that is going to have the file on HEAD would make the trick).

The help for the command line reports this text:

Maybe in your case, the option -f could be of any help. Just commit each binary file in a single invocation of the command, and you would get the file updated.

I am not sure if binary files should be automatically added in CVS when modified. Looking at the file Entries contained in the directory CVS of a project, I notice the following text (the file is for Nodewords):

The only data recorded for a file are the file revision, the last modification date, and the tag associated with the file.
I am not sure if that answer to your question.

Thanks KiamLaLuno again for your help.

About if binary files are automatically marked as modified I think they are, swf files work fantastic and are binary ones, every time they change they are marked as locally modified.

That data record makes me think of the last modification date as the proper data to be checked by CVS to know if a file has been changed locally. So the problematic file should have been marked as modified. Maybe the problem is the type of those binary files, they where the only ones I had to put the binary sticky myself. So probably the force is the only solution for those type of files.

I'm curious to know the CVS data for those specific files, so I'm going to have a look.

Thanks.

My fault my fault and only my stupid fault.

Many thanks to point me to the data record. That confirmed the dates where the same so pointed me to my stupid fault. Just a mistake when saving file that saved the new one in a different folder (not overriden the old one). I thought I was copying the modified file to the checkout folders but I was copying the older file that hadn't been overriden with new version.

Thanks again it is fixed and without the need of force.

Automatically closed -- issue fixed for 2 weeks with no activity.