Closed
Bug 267046
Opened 20 years ago
Closed 18 years ago
CVS user name not showing up in history log
Categories
(mozilla.org Graveyard :: Server Operations: Projects, task, P2)
mozilla.org Graveyard
Server Operations: Projects
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: u60234, Assigned: reed)
References
Details
My CVS user name, "jasajudeju%telia.com", is not showing up in the history log for files I have committed. The checkin is instead attributed to "uid665". See http://bonsai.mozilla.org/cvsgraph.cgi?file=mozilla/browser/locales/sv-SE/README.txt for one example of this. Is the setup of my account not really finished yet?
Comment 1•20 years ago
|
||
hmm, that's correct. Your account was missing a piece of the setup. I just fixed it. Existing checkins will forever have the uid665 moniker, but new checkins should show up correctly now. Leaving the bug open for now until we determine how it got missed. It's all part of the same script, so unless the person who created your account didn't use the script for some reason, the script might be broken.
There are other accounts who have the same problem. Someone in the cs-CZ localization team is called "uid 642", http://bonsai.mozilla.org/cvsgraph.cgi?file=mozilla/browser/locales/cs-CZ/README.txt And in fr-FR there is a "uid 667", http://bonsai.mozilla.org/cvsgraph.cgi?file=mozilla/browser/locales/fr-FR/chrome/browser/browser.dtd CC:ing the likely people behind these monikers.
Hi, I'm uid667 :) My CVS checkins are indeed marked as "uid667@mozilla.org", but I was told to not worry about it for now. If you don't mind to fix it, my username is benoit.leseul%gmail.com. I've heard of other people sharing the same "uid" on IRC #l10n but I don't remember who it was.
Comment 4•20 years ago
|
||
Dave, these are all loccalizer accounts, so perhaps "the script" needs a version for localizers.
Comment 5•20 years ago
|
||
(In reply to comment #4) > Dave, these are all loccalizer accounts, so perhaps "the script" needs a version > for localizers. Yeah, that was indeed the case. I hadn't gotten back to this bug since then, but Chase and I were discussing it on IRC yesterday and discovered that the adduser script for the l10n repository wasn't adding the users to the /etc/passwd file inside the cvs chroot jail (the main adduser script did this). The lines to do this from the main script got copied into the l10n script last night, so any future accounts should be okay. Any existing once we'll need to track down and update though. Best course at this point is probably to write a script to compare the root level /etc/passwd to the one in the jail and fill in the missing ones.
I've made some checkins this week on the l10n trunk and saw in the CVS log they were still marked as "uid667". Could you please manually fix my account to be named "benoit.leseul%gmail.com"? Thanks in advance.
Updated•19 years ago
|
Assignee: myk → server-ops
Severity: normal → major
OS: Windows XP → All
QA Contact: justdave → myk
Hardware: PC → All
Updated•19 years ago
|
QA Contact: myk → justin
Comment 7•19 years ago
|
||
since this is going to require a few hours of playtime, it's a project. Taking, since I'm going to be messing with cvs stuff next month anyway.
Assignee: server-ops → justdave
Severity: major → normal
Component: Server Operations → Server Operations Projects
Updated•19 years ago
|
Priority: -- → P3
Updated•18 years ago
|
Priority: P3 → P2
Whiteboard: needs host and jail passwd file resync
| Assignee | ||
Comment 8•18 years ago
|
||
What's the latest on this?
Comment 9•18 years ago
|
||
sounds like a good intern project ;) I just dropped the production passwd file and the one from the jail in your home directory on boris.
Assignee: justdave → reed
| Assignee | ||
Comment 10•18 years ago
|
||
Found four issues with homedir inconsistencies, which were then fixed, but the users themselves are in sync already.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Whiteboard: needs host and jail passwd file resync
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•