Technological Wanderings - svn http://www.technologicalwanderings.co.uk/taxonomy/term/70 en svn: cannot rename file 'entries' http://www.technologicalwanderings.co.uk/node/36 <div class="field field-name-taxonomy-vocabulary-1 field-type-taxonomy-term-reference field-label-above"><div class="field-label">Keywords:&nbsp;</div><div class="field-items"><div class="field-item even"><a href="/taxonomy/term/70">svn</a></div><div class="field-item odd"><a href="/taxonomy/term/71">subclipse</a></div></div></div><div class="field field-name-body field-type-text-with-summary field-label-hidden"><div class="field-items"><div class="field-item even"><p>Using an SVN working directory on a Samba share from a Mac? With Subclipse or similar? You may have seen the following message as it bombs during checkout:</p> <p>svn: cannot rename file 'entries'</p> <p>I did and Google says others have for the last three years at least.</p> <p>Examining the files in the .svn directories, I find that the root 'entries' file is created with permissions of -r--r--r--, so naturally a file can't be renamed over it as that requires write permissions.</p> <p>After a bit of hacking I came up with the following solution, which may or may not be suitable for others. Use with care.</p> <p>Create a share in Samba specifically for your working directories if you haven't already.</p> <p>Add these lines to the share definition:<br /> force create mode = 0640<br /> force security mode = 0640</p> <p>or, if you want world readability (I don't, hence 640..):</p> <p> force create mode = 0644<br /> force security mode = 0644</p> <p>Now everything you write to that share will be forced as writable (at least -rw-r-----) by your user account. This fixes the SVN bug.</p> <p>I say 'SVN bug', but it could be Subclipse, the Java SVN library, Samba,... I don't know.</p> </div></div></div> Wed, 18 Jun 2008 10:45:47 +0000 techuser 36 at http://www.technologicalwanderings.co.uk http://www.technologicalwanderings.co.uk/node/36#comments