I am running subversion v1.6.7. on Windows.
I have had a problem committing a file, that does not report an error. If I look at the log message for the newly committed file the history appears all ok at the location where the commit was carried out. However, if I update from the SVN repository to a new location then the commit did not stick and the previous version of the file has been lost as well. This is verified by the repo-browser results.
So, to demonstrate the problem by example:
Log Messages for a file are:
Revision Actions
2 Added
1 Modified
After committing a change to the file, everything seems normal. I receive no errors and the log message for the file shows the new version 3 as expected.
Revision Actions
3 Modified
2 Added
1 Modified
However, if I update the file in a new location I get version 1, and looking at the change log I see: (this is verified by the repo browser also).
Revision Actions
1 Modified
So the commit of a file has failed and the previous revision 2 of the file has disappeared also, unless I look in the original build directory. It is interesting to note that revision 2 of the file had an associated change type of Added as opposed to Modified, and am curious as to whether this fact could be associated with the source of the problem.
I have tried a Clean Up on the parent directory but this makes no difference.
I have tried switching off Log Caching temporarily, and updating the new location but this does not fix the problem either.
I could just re-commit the changes by adding a white space to the file and therefore forcing a new change again, but am concerned that this is merely papering over the cracks of a problem that is most likely going to happen again.
Information from anyone who has any insights, or experience of this problem would be hugely appreciated.
I have had a problem committing a file, that does not report an error. If I look at the log message for the newly committed file the history appears all ok at the location where the commit was carried out. However, if I update from the SVN repository to a new location then the commit did not stick and the previous version of the file has been lost as well. This is verified by the repo-browser results.
So, to demonstrate the problem by example:
Log Messages for a file are:
Revision Actions
2 Added
1 Modified
After committing a change to the file, everything seems normal. I receive no errors and the log message for the file shows the new version 3 as expected.
Revision Actions
3 Modified
2 Added
1 Modified
However, if I update the file in a new location I get version 1, and looking at the change log I see: (this is verified by the repo browser also).
Revision Actions
1 Modified
So the commit of a file has failed and the previous revision 2 of the file has disappeared also, unless I look in the original build directory. It is interesting to note that revision 2 of the file had an associated change type of Added as opposed to Modified, and am curious as to whether this fact could be associated with the source of the problem.
I have tried a Clean Up on the parent directory but this makes no difference.
I have tried switching off Log Caching temporarily, and updating the new location but this does not fix the problem either.
I could just re-commit the changes by adding a white space to the file and therefore forcing a new change again, but am concerned that this is merely papering over the cracks of a problem that is most likely going to happen again.
Information from anyone who has any insights, or experience of this problem would be hugely appreciated.