Can't view Manjaro gitlab unless signed in now

Is there a reason that gitlab.manjaro.org was made private and can be viewed only by developers who are signed in? There is no way to sign up, and signing in with GitHub credentials does not work.

The reason I went to the gitlab is because I find it concerning that unstable still doesn’t have linux 7.2.3 five days after it was released. This makes me wonder if anyone is currently maintaining the kernels for Manjaro. I decided to see if there was any progress on the gitlab, only to find out I need an account to view it now.

If the Manjaro team wants to be trusted, their PKGBUILD files and source code should be publicly accessible and not require a login to view.

That was a try from @philm to check if the bots will stop sucking server resources but it didn’t work, so i guess he will revert it. I hope so.

This version doesn’t seem to be on upstream yet cf.

So perhaps Arch Linux is going down :thinking:

We are currently having a lot of issues with the Gitlab instance.

It is stinking slow - worst case - pushing a commit takes 2-3 minutes.

In an attempt to check if it were scrapes that slows the system almost to a halt - I suggested we tested by only allowing registered users.

But that didn’t help - it is still painfully slow.

We are looking into options to migrate the repositories to a forgejo (fork of gitea) instance - but it is a slow process…

linux 7.2.3. arch1-2 was released to Arch core-testing repository yesterday

Arch core repository still has linux 7.2.2.arch1-1

As @Teo & @linux-aarhus mentioned, @philm restricted the Manjaro Gitlab instance to registered users only temporarily.

Maybe you’re thinking of 7.3-rc1 released 2026-08-30? 7.2.3 was released 2026-09-02. The kernel builds were triggered that night, but since GitLab was down a few times, the first two attempts failed. I just pushed all the updated kernels just now. Well, except for 6.12.108 due to a patch not applying that Phil will have to sort out.

To be optimistic… I have some automated scripts that fail and I have to relaunch them often
:face_exhaling:

Oh, forgot to mention–We have a GitLab mirror created by @boredland here:

Thank you to everyone who replied. I’m sorry that I got suspicious when kernels weren’t updating and the gitlab wasn’t publicly accessible.