On 24 February 2015 at 17:05, Phil Steitz <phil.ste...@gmail.com> wrote:
> On 2/23/15 1:21 AM, Mark Thomas wrote:
>> On 22/02/2015 22:27, Thomas Neidhart wrote:
>>> On 02/22/2015 08:18 PM, Mark Thomas wrote:
>>>> On 22/02/2015 16:07, Karl Heinz Marbaise wrote:
>>>>> Hi,
>>>>>
>>>>> unfortunately you have to ...I'm doing that at the moment as well for
>>>>> Maven site...
>>>>>
>>>>> already filed in an issue...
>>>>>
>>>>> https://issues.apache.org/jira/browse/INFRA-9175
>>>> Commons folks,
>>>>
>>>> The issue above does not affect us. We do not use the CMS. We simply
>>>> need to fix the execute property on our CGI scipts and all will be
>>>> fixed. (I had to do the same for Tomcat a few days ago and setting the
>>>> svn property fixed it immediately.)
>>> I have fixed the execute property on the published sites already a few
>>> hours ago, and it seemed to work.
>>>
>>> Did you also have to change the property for the files in the source
>>> repository to prevent that the property is reset when publishing a new
>>> site build?
>> Tomcat uses a different build process for its site than Commons. I set
>> the execute property in the source and the build output just to be sure
>> but I suspect that setting it in the build output is sufficient unless
>> the build process uses svn rm / svn cp with the CGI scripts.
>
> I just used site-deploy to update the DBCP site and the props on the
> download cgi survived the update.

That's very useful to know.

Next time someone does a manual checkin it would be useful to know if
the props are also preserved - and what commands were used.

Note: the following command can be used on people/minotaur to check
the Commons CGI scripts:

find /www/commons.apache.org -name "*.cgi" ! -perm -111 -ls

> Phil
>>
>> Mark
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Reply via email to