Tony Butt wrote on Tue, Nov 08, 2011 at 15:07:55 +1100: > Hi all, > > We have recently upgraded our subversion servers from 1.6.17 to 1.7.1, > and as I usually do when making the 'semi-major' upgrade, dumped and > reloaded the repository. >
1.6 and 1.7 use the same backend format. dump/load gains nothing. And the release notes say that... > Here I noticed 2 things: > 1) the individual revs and revprops files are now read-only, previously > they were read/write for group and owner. > 2) the svn+ssh committed files were owned by the committing user (myself > in the test case) > > I tried to edit the log message of a commit made with svn+ssh://, using > http:// access, and failed. Now the strange thing, after changing a > different commit message for a test (using http:// access only, > successsfully), drafting this email, and re-checking the revprops file > in question, it was now owned by www-data - the apache user. > We make rev files read only intentionally. I don't remember offhand how revprop files would be affected, but in any case those are never changed either --- we only ever rename(2) new versions on top of old ones. And, anyway, I really don't understand your bottom line. Are you saying the new behaviour is non backwards compatible? That it should be changed? Or just that it's surprising? > In short, this is unexpected behaviour for me, but not exactly broken. > > Tony Butt > CEA Technologies > Canberra Next time can you try to be more concise, rather than bury your question somewhere in the middle. Thanks.