Hi Simon, Simon Josefsson <[email protected]> skribis:
> Ludovic Courtès <[email protected]> writes: > >> A serious limitation to be aware of: ci.guix is underpowered for >> AArch64, to the point that I doubt it could produce artifacts in a >> timely fashion as it stands (it’s roughly one month behind). > > Ouch. I could sponsor a Hetzner CAX41 (16 core, 32GB RAM, 320GB NVME, > 20TB traffic) if a sysadmin has time to set it up, or help me get > through the process of doing it (I seem to get stuck every time I try). That would make quite a difference, almost doubling the number of AArch64 cores behind ci.guix. :-) (To be fully transparent, we have 2 more 16-core Honeycombs hosted at the MDC, but they have been unreachable for several months and we depend on our contact there to go to the data center and investigate.) If you’re willing to do that, it should be possible use an OS config similar to: https://codeberg.org/guix/maintenance/src/branch/master/hydra/modules/sysadmin/honeycomb.scm ‘guix deploy’ has Hetzner support too. I’ve never used it but hopefully people here can provide guidance (Cc’ing knowledgeable people). > Publishing public snapshot of a Guix aarch64 tarball would be great, to > avoid having to rely on the 1.4.0 release tarball. Agreed. Thanks, Ludo’.
