Author Topic: CVS problem committing DX8 branch  (Read 1740 times)

0 Members and 1 Guest are viewing this topic.

Offline RandomTiger

  • Senior Member
  • 211
CVS problem committing DX8 branch
I get this trying to commit without updating

Code: [Select]

cvs commit: Examining code/weapon
cvs commit: Examining code/windows_stub
? code/freespace2/FreeSpace.aps
? Release
? fs2_open.opt
? fs2_open.ncb
? Freespace2.plg
? Freespace2.opt
? Freespace2.ncb
cvs server: Up-to-date check failed for `Freespace2.dsp'
cvs server: Up-to-date check failed for `code/code.dsp'
cvs server: Up-to-date check failed for `code/freespace2/freespace.cpp'
cvs server: Up-to-date check failed for `code/graphics/2d.cpp'
cvs server: Up-to-date check failed for `code/graphics/grd3d.cpp'
cvs server: Up-to-date check failed for `code/graphics/grd3drender.cpp'
cvs server: Up-to-date check failed for `code/graphics/grdirectdraw.cpp'
cvs server: Up-to-date check failed for `code/menuui/mainhallmenu.cpp'
cvs [server aborted]: correct above errors first!
cvs commit: saving log message in C:\DOCUME~1\TOM~1.RAN\LOCALS~1\Temp\7

 

Offline RandomTiger

  • Senior Member
  • 211
CVS problem committing DX8 branch
Looks like the problem is that I 'need' to update. However I dont want to do this, currently searching though docs for some kind of scrub flag.

 

Offline Inquisitor

CVS problem committing DX8 branch
Won't be home till this evening, pretty sure how to fix it.
No signature.

 

Offline RandomTiger

  • Senior Member
  • 211
CVS problem committing DX8 branch
DOnt worry, this is old news. Ignore it. Everything is OK.

  

Offline penguin

  • Eudyptes codus
  • 28
  • Still alive.
CVS problem committing DX8 branch
Edit: just saw RT's post above... oh well, I'll keep this here for everyone else's CVS edification :)


Looks like a conflict -- the files you are committing have been changed by someone else.  Here's how to fix it:

1. Make sure you back up your working copies!  You don't need to do the whole directory, just the ones w/ errors.  Strictly speaking, you don't need to do this, but it's a good idea....

2. You will need to do an update.  This will merge your changes with those on the server.  You will probably see some lines like:
Code: [Select]
M filename1.xxx
C filename2.xxx
...

The 'M' lines are OK, it means your local file was modified but the one on the server was not, and you should be able to check it in OK once you fix the other files.

The 'C' lines indicate a conflict.  CVS has now merged your changes with those on the server, putting the merge on your machine.  

3. Edit the conflict file; you will see the results of the merge, like this:
Code: [Select]
<<<<<<<< filename2.xxx
  your changes are here
========
  changes from the server are here
>>>>>>>> 1.5

You will just need to go through and resolve the conflicts.  Determine which of the change sets are more appropriate to keep, and edit the file, keeping the "good" stuff and blowing away the others.  Also make sure you erase the '<<<<', '====', and '>>>>' markers.

4. Repeat for all files that had conflicts :(

5. Compile to make sure it works as expected.

6. You should now be able to do a commit.
your source code slave