> we have just upgraded Subversion on the openEHR server to 1.4 from 1.2.1, a > version that caused occasional repository corruption in the past. One small > glitch occurred that lasted about 1 hour, but after that I believe you > should not see anything different. If anyone experiences any problems, make > a short post to this list, and we will address it as quickly as possible.
Is it worth mentioning the working copy client update in 1.4? http://subversion.tigris.org/svn_1.4_releasenotes.html In particular, here's the relevant part: "Working Copy and Repository Format Changes Due to certain improvements and bugfixes made to the working copy library, the version number of the working copy format has been incremented. This means that Subversion clients earlier than 1.4 will not be able to work with working copies produced by Subversion 1.4. Similarly, the repository format has changed as well, meaning that pre-1.4 Subversion tools that normally access a repository directly (e.g. svnserve, mod_dav_svn, svnadmin) won't be able to read a repository originally created by Subversion 1.4. WARNING: if a Subversion 1.4 client encounters a pre-1.4 working copy, it will automatically upgrade the working copy format as soon as it touches it, making it unreadable by older Subversion clients. If you are using several versions of Subversion on your machine, you need to be careful about which version you use in which working copy, to avoid accidentally upgrading the working copy format. This "auto upgrade" feature, however, does not occur with the new repository format." _______________________________________________ openEHR-technical mailing list openEHR-technical at openehr.org http://www.chime.ucl.ac.uk/mailman/listinfo/openehr-technical
