On 2021-05-25 00:19, Thorsten wrote:
Hello,
My guess would be that subversion handles the presence and absence of
the the executable bit, so it tries sets the permissions accordingly,
maybe even if they are already correct.
Adding files from a readonly filesystem to a working copy will
probably give you inherently "weird" results, since you cant really
work with these files?
Best regards,
Thorsten
Am 24/05/2021 um 03:32 schrieb Pingu:
Hello,
I was adding some files to a repository and encountered error
"E000030: Can't change perms". The commit was successful but I don't
understand the error.
The files I added were from a read-only source, so I understand the
nature of the error. What I don't understand is, why is SVN trying to
change permissions?
I assume this doesn't affect the commit but I would like to understand.
-Kenneth
Example of error:
svn: E200000: Commit succeeded, but other errors follow:
svn: E155009: Error bumping revisions post-commit (details follow):
svn: E155009: Failed to run the WC DB work queue associated with
'somerepository', work item 17 (file-commit 12 somefile)
svn: E000030: Can't change perms of file 'somefile': Read-only file
system
Thanks, Thorsten. It isn't a common scenario but I'm moving data into a
new svn repo from another system. I mount the paths as r/o to avoid
accidentally altering anything. Once it's there, people will get their
own working copies with normal, r/w permissions.
-Kenneth
