You are not logged in.
I encountered an issue with the Bitwarden package and doing a search for the problem resulted in finding this bug report on the Arch Gitlab: https://gitlab.archlinux.org/archlinux/ … k_items/11 which is the same problem I have.
I am wanting to create a Gitlab account so I can contribute to this bug report but currently Gitlab says, "Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.". No problem, I registered an account, sent an email to accountsupport@archlinux.org and then waited. It's been two weeks and heard nothing back.
Is two weeks a normal amount of time to wait? I use a + email address as separate logins for every website and service I use so is it possible it's ended up in a spam box? Should I just send another email or is there another email address I can contact someone on about it?
Last edited by Thorned_Rose (2026-06-17 22:48:41)
Offline
Is two weeks a normal amount of time to wait?
For me it was like ~4 weeks (March 20th; April 16)
I guess 3-4 weeks is normal...
Edit:
quote
Last edited by 5hridhyan (2026-04-28 01:53:46)
Fun fact: There is no such thing as bad luck. If there were, I'd call existence on Earth the ultimate example.
Offline
It's the unfortunate side effect of things being maintained by volunteers, things may take a while to get processed (especially that kind of boring paperwork). I sent my approval request 4 weeks ago, haven't heard back yet. ![]()
When you sent your email, you should've got back an automatic response from the GitLab Support Desk thingy telling you the ticket has been created. Once it's on the issue tracker, there's nothing much to do besides wait for the ticket to be triaged eventually.
Offline
Thanks all for relating your experiences. Glad to know it's not just me and my email preferences ![]()
Offline
I encountered an issue with the Bitwarden package and doing a search for the problem resulted in finding this bug report on the Arch Gitlab: https://gitlab.archlinux.org/archlinux/ … k_items/11fnf mods which is the same problem I have.
I am wanting to create a Gitlab account so I can contribute to this bug report but currently Gitlab says, "Due to an influx of spam, we have had to require each new account to be manually approved. Please register an account and then write an email to accountsupport@archlinux.org to get it approved. Sorry for the inconvenience.". No problem, I registered an account, sent an email to accountsupport@archlinux.org and then waited. It's been two weeks and heard nothing back.
Is two weeks a normal amount of time to wait? I use a + email address as separate logins for every website and service I use so is it possible it's ended up in a spam box? Should I just send another email or is there another email address I can contact someone on about it?
I had a similar concern. Two weeks feels longer than expected, so I’d probably send a follow-up email just in case the first one got missed or filtered as spam. Hopefully someone from the Arch team can take a look soon.
Offline
I had a similar concern. Two weeks feels longer than expected, so I’d probably send a follow-up email just in case the first one got missed or filtered as spam. Hopefully someone from the Arch team can take a look soon.
Thankfully all sorted now
Took a little over a month to get allowed.
Offline
omg why so long? I wait since 5/6/2026...
Offline
Well, I guess there's a bit of luck involved... I sent a followup a week or two ago and still no update. I originally sent the email more than 2 months ago by now ![]()
I don't want to be that kind of person that sends multiple followups but it's quite frustrating being stuck on this formality... I get that everyone's a volunteer and understand things take time, but waiting for months and seeing newer requests get processed starts to leave quite a sour taste... I've seen in other threads the sso approval process described as "borderline dysfunctional", and I'm starting to think it's actually "entirely dysfunctional" ![]()
Offline