Changing username results in defect repositories
Created by: lukas2511
As you change a username (as admin) the repositories are moved into a new namespace, but the gitolite config doesn't get updated.
There is no data loss, but you can't use that repositories anymore until you change the gitolite config manually.
Activity
Created by: lukas2511
Okay, I had upgraded through several versions up to the newest 4.0.0 release.
I don't remember setting usernames and every username was basically the first part of the email address (in front of the "@")
As some people used funny names like "admin" and "root" in their email addresses i wanted to change these. I basically clicked on Admin -> Users and changed the usernames to something else.
After that modification the repositories were moved (in filesystem) to the correct path, but the gitolite config wasn't updated with the new path and the old path consisted of an empty repository.
To fix that i basically checked out the gitolite admin repository, changed the paths manually, and pushed everything back, that fixed the problem, but it still seems to be a bug in the rename method or something.
By Administrator on 2012-12-24T16:14:53 (imported from GitLab)
Created by: dzaporozhets
got it. thank you
On Mon, Dec 24, 2012 at 6:15 PM, Lukas Schauer notifications@github.comwrote:
Okay, I had upgraded through several versions up to the newest 4.0.0 release.
I don't remember setting usernames and every username was basically the first part of the email address (in front of the "@")
As some people used funny names like "admin" and "root" in their email addresses i wanted to change these. I basically clicked on Admin -> Users and changed the usernames to something else.
After that modification the repositories were moved (in filesystem) to the correct path, but the gitolite config wasn't updated with the new path and the old path consisted of an empty repository.
To fix that i basically checked out the gitolite admin repository, changed the paths manually, and pushed everything back, that fixed the problem, but it still seems to be a bug in the rename method or something.
— Reply to this email directly or view it on GitHubhttps://github.com/gitlabhq/gitlabhq/issues/2367#issuecomment-11662765.
Best regards, Dmitriy
By Administrator on 2012-12-24T16:49:39 (imported from GitLab)
Created by: dzaporozhets
this one should fix a87fccc0
Also I will take this commit to 4-0-stable
By Administrator on 2012-12-24T18:05:51 (imported from GitLab)
