You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by "Malte S. Stretz" <ms...@gmx.net> on 2004/01/09 21:24:54 UTC

Read-only files in SVN?

I just checked out the sources from the new repository and now all files in 
lib/ are read-only. Any ideas why?

Cheers,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Re: Read-only files in SVN?

Posted by "Malte S. Stretz" <ms...@gmx.net>.
On Saturday 10 January 2004 22:36 CET Sander Striker wrote:
> On Fri, 2004-01-09 at 22:21, Malte S. Stretz wrote:
> > 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.

I can't reproduce it. So I've got to file this under "weird stuff". Maybe my 
umask was really f***ed up. I don't know how this could have happened, but 
who knows?

> > 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.

I also removed the executable bits from rules/20_uri_tests.cf and 
lib/Mail/SpamAssassin/Received.pm (I corrected those again lately). And as 
I just typed 'svn commit' at root level, those changes should have gone in.

> 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.

I didn't see any other weird behaviour till now. Btw, my Subversion is
	svn, version 0.35.1 (r8050)
	   compiled Dec 28 2003, 15:42:23

> > Quite confused,
>
> You are looking at trunk/ right?

Yes.

Cheers,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Re: Read-only files in SVN?

Posted by Sander Striker <st...@apache.org>.
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

Re: Read-only files in SVN?

Posted by "Malte S. Stretz" <ms...@gmx.net>.
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.

> 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?

Quite confused,
Malte

-- 
[SGT] Simon G. Tatham: "How to Report Bugs Effectively"
      <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>
[ESR] Eric S. Raymond: "How To Ask Questions The Smart Way"
      <http://www.catb.org/~esr/faqs/smart-questions.html>

Re: Read-only files in SVN?

Posted by Theo Van Dinter <fe...@kluge.net>.
On Fri, Jan 09, 2004 at 09:55:30PM +0100, Sander Striker wrote:
> It's the same account.

Oh.  when putting in requests, there was a "is this for test or the real
repo" question which is why I thought they were separate. :|

-- 
Randomly Generated Tagline:
There was a young lady named Bright
 Who could travel much faster than light.
         She took off one day,
         In a relative way,
 And returned on the previous night.

Re: Read-only files in SVN?

Posted by Sander Striker <st...@apache.org>.
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?
How was your umask set at the time of your checkout?

NB.  Subversion doesn't version permission bits, it can only set
      the execute bit when a special property is set.

> Hrm.  Perhaps your test repo account didn't get copied over to the
> real repo?  :(  Sander?

It's the same account.

Sander

Re: Read-only files in SVN?

Posted by Theo Van Dinter <fe...@kluge.net>.
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?

Hrm.  Perhaps your test repo account didn't get copied over to the
real repo?  :(  Sander?

-- 
Randomly Generated Tagline:
"When it is not necessary to make a decision, it is necessary not to make a
 decision."               - From www.slashdot.org