#117 conflict:on update with gid-bit set on cvs directory

[Sven Hergenhahn]

Hi All,

problem is that on our CVS tree, the GUID bit for
directories is set and changes all file ownerships to
user cvs.

When adding a new file and then updating it, the
following happens:
----------------------------------------------------------------------------------
Changing home directory to /home/myuid
Command add shellscrips
[:pserver:myuid@unixcvs.domain.com:/home/cvs]
Opening connection
Connection opened
Local path is /home/myuid/develop/Devel_Files
Directory /home/cvs/Devel_Files/shellscrips added to
the repository
Closing connection
Command add -kkv stress_proxy.sh
[:pserver:myuid@unixcvs.domain.com:/home/cvs]
Opening connection
Connection opened
Local path is /home/myuid/Devel_Files/shellscrips
cvs add: scheduling file `stress_proxy.sh' for addition
cvs add: use `cvs commit' to add this file permanently
Closing connection
Command commit -m "no message" stress_proxy.sh
[:pserver:myuid@unixcvs.domain.com:/home/cvs]
Opening connection
Connection opened
Local path is /home/myuid/Devel_Files/shellscrips
/home/cvs/Devel_Files/shellscrips/stress_proxy.sh,v
<-- stress_proxy.sh
initial revision: 1.1
Closing connection
Command update -P -A stress_proxy.sh
[:pserver:myuid@unixcvs.domain.com:/home/cvs]
Opening connection
Connection opened
Local path is /home/myuid/Devel_Files/shellscrips
cvs update: conflict: `stress_proxy.sh' created
independently by second party

Closing connection
--------------------------------------------------------------------------------

Looks like committing works fine, but then I get an
ownership conflict.

Any ideas?
Thanks,
Sven

[Sven Hergenhahn]

Logged In: YES
user_id=393897

BTW - it works when I do it with "force"

[Sven Hergenhahn]

Logged In: YES
user_id=393897

BTW - it works when I do it with "force"

[Sven Hergenhahn]

Logged In: YES
user_id=393897

BTW - it works when I do it with "force"