[
https://issues.apache.org/jira/browse/SVN-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-1509:
-----------------------------
Fix Version/s: (was: 1.1-consider)
1.0.2
> unable to share working copy.
> -----------------------------
>
> Key: SVN-1509
> URL: https://issues.apache.org/jira/browse/SVN-1509
> Project: Subversion
> Issue Type: Bug
> Components: unknown
> Affects Versions: all
> Environment: NetBSD
> Reporter: Subversion Importer
> Priority: Critical
> Fix For: 1.0.2
>
> Attachments: 1_1509.patch
>
>
> {noformat:nopanel=true}
> It is not possible to have more than one person using the same checked
> out subversion directory tree even if the umask is set so all created
> files and directories are writable by the group and all group
> ownership and permissions are set appropriately.
> It appears that subversion attempts to set the permissions on the
> entries file even when it already has access to it. Even if it
> doesn't have write access it should still be able to use and modify it
> since the .svn directory has group write access and it could rename
> and recreate the entries file. There error I get when I, for example,
> try to "svn up" is:
> svn: Operation not permitted
> svn: svn_io_set_file_read_write: failed to set file '.svn/entries'
> read-write
> The only way to work around this is to have someone log in as root and
> change the owner to the user actually trying to run a subversion command.
> This is using version 0.28.2 (r6946)
> {noformat}
> Original issue reported by *erh*
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
