"Tony Butt" <tony.b...@cea.com.au> writes: > On Tue, 2011-11-08 at 13:50 +0200, Daniel Shahaf wrote: >> Tony Butt wrote on Tue, Nov 08, 2011 at 15:07:55 +1100: >> > 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? > The new behaviour is slightly different, and slightly incompatible in > our corner case. It was more surprising than anything else, and I wanted > to check that I didn't need to tweak the repository config in some way > to allow for this - possibly some subtlety with umasks that I was not > aware of.
The fact that the files are read-only should have no effect on Subversion operations. It should be possible to use svn+ssh and http access simulataneously provided the repository Unix permissions are correct: http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.serverconfig.multimethod -- Philip
