Re: [boost] [1.35.0] Release candidate 1 available

From: Beman Dawes (bdawes_at_[hidden])
Date: 2008-03-22 14:03:21

Rene Rivera wrote:
> Jens Seidel wrote:
>> Hi Beman,
>>
>> On Fri, Mar 14, 2008 at 11:16:11AM -0400, Beman Dawes wrote:
>>> Release Candidate 1 is available at http://boost.cowic.de/rc/
>> I checked RC2 (tar.bz2) and noticed that still many files have wrong
>> permissions:
>>
>> -rwxrwxrwx Administrator/None   10006 2008-02-23 19:00
>>    boost-posix-2008-03-21/libs/iostreams/doc/guide/exceptions.html
>> -rwxrwxrwx Administrator/None   10009 2008-03-21 08:31
>>    boost-posix-2008-03-21/doc/html/foreach/portability.html
>> -rwxrwxrwx Administrator/None  100117 2006-02-02 00:33
>>    boost-posix-2008-03-21/libs/iterator/doc/iterator_adaptor.pdf
>> -rwxrwxrwx Administrator/None    1001 2006-03-19 13:01
>>    boost-posix-2008-03-21/libs/test/example/cla/validation/ambiguous_access.cpp
>>
>> I told you already about this and wonder why it isn't fixed yet

Sorry, I dropped the ball on that one. The issue is now added to the 
trac 1.35.0 issues list: 
http://svn.boost.org/trac/boost/wiki/MergeOneDotThreeFiveDotZero

>> (removing the svn:executable property of Subversion should be sufficient).
>> Opening a PDF file marked as executable will probably confuse some file
>> managers as executing will fail.
>>
>> Nearly 20% of all files are affected!
>>
>> If you need a script just ask ...
> 
> OK... What does the script do? Obviously I would prefer something that 
> does the svn manipulations. I would also love it if I could run it on 
> Windows so I could more easily verify with tsvn what the changes to the 
> repo it's going to do.

There are really two issues here: (1) Clearing svn:executable in 
Subversion (not just in branches/release, I assume), and (2) preventing 
this from happening in the future.

An alternative is to not worry about Subversion, but to clear out the 
wrong permissions in the snapshot script, 
trunk/tools/release/snapshot_windows.sh and snapshot_posix.sh.

Without knowing how the svn:executable property got set in the first 
place I can't tell if this is a one time or recurring problem. Any ideas?

Thanks,

--Beman