Commit succeeded, E000030: Can't change perms
Hello, I was adding some files to a repository and encountered error "E30: 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: E20: 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: E30: Can't change perms of file 'somefile': Read-only file system
Re: Commit succeeded, E000030: Can't change perms
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 "E30: 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: E20: 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: E30: 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
Re: Commit succeeded, E000030: Can't change perms
On 2021-05-25 08:06, Nathan Hartman wrote: On Mon, May 24, 2021 at 5:04 AM Pingu wrote: Hello, I was adding some files to a repository and encountered error "E30: 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: E20: 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: E30: Can't change perms of file 'somefile': Read-only file system During post-commit processing, Subversion ensures that the file is as it should be in the working copy [1], meaning that its contents and permissions match its properties and lock status. This includes adjusting (if necessary) line ending style, keyword translation, and read/write/execute permissions. In other words, this may alter not only the file's permissions, but also its contents. You can see other examples of this post-commit processing in action. For example, create a test repository, add and commit a text file with CRLF line endings. Then, add a svn:eol-style property of "LF" to the file and commit again. Then, without running 'svn update' or any other commands that might make changes, check the contents of the file and you'll see that its line endings have changed to LF. Hope this helps! [1] See install_committed_file() in libsvn_wc/workqueue.c. Cheers, Nathan That makes sense! I wondered why the error popped up on a text file, instead of another file. Thank you for the details and explanation. I'm glad that SVN considers the commit successful, even though it can't alter the working copy, afterwards. -Kenneth
Re: Commit succeeded, E000030: Can't change perms
On 2021-05-26 00:59, Thorsten wrote: Hello, Given That your commit succeeded, you should be good. For the future you may or may not find the "svn import" functionality helpful, That way subversion will not try to alter your existing files. However you will no longer see localy which files you already added, but you can browse the repo online. For a one time migration this should be ok. Best regards, Thorsten Goetzek Am 26/05/2021 um 09:52 schrieb Pingu: 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. Thanks for the tip, Thorsten! I hadn't tried that command. I'll try it.
