Hi Anton, If you're accessing your repository over svn+ssh, this could possibly be related to the problems with SVN 1.6 on Mac OS X with zombie ssh processes. If quitting and relaunching Versions fixes the remote changes counter, that could actually be the cause.
Refreshing the change counters of svn+ssh working copies using SVN 1.6.1 can leave zombie processes behind. When those keep adding up, at some point your machine won't be able spawn *any* more new processes until you quit Versions, which will also prevents any new refreshes on svn+ssh working copies from taking place. If this is actually what's going on here, launching any other process before you quit Versions (which also takes out all of the stray ssh processes) will probably also not do anything. If the quit/relaunch thing doesn't take care of the 27 changes, could you maybe take a look whether you get the same results when you use Versions 1.0.4b with SVN 1.5.6? Thanks! - Dirk On Apr 28, 9:22 pm, Anton <r...@acm.org> wrote: > I've got one workspace which shows up with 1.0.4b as having 27 remote > differences. However, using Update in Versions doesn't do anything, > and 'svn update' doesn't do anything. I deduce that there really > aren't any differences. Is there some way I can find out what's > causing this? > > There's nothing particularly unusual about my configuration, so far as > I know. We do use externals, and there are 11 external references > from this workspace. > > I didn't see this behaviour with 1.0.3 as far as I recall. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Versions" group. To post to this group, send email to versions@googlegroups.com To unsubscribe from this group, send email to versions+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/versions?hl=en -~----------~----~----~----~------~----~------~--~---
