Knut Arne Bjørndal <[EMAIL PROTECTED]> writes: > On Sun, Oct 26, 2008 at 02:08:51PM -0400, Matthias Julius wrote: >> Knut Arne Bjørndal <[EMAIL PROTECTED]> writes: >> >> > I've recently seen some old bugs rear their heads long after they were >> > fixed and the version date thing updated, so I think there are some >> > ways in which clients can avoid updating. >> >> What do you think those ways could be? >> >> I would think svn is doing a pretty good job synchronising with the >> repository. I don't think it is likely that svn is skipping some >> files. >> >> What is much more likely is that users are tampering with either >> version.txt or some source files. In the first case the client might >> never update itself and in the latter svn will try to keep the local >> edits. Svn will only fail if there is a conflict it can not resolve. > > I think it's much more likely the update mechanism isn't working than > that users are sabotaging it. Adding --subversion /bin/true to the > client command line makes it not mess up my checkout when developing.
I didn't mean that people are sabotaging their client installation, but people might play with the code a little bit to work around bugs or whatever. We had reports from people reporting about perl complaining about syntax errors resulting form the > or < inserted by svn on merge conflicts. I don't actually know what happens if svn fails (e.g. due to network problems) during auto-update. Maybe this can cause those problems. Matthias _______________________________________________ Tilesathome mailing list [email protected] http://lists.openstreetmap.org/listinfo/tilesathome
