Re: Execute bit gets hammered on checkout.

[Mark D. Baushke]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Fisher, Allen <address@hidden> writes:

> Frederic--
> 
> Thanks. It looks as though the executable bit is getting stripped off
> during check-in. 

Does the user have a CVSUMASK environment variable set? If so, is it
prohibiting the execute bits?

When you built your cvs executable, did you use an explicit
- --with-umask of a value other than the default 002 ?

> It's set correctly on the local machine, and is gone
> when it reaches the server. Could it be an issue with the client, or is
> there something on the server that I can set?

It would probably be useful to run a small test with CVS_CLIENT_LOG
environment variable set to a basename like /tmp/$USER.client and look
at the /tmp/$USER.client.in and /tmp/$USER.client.out files to see if
the umask is being properly transmitted to the server. So, create a new
file and add the execute bits to it. Then do a 'cvs add' of the new file
and a 'cvs commit' and then look at the contents of the
$CVS_CLIENT_LOG.* files.

        -- Mark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (FreeBSD)

iD8DBQFEWjAGCg7APGsDnFERAvNJAKCcgbwOnTIPSjezAhCILHcscOJyswCgnHf/
xy9Tcbd6DtzYaG95fIGAibA=
=5WHK
-----END PGP SIGNATURE-----