www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "#asfinfra IRC Bot (JIRA)" <j...@apache.org>
Subject [jira] Commented: (INFRA-2189) Please add setgid permission on /www/maven.apache.org
Date Wed, 16 Sep 2009 00:10:57 GMT

    [ https://issues.apache.org/jira/browse/INFRA-2189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12755810#action_12755810

#asfinfra IRC Bot commented on INFRA-2189:

<brettporter> Tony has said this should be fixed now

> Please add setgid permission on /www/maven.apache.org
> -----------------------------------------------------
>                 Key: INFRA-2189
>                 URL: https://issues.apache.org/jira/browse/INFRA-2189
>             Project: Infrastructure
>          Issue Type: Wish
>      Security Level: public(Regular issues) 
>          Components: Unix Groups
>            Reporter: Benjamin Bentmann
> After deploying the Maven website via {{mvn site-deploy}} to p.a.o we noticed that the
*group* of the uploaded files gets set to the user performing the upload, see for instance
the path {{/www/maven.apache.org/shared/maven-common-artifact-filters-1.2}}. I'm not aware
of a related change in our tooling and from some discussion on the Maven dev list I got the
impression that the setgid flag on the {{/www/maven.apache.org}} directory should provide
the desired the effect, namely that newly created files automatically belong to the group
"maven". The content in this directory is meant to be updated by all our committers, having
the default group ownership for files being the user's primary group doesn't fit well in this

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message