On Thu, Feb 23, 2012 at 9:57 AM, Gary Weinfurther <gweinfurt...@es3.net>wrote:
> I have a team of about seven people, both on Macs and PCs. Within the > last couple of weeks, we have been experiencing frequent occurrences of > lost changes. Someone will commit a change and later we discover that the > change has been reverted. Everyone claims that they are updating before > they work on files. Even if this was not always true, the SVN clients > should catch commits that were not on the most recent files, correct? > > > Your observation sounds right. Sounds like you really need to examine the change history. For example, an automated procedure that is copying *back* old files and committing them on top of old changes would cause just this sort of problem. Also, if you have multiple Subversion servers in a multi-hosted proxy or svnsync based setup, or you're using DNS to point to a master and a slave server and the slave allows writes, you're ripe for "split-brain" problems. It does sound like a PEBKAC, though. (Problem Exists Between Keyboard And Chair.) For example, if people are working in branches and not merging changes carefully before committing to trunk, that could also cause issues. And don't get me *going* on what clever people can do to git2svn gateways. > Server is VisualSVN 2.5.3. > > > This is where I'd start looking. In particular, setting up a pre-commit script to log or email a log of changes so that you have a transcript of operations would be very helpful to debugging. ** > PC Clients:**** > > ** ** > > TortoiseSVN 1.7.5, Build 22551 - 64 Bit**** > > ** ** > > Mc Clients:**** > > ** ** > > SmartSVN 6.6.11**** > > ** ** > > SmartSVN Early Access 7EA4**** > > ** ** > > Subversion Client Adapter for Eclipse 1.6.12**** > > Subversion JavaHL 1.6.17**** > > SVN Team Provider Core 1.6.18**** > > ** ** > > Versions 1.1.10 Build 1029**** > > ** ** > > ** ** > > I am not subscribed. Please CC me on replies.**** > > ** ** > > Gary**** >
