Answer the question
In order to leave comments, you need to log in
cvs - wrong versions
In CVS, as many people know, in each directory there is a folder where the system files of this system are located. The problem is that if you look at the versions on the server where we have a deployed repository, and just updated on the local machine, the server one becomes outdated, and as far as I understand, exactly one "step" back.
For example, if the test.xml file of version 1.3 on the server has version 1.2 according to the entry in this file, then exactly the same, made a second ago, on the local machine has the correct entry - 1.3. What could be the problem?
Example entry with <folder_name>/CVS/Entries :
Local:
/example.php/1.26/Fri Aug 5 13:38:38 2011//
Server:
/example.php/1.25/Thu Aug 4 14:12:23 2011/ /
Answer the question
In order to leave comments, you need to log in
One possible explanation:
The fact that you have a CVS directory in somefolder on your server suggests that this is also a checkout copy from the repository, which, apparently, is periodically updated by cron (for example, once an hour). Immediately after the commit, the repository itself will have a new version (file example.php ,v ), but the deployed tree on the server has not yet been updated - you have to wait for the next “sync”.
Usually in such cases (if you do not want to wait until the cron pulls the update script), it (the script) should be run manually.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question