the motherboard of a dedicated server I'm renting since five years went south and the motherboard got replaced by a new one.  The very old (Debian) distro couldn't keep up with all the new hardware on the motherboard so I decided to re-install a new distro (Debian Wheezy) from scratch (even doing an upgrade was kinda problematic seen that the old Debian wouldn't recognize the ethernet chipset of the new motherboard as far as I can tell, so I went for a re-install from scratch).I re-installed SVN and did get all the repositories by doing a:tar -xzf repoBackups.tgzAnd it works.The problem is that although, say, Eclipse recognizes the SVN repositories, it wants to commit every single file, even though they are identical.Could this be related to timestamps on the files?  Either way, do you have an idea as to what caused this and how to solve the issue?I could simply ask everybody to re-commit every single file of every project and I think everything would be ok but some of these projects are quite big and it would be a bit painful for the developers. As a bonus (and less important) question: would another VCS like Git or Mercurial not suffer from this problem?
SVN wants to commit everything after server re-install
linux;subversion;timestamps