You are not logged in.
Q: see title
While waitng for access to "source files" from https://archlinux.org/packages/extra/any/nextcloud/ I got this message
Interne Serverfout: beheerder heeft Anubis verkeerd geconfigureerd. Vraag de beheerder om de logs te bekijken..
Translation :
Internal Server Error: The administrator has configured Anubis incorrectly. Ask the administrator to check the logs.
Under that message this was shown on a yellowish background
H4sIAAAAAAAA/wAx
AM7/dmFncmVhbnkg
cmVlYmU6IHB1bnl5
cmF0cjogaGZyZSBz
bnZ5cnEgcHVueXly
YXRyCgMAGNmmLzEA
AAA=Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Viewing the sources works for me (https://gitlab.archlinux.org/archlinux/ … /nextcloud) - and I am also still waiting for my 2FA reset on GitLab for almost two years.
I guess if you don't have access to GitLab, i.e. with an account, maybe use one of (i.e. the most fitting) the mailing lists.
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
I do have an archlinux gitlab account (registered before it needed manual actions by account support) but have no idea where to file bugs for the archlinux gitlab instance.
I've just subscribed to arch-devops ML and sended a message to that list.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
Ah, I see. If you want to report a general bug in GitLab, I'd report it upstream to GitLab's repo.
If you want to report a bug pertaining to GitLab as hosted by Arch Linux, I'd report it here: https://gitlab.archlinux.org/archlinux/teams/devops
Inofficial first vice president of the Rust Evangelism Strike Force
Offline
gitlab currently runs level 6 anubis which takes an insane amount of CPU and unhealthy amount of RAM and time to finish
On less equipped hardware it will take forever™ or fail.
… accept that the internet is currently fundamentally broken
waiting for my 2FA reset on GitLab
… and so is apparently the entire archlinux SSO/2FA mistake endeavor ![]()
Online