Migrated CVS to new server - why did the file commit with a weird, non-cvs, group name?
0
votes
1
answer
493
views
We just migrated a cvs file repository from one server to another.
To test it out, I checked out, changed, then committed a file.
The owner / group changed from "cvs / cvs" to "MyAccount / SomeoneElseAccount".
I was expecting at least "MyAccount / cvs".
1. What was I supposed to expect?
2. Do I need to resolve this, or is this OK?
3. How might I resolve this if it is not OK?
UPDATE
Per the comments, I checked user ids. Results on same line after '='.
id -u cvs = 60000
id -g cvs = 60000
id -G cvs = 600000 20 40
id -u MyAccount = 200007
id -g MyAccount = 200002
id -G MyAccount = 200002 60000 100005 100025
id -u SomeoneElseAccount = 200002
id -g SomeoneElseAccount = 200002
id -G SomeoneElseAccount = 200002 100678
I also had "AnotherUser" check out and commit; his file also ended up with group "SomeoneElseAccount".
id -u AnotherUser = 200018
id -g AnotherUser = 200002
id -G AnotherUser = 200002 60000 100005 100025
Setup on the old server provides a similar id configuration with 200002, though cvs is '100' there, and the items are committed as group 'cvs'.
Checking /etc/group
OLD SERVER
cat /etc/group
...
cvs:!:200002:name,name,name,MyAccount,AnotherUser,name,name...
...
NEW SERVER
cat /etc/group
...
cvs:!:60000:name,name,name,MyAccount,AnotherUser,name,name...
...
Asked by JoshDM
(83 rep)
Jun 29, 2017, 08:00 PM
Last activity: Jun 30, 2017, 12:23 AM
Last activity: Jun 30, 2017, 12:23 AM