Plan is to squeeze in a failed packages rebuild before the big python rebuild drops. Probably starting that today.
Status "built" means it finished building and is waiting to be moved. Packages are being moved live at the and of a build-cycle. As you can see on the status page, we still have ~550 packages to…
Having an archive would be nice indeed. I can come up with some rough size calculations, maybe I have the space. It won't be fast, but I think considering the usage is wont have to be.
That would obviously be nice, but as-is the donations do not even cover electricity costs for the one machine we do have.
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.