Hi Kevin, Within. Dan
On 28 October 2010 07:57, Kevin Meyer <[email protected]> wrote: > > On Thu, October 28, 2010 00:41, Dan Haywood wrote: > > It doesn't look like you've done a full svn update? That class got moved > > to a different package, and the other post with a build error looked like > > the pom.XML for viewer/junit hadn't been updated. > > > > That's a question - My first svn update got interrupted (link forcibly > closed by host). The second update fetched more files. The third says > update complete. > > How error prone is svn when links are forcibly closed? I thought it was > supposed to be atomic. > Commits are atomic, but doing an svn update isn't, as you've seen. I've also noticed the ASF repo sometimes terminating an svn update, so wrote a little script svnup.sh (in isis/trunk) which continually performs an svn update until it fully succeeds. This runs fine on Windows under Cygwin, or under *nix, of course. > > If I do have an unstable svn state, what can repair it? Not sure what you mean by "unstable svn state"; an interrupted svn update is not serious, just try again. > svn clean doesn't > do anything. > The command is "svn cleanup", and only relates to cleaning up locks when an svn commit fails for some reason (typically if you kill the svn process while it is still working). > I'm mostly using the TortoiseSVN extensions (context menus in explorer), > but I believe those are wrappers to the svn commandline apps? > I use TSVN also, but it's also worth installing the command line 'svn' and cygwin. HTH Dan > > > Regards, > Kevin > > >
