I am sending this on to the dev list, and filing a bug as well.
After about 3 days of hacking on this (I'm stubborn) I finally came up
with a repeatable testcase.
I am seeing a situation where svn switch is erroring out with "unable to
set access time" in a multi-user working copy. The use-commit-times
option is set in the config.
svn propset needs-lock
switch to trunk
make same edit
svn sw common working copy to branch
*die* (see below for err message)
I think what happens is that the contents of a file don't change, but
the commit times are different. Since there is no diff the re-ownership
is skipped but the set atime fires on files that are read-only, owned by
Clearly re-ownership needs to happen for both file update and atime
update as well.
I've attached a script that can demonstrate the issue. Just make
./config dir and copy in the config attached and run "test <user>" with
a different username that has write permissions.
Could someone shed a little light on what might be happening here:
% svn cleanup path
svn: In directory 'path'
svn: Error processing command 'set-timestamp' in 'path'
svn: Can't set access time of 'path/file': Operation not permitted
This is a shared working copy (I know... I know...) but this is the
first time I've run into this issue. Permissions, gids, etc. look ok.
I first saw it when trying to do a switch command:
% svn switch -r HEAD svn+ssh://machine/tag_path/path path
Problem running log: In directory 'path': Error processing command
'set-timestamp' in 'path': Can't set access time of 'path/file':
Operation not permitted
path/file does have needs-lock and is currently unlocked (read-only).
Erik Huelsmann wrote:
"Does your filesystem support setting the atime attribute by the user
your svn client is running? Because that's what the client is
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Tue Oct 16 21:48:15 2007
- application/octet-stream attachment: test
- application/octet-stream attachment: config