On Fri, 2022-05-06 at 14:52 +0000, mowest wrote:
On Friday, May 6, 2022 2:59:30 AM (-04:00), Peter Boy wrote:
> > Am 06.05.2022 um 06:02 schrieb mowest <mowest(a)vivaldi.net>:
> > If this is simply a matter of moving our infrastructure from Pagure to Gitlab
> Well, it is a matter of moving, but simply? You have to adjust a lot of details.
My apologies, I did not mean to infer that this would be an easy process. I still agree
with other comments that there are more important tasks to focus on at this time.
> Fedora has decided to give up to host it’s repository and had outsourced it to a
commercial service provider, gitlab in this case. You will continue zu use your FAS
account to login to the gitlab hosted Fedora repos. The Fedora Account is kind of
„shadowed“ in gitlab.
I have never had a Gitlab account, so I decided to attempt to get
connected to the Fedora namespace / "instance" in Gitlab to see what
has been moved over. I found the sign-in / sign-up process as little
cumbersome. By hitting the Gitlab Fedora Namespace, it triggered an
authentication asking for my Fedora Account by taking me to the FAS
login page. After doing so, it then kicked me back to Gitlab where it
said that it sent an email to verify my email address. I clicked on
the link to authenticate my email address, and then that link took me
to a page claiming that my email had been verified, and asked me to
login with either my username which was in the Gitlab email
verification email, or my email address that I use for my Fedora
Account. However, when I tried to login using either of those and
then use my Fedora Account Password, that failed.
I agree the process is confusing, but you went wrong here. What you
should do at this point is ignore the login screen and go back to the
SSO login link. Now your account is confirmed, it will work and fully
log you in, after you accept Gitlab's T&Cs.
I just went through the same thing, and yeah I agree it's messy.
IRC: adamw | Twitter: adamw_ha