[SciPy-dev] CVS problem
eric at scipy.org
Thu Feb 14 01:10:42 CST 2002
I fixed the files in question.
I thought we fixed this earlier globally, but apparently not. Any Unix gurus
that know what the magic incantation needed on /home/cvsroot/world/scipy to
force all created files in scipy or one of its sub-directories to have users as
----- Original Message -----
From: "Pearu Peterson" <pearu at cens.ioc.ee>
To: <eric at scipy.org>
Cc: <travis at scipy.org>
Sent: Thursday, February 14, 2002 3:03 AM
Subject: Re: [SciPy-dev] CVS problem
> On Thu, 14 Feb 2002, Heiko Henkelmann wrote:
> > Hello there,
> > thank you for all of your support on fixing my build problems. I've been
> > experimenting a bit and found out that also the order of the libraries has a
> > big impact.
> > Anyway, I tried to update my sandbox and got the following message:
> > cvs -z7 update -P -d (in directory C:\home\henkelma\projects\python\scipy\)
> > cvs server: Updating special/mach
> > cvs server: failed to create lock directory in repository
> > `/home/cvsroot/world/scipy/special/mach': Permission denied
> > cvs server: failed to obtain dir lock in repository
> > `/home/cvsroot/world/scipy/special/mach'
> > cvs [server aborted]: read lock failed - giving up
> > *****CVS exited normally with code 1*****
> > Any idea what's going on there?
> May be I have. It appears that the group id of special/mach is 'pearu' but
> it should be 'users'. The cause of this problem is that the parent
> directory 'special' has wrong gid permsissions:
> drwxrwxr-x 9 travo users 4096 Feb 14 01:36 special
> \_ this should be 's'
> that results wrong GIDs for subdirectories. The same problem seems to be
> also in order places.
> _All_ files in CVS must have GID of 'users' and _all_ directories in CVS
> must have 'set group ID on execution' set on.
> Can you fix it?
More information about the Scipy-dev