Have you by any chance also installed SVNSCC (a Microsoft Common Source
Code Control interface to SVN) from www.pushok.com? If not configured
the right way, this tool can do similar things, as it lurks in the
background monitoring checks and commits and altering RO flags unless
told not to do so. Proper configuration cures this.
henning
________________________________
From: Rob Brown [mailto:rob.brown@whispertech.co.nz]
Sent: Tuesday, April 18, 2006 5:41 AM
To: users@subversion.tigris.org
Subject: Checked out files become read-only
Hi,
I sent a message on this subject about a week ago, and received no
response. I'm now completely desperate, and possibly at least half-way
insane.
My problem is that when svn performs an update or commit operation on my
working copy, it sets the read-only attribute on the controlled files.
The behaviour follows bizarre (to me) patterns, but the upshot is that
it's no use to me in its present state.
My vital statistics:
OS - Windows XP SP2, part of a company network
File system - NTFS
svn version - 1.3.1 and 1.1.4 both show the symptom
I've looked for answers in - the SVN Book, the SVN Faq, the RapidSVN and
TortoiseSVN websites, the Apache/APR website, the internet as presented
by google, etc
I've attached a batch file (called svntest.txt, to get past virus
filters) to create a repository and a trivial project, and commit a
change to that repository. Output is in svntest-output.txt, and it is
exactly what the documentation told me to expect. I can also make a
trivial change, for example, by running the following in a batch file
from within the working copy (c:\svntest):
rem Batch file to perform a trivial change
echo some text >> soft.c
svn update
svn commit -m "A change"
attrib soft.c
The output from attrib says that the file is not read-only. However, if
I perform any actions directly from the command line, the soft.c file
becomes readonly:
C:\svntest>svn update
At revision 7.
C:\svntest>attrib soft.c
A R C:\svntest\soft.c
This is the first thing I can't understand. Why the difference between a
batch file and the command line? Also (and this is *really* odd) if I
reboot, the first time I run the batch file above, the soft.c file will
be set to read-only. Subsequent runs of the batch file will not set the
read-only flag.
I have tried all of this in Linux, and the problem does not exist. I
have also done some testing on a stand-alone Win2k computer, and it
seemed to work correctly. I've also made a "post-commit.bat" file, which
clears the read-only flag on my working copy. That doesn't work
correctly, and I wouldn't like to do it anyway because it's horribly
hacky.
I'm hoping that someone here will offer guidance, even though I don't
know whether the problem lies in Subversion, or APR, or Windows XP
(possibly my IT-department-enforced permissions - I'm a "Power User",
whatever that means).
All suggestions gratefully received!
Received on Tue Apr 18 09:12:53 2006