Package Building Infrastructure Maintenance

HardenedBSD is growing, thanks to our donors. We've built a new server and thanks to a generous donation, we have a hosted second server. One server is generating nightly builds (our Jenkins instance) and the other is a development workhorse and is responsible for our package building. Our old server took 3.5 hours to do a buildworld+buildkernel just for amd64 and around 75-80 hours for a package build for amd64. Our new server takes 3.5 hours to do a buildworld+buildkernel+release for amd64, i386. and beaglebone black and does a package build in around 50 hours. The core team and the developers at HardenedBSD would like to thank all who have donated (and those who will donate in the future).

We are working to streamline our operations. As such, we will be dropping our i386 package repo and will only build amd64 packages for now. As you've likely noticed, since we have only one web server publishing packages, when we sync the web server with the package builder, the repo as delivered by the package server is placed in a semi-broken state. Dropping the i386 package repo will give us the space we need to do some magic to keep a fully-working package repo while still being able to sync with the web server. We will be making these changes this week and should be completed within the next seven to fourteen days. We appreciate the patience and are grateful that you all have even made this possible.