Hi, got what I am pretty sure is a bug here, about to file a bug report
unless you folks have any comments.
Steps to reproduce:
I am using a 1.5 client, running on windows. (I used TortoiseSVN, any of the
I am using a 1.5 httpd host, running on Linux.
set up a working copy on a samba share. a single empty directory is
Add a empty .txt file to the working copy and commit it. (this will work)
Add a property to the txt file. Any property is sufficient.
Attempt to commit the property.
Commit succeeded, but other errors follow:
Error bumping revisions post-commit (details follow):
In directory 'J:\test'
Error processing command 'committed' in 'J:\test'
Can't move 'J:\test\.svn\props\foo.txt.svn-work' to
'J:\test\.svn\prop-base\foo.txt.svn-base': Access is denied.
Errors do not occur when committing text changes to WC on local hard drive
using a 1.5 client.
Errors do not occur when committing property changes to WC on local hard
drive using a 1.5 client.
Errors do not occur when committing text changes to WC on samba share using
a 1.5 client.
Errors DO occur when committing property changes to WC on samba share using
a 1.5 client.
Errors do not occur in any circumstances when commiting using a 1.4-based
client (still talking to a 1.5 server)
Looks like the post-commit updates inside the .svn server fail *only* when
committing property changes on a WC hosted on a samba share. svn-base files
in that folder, along with entries, format, etc, are all created with write
permissions actively removed. SVN seems to happily work on those files,
presumably having adjusted the permissions, written, and then returned
permissions. However, when it tries to do the same for props/foo.svn-work
files, it seems to fail to do that (but only when the files are on a samba
share), and gets access denied because it's trying to work on a read only
file. This seems to be a new behavior introduced in the 1.5 code revisions.
Let me know how I shoudl proceed.
--Jason C. Wenger
Received on 2008-09-24 17:15:02 CEST