This is plenty easy to fix, but only with shell access on the box that
hosts the repository. The following is a surprisingly clear
description of the stupidity that CVS manages to achieve with
permissions.

http://durak.org/sean/pubs/software/cvsbook/CVS-keeps-changing-file-permissions_003b-why-does-it-do-that_003f.html

Andrew

On 3/27/07, Peter Eisentraut <peter_e at gmx.net> wrote:
> Most files in the slony 1.2.9 tarball still have executable permissions.
> Is anything being done about that?
>
> --
> Peter Eisentraut
> http://developer.postgresql.org/~petere/
> _______________________________________________
> Slony1-bugs mailing list
> Slony1-bugs at lists.slony.info
> http://lists.slony.info/mailman/listinfo/slony1-bugs
>