On 2 May 2010 11:53, Peter Pfannenschmid <lists_at_binarus.de> wrote:
> On 01.05.2010 23:38, Simon Large wrote:
>> On 1 May 2010 15:31, Peter Pfannenschmid <lists_at_binarus.de> wrote:
>>> I think I have experienced a bug in TortoiseSVN, but I am not absolutely
>>> sure about it, so I am looking forward to comments.
>>> I am using the latest version of TortoiseSVN (TortoiseSVN 1.6.8, Build
>>> 19260 - 64 Bit , 2010/04/16 20:20:11) under Windows Vista Ultimate x64.
>>> I am using a linux system with samba as file server.
>>> Working on the windows system, I have checked out a project (in this
>>> case, a small website) onto a samba share. Using Windows explorer, I
>>> then have created a new subdirectory in this working copy and added some
>>> files to the new subdirectory.
>>> Then I have used TortoiseSVN -> Add to add the newly created
>>> subdirectory to the project and to put it under version control,
>>> Then I tried to commit, but there was the error message that I have
>> Try this FAQ entry
> thank you very much for the hint. I wonder why I didn't see it since I
> had taken a look into the FAQ. Your tip saved a lot of time and frustration.
> Applying the first solution mentioned in the FAQ (delete readonly = yes)
> has solved the problem for me. Just some quick notes:
> - My samba version is 3.2.5, so, according to the FAQ, the main problem
> should have been fixed. But my version seems to be, guess what, the last
> one in which the additional supplementary problem mentioned in the FAQ
> hasn't been fixed. Since my samba is Debian Lenny stock, I think many
> people will be affected by this.
> - I am still wondering what's going on there because when I create a
> file in the respective share using windows explorer (right mouse click
> -> new file), the attributes are set in the right way. So TortoiseSVN
> seems to set the attributes to readonly by intent when creating files.
> I have understood that it is a samba / linux thing if read-only files
> could be deleted. But before being readonly, they must be created
> readonly or set to readonly. Is this still a samba bug, or is is done
> intentionally? If the latter is the case, what's the reason for this? Is
> read-only and locking used to make transaction security possible?
It is all done inside the subversion libraries, so you would have to
ask on the subversion users list instead.
: oo // \\ "De Chelonian Mobile"
: (_,\/ \_/ \ TortoiseSVN
: \ \_/_\_/> The coolest Interface to (Sub)Version Control
: /_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-05-02 15:30:16 CEST