Hi, Rutherther <[email protected]> skribis:
>>Two possibilities I can think of: >> >> 1. If you can get those artificats to be built by ci.guix, then they >> will be hosted here, as is the case for everything at >> <https://guix.gnu.org/en/download/latest/>. > > Yes, I wanna get to that, hopefully I will have scheme files with > packages / manifests ready till the end of the week. (I would like to > move away from the shell script to generate the artifacts see > <https://codeberg.org/guix/guix/issues/4348>) I was solving getting > aarch64 ISO and qcow2 ready - it works now. Though then its still not > clear to me if I should contribute the jobset declaration to codeberg > or if defining it through the web interface 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). ARMv7 (armhf-linux) is disabled altogether. RISC-V is mostly non-functional: <https://codeberg.org/guix/maintenance/issues/30>. Maybe we can sort of prioritirize builds, but let’s not wait until the last minute if we need to work on the infra. >> 2. Alternatively, they could be uploaded to alpha.gnu.org, which >> exists specifically for the purpose of providing release >> candidates. > > I see. Maybe it would be good to go this way for now. Let [email protected] know if you and/or other release team members want to be authorized for {ftp,alpha}.gnu.org uploads (it may take a week or more for the FSF sysadmins to process it.) Thanks, Ludo’.
