Buildserver is back online now.
But to answer your question, it would need to be v4 capable and at least 6-8 dedicated cores and >64GiB ram.
Sort of. The ISP has IPv4 connectivity problems, so I stopped the buildbot. This way we do not have packages failing by mistake due to lack of IPv4 connectivity.
I implemented cache-tagging, should work fine from now on. Please reopen if the problem persists for you.
Well, seems that the new method does not clear correctly either. I now implemented a more "radical" purge method, lets see if that helps.
We are tracking this in ALHP/alhp-keyring#4. I'll try to get a new cache purge mechanism going this weekend.
You would need to modify ALHP to use Manjaro's "stable" repository. Since ALHP uses the (state repository)[https://gitlab.archlinux.org/archlinux/packaging/state], you would have to find a Manjaro…
@mihalycsaba You seem to have a different problem, have a look at ALHP/alhp-keyring#4.
Not sure its a good idea to close this, I think we should try to solve this instead of recommending switching mirrors. The CDNs probably have a cache purge problem, I'll try to implement a…
Not sure how you jumped to the conclusion its expired, because its certainly not:
pacman-key -l cie@harting.dev …
Yes I considered that. Would add a lot of packages of course, but it would present at least some of these windows where one can potentially break something. Need to think about that, because its…