[ 
https://issues.apache.org/jira/browse/CASSANDRA-6490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13849187#comment-13849187
 ] 

Sebb commented on CASSANDRA-6490:
---------------------------------

There is a problem with the directory protections:

drwxrwxr-x  3 eevans     eevans     6 Aug 20  2012 06x
drwxrwxr-x  3 eevans     eevans     6 Aug 20  2012 07x
drwxr-xr-x  3 slebresne  cassandra  6 May 27  2013 11x
drwxr-xr-x  3 slebresne  cassandra  6 Nov 25 08:11 12x
drwxr-xr-x  3 slebresne  cassandra  6 Nov 25 08:40 20x
drwxrwxr-x  3 apbackup   cassandra  6 Sep 10  2012 sid
drwxrwxr-x  3 eevans     eevans     6 Aug 20  2012 unstable

Only 'sid' above is correct.

The file group should be cassandra, and files should be group-writable 
otherwise only the owner can change things.
Which is awkward when the individual is temporarily unavailable.

However please note that Infra are moving towards all projects using svnpubsub 
[1] for releases - which avoids all such issues.
I suggest you file an Infra request now so you are ready for the next release.

[1] http://www.apache.org/dev/release-publishing.html#distribution_dist

> Please delete old releases from mirroring system
> ------------------------------------------------
>
>                 Key: CASSANDRA-6490
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6490
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: http://www.apache.org/dist/cassandra/
>            Reporter: Sebb
>            Assignee: Sylvain Lebresne
>
> To reduce the load on the ASF mirrors, projects are required to delete old 
> releases [1]
> Please can you remove all non-current releases?
> Thanks!
> [Note that older releases are always available from the ASF archive server]
> Any links to older releases on download pages should first be adjusted to 
> point to the archive server.
> [1] http://www.apache.org/dev/release.html#when-to-archive



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)

Reply via email to