On Fri, 2004-01-09 at 22:21, Malte S. Stretz wrote: > On Friday 09 January 2004 20:55 CET Sander Striker wrote: > > On Fri, 2004-01-09 at 21:50, Theo Van Dinter wrote: > > > On Fri, Jan 09, 2004 at 08:24:54PM +0000, Malte S. Stretz wrote: > > > > I just checked out the sources from the new repository and now all > > > > files in lib/ are read-only. Any ideas why? > > > > What do you mean? On your local disk in your working copy? > > Yes. > > > How was your umask set at the time of your checkout? > > 0022 as always. And what's really weird: The permissions are correct now!
?! > But I did not hallucinate: I noticed this when I tried to modify > SpamAssassin.pm and vim told me that I'm going to modify a read-only file. > I then manually chmod +w'd that file but had a look at the > lib/Mail/SpamAssassin/ dir and the files were definitely -r--r--r--. > And now I look again and everything is ok... I ran some 'svn stat's and 'svn > diff's in between, maybe SVN corrected the permissions itself? Very weird. SVN doesn't explicitly mess with permissions. > > NB. Subversion doesn't version permission bits, it can only set > > the execute bit when a special property is set. > > That's another thing I noticed: It seems like we lost a whole bunch of > properties. Or better: Got them back. Some days ago I corrected a whole > bunch of incorrect executable bits. That was r6088. I definitely removed > the executable bit from the one rule file and Received.pm in the libs. But > those bits are back now. Some SVN bug? r6088 touched four files, all four have their svn:executable property set, and are executable in my workingcopy. FWIW, what I did was a dump of the test repository, to save your commits there, and I loaded that data into the asf repository. If there is any data lost we have a serious problem in the dump/load code in subversion. Please let me know if there is anything out of the ordinary. > Quite confused, You are looking at trunk/ right? Sander
