Also played some email switcheroo games and got the Discourse account merged/migrated, so that part is also all done now. Just waiting on the actual FAS groups/packaging/etc stuff.

Commenting from the new account for validation. I assume the pagure (and src.f.o) accounts can't be migrated/merged, so I'll have to abandon existing forks/etc? (This is not a major issue, just want to confirm).

I did move the old account to a lina+legacy@asahilina.net, which isn't used for anything, so I can have the old email as an alias on the new account and have old Git commits recognized as the new identity etc.

I've gone ahead and cleared out the pagure.io forks/permissions from the old account, since there was nothing of value left there (all of that should have been handed off for other reasons anyway). dist-git perms are still relevant (and forks, but less so).

I've added the new account to packager for you.

You should be able to login with the new account to src.fedoraproject.org (to sync the packager group membership), then go to your packages and settings and 'give package' to the new account.

Let us know if there's any issues with that...

I tried to log into src., but I got an infinite redirect loop and going back to the site, " Could not set up you as a user properly, please contact an administrator".

I tried to log into src., but I got an infinite redirect loop and going back to the site, " Could not set up you as a user properly, please contact an administrator".

Incidentally, the username I wanted was "lina" (which would have avoided this whole change to begin with), but FAS wanted 5+ characters... even though 4 and 3 character usernames exist. I'm assuming this is an intentional policy change?

I tried to log into src., but I got an infinite redirect loop and going back to the site, " Could not set up you as a user properly, please contact an administrator".

Logging in as which user?

It looks like perhaps the asahilina account has an alternate email address attached to it that is the same as the primary email for the new account.
If you can login with the asahilina account, go to https://src.fedoraproject.org/settings#nav-email-tab and delete that email there, you should be able to login with the new account.

If that doesn't work for some reason, let us know...

Incidentally, the username I wanted was "lina" (which would have avoided this whole change to begin with), but FAS wanted 5+ characters... even though 4 and 3 character usernames exist. I'm assuming this is an intentional policy change?

Yeah, our old account system allowed short names, but the new/current one doesn't. ;(

Thanks, it was the email thing! I moved all the owned packages over and @ngompa took care of the ones I had commit access to. I also got rid of all the forks.

I think that means we're mostly done, I'm assuming BZ will take care of itself now? (I've been getting the notification emails at the old account address since I already moved the email over).

yes, there should be a perodic job that comes along and reassigns any bugzilla bugs... I don't recall at what frequency it runs.

Shall we close this now? If you find any other issues, please let us know!

and I am sorry this is such a clumsy process. ;(

Minor issue but, I just got locked out of dist-git on my old account with the same error message. However, this time, there should not be an email conflict (the FAS email for the old account is set to lina+legacy@asahilina.net).

Not a major deal, just wanted to note it here.

Minor note for anyone else going through this: /home/lina/.config/bodhi/client.json needs to be deleted to refresh the bodhi token (I think it picks up a new token automatically via kerberos, but you need to delete the file to force it to do so, otherwise it still uses the old identity).

It might be ssh key if you have the same one...

@misc was working on trying to improve the name change situation. He might want to add those to docs...

I checked but I already deleted the SSH key from the old account in FAS as far as I can tell...

Something is still wacky. I can access git over SSH at hoshinolina@pkgs.fedoraproject.org with the SSH key in this FAS account, but https://src.fedoraproject.org still says "You need to upload SSH key to be able to clone over SSH" even if I log out and back in. It still works if I manually set the remote URL though, so it looks like the Pagure frontend just hasn't noticed?

FWIW asahilina@pkgs.fedoraproject.org fails, so the SSH key did get removed correctly from the backend at the old account...

I checked but I already deleted the SSH key from the old account in FAS as far as I can tell...

Huh, odd then. I only thought it was email add ssh keys that it considers there.

Something is still wacky. I can access git over SSH at hoshinolina@pkgs.fedoraproject.org with the SSH key in this FAS account, but https://src.fedoraproject.org still says "You need to upload SSH key to be able to clone over SSH" even if I log out and back in. It still works if I manually set the remote URL though, so it looks like the Pagure frontend just hasn't noticed?

There was another recent report from another user of the same thing. ;( You do show in the packager group tho, so it should show you the ssh link. :(