A week ago, I migrated our source control files from PVCS to Subversion (using the Ankh plugin for vs2005). I think its a good move, but not everyone in the team shares this opinion (although I have to say the majority of the team seem to agree with me).
We have a meeting this afternoon to decide if this is going to be a permanent switch.
Some unexpected things appear to have happened. It appears that a team member was able to update and check in an old revision of a file. I can see by looking at the history of the file that changes were made by team member A, then by member B. When member B checked in her changes, member A's changes were reverted. If we have any chance of retaining subversion I will need to find an answer as to why this happened. I've checked the event log on the server and have found some entries relating to the file.
Code:Path '/trunk/DS2BOOKING/dsBookingQueries.vb' is already locked by user 'frankh' in filesystem 'C:/Base_SVN/automate/db' [423, #160035] [client 160.10.1.178]Code:Failed to create new lock. [423, #160035] [client 160.10.1.178]Would it be possible that the team member was able to update an old version after stealing the lock? Is there any way to verify this?Code:Lock failed: newer version of '/trunk/DS2BOOKING/dsBookingQueries.vb' exists [500, #160042] [client 160.10.1.178]
Many thanks for your time![]()


Reply With Quote