No Fedora 38 ISOs for aarch64

[travier]

Describe the bug

Due to https://pagure.io/releng/issue/11385, there are no Fedora 38 ISOs for aarch64

To Reproduce Please describe the steps needed to reproduce the bug:

1. Go to https://silverblue.fedoraproject.org/download
2. Try to download the Fedora 38 aarch64 ISO

Expected behavior

Get a Fedora 38 aarch64 ISO. We currently link to the Fedora 37 one.

[fwilhe]

Any updates on this? It has been a while. There seems to be an up-to-date rawhide iso for aarch64, but that is not linked on the downloads page too. The 38 directory only contains a x86 iso.

[xmstspider]

I just wonder if anyone cares that the ISO is still missing.

As I understood from the comments in the issue, the fix is trivial (as shown here) so does anyone know why this wasn't still fixed?

Thank you

[travier]

Release ISOs are only ever published once. If you want an official release ISO for aarch64, then it would need to be requested to releng and go through the testing process before it is released.

Otherwise you can use the netboot installer and provide a kickstart to do the installation.

[JamesBelchamber]

Release ISOs are only ever published once. If you want an official release ISO for aarch64, then it would need to be requested to releng and go through the testing process before it is released.

Can we do this? Not doing so implies that we are no longer supporting aarch64, and if that's the case then it feels like something we should formally do rather than by accident?

[juhp]

Probably the easiest workaround currently would be to install SB 37 and then rebase to 38. I agree that is not ideal, but in practice the experience is probably not drastically worse than updating from 38 GA. I assume the aarch64 image will be back for F39 (current rawhide SB is available).

[travier]

Release ISOs are only ever published once. If you want an official release ISO for aarch64, then it would need to be requested to releng and go through the testing process before it is released.

Can we do this?

Definitely. Here are the rough steps (taken from the release process):

• Reach out to Fedora QA
• Pick an existing build (installer ISO) or ask for a new build of Silverblue F38
• Ask the Fedora QA team and people to test it
• Report back here and to releng and ask for it to be promoted as an additional release artifact

Not doing so implies that we are no longer supporting aarch64, and if that's the case then it feels like something we should formally do rather than by accident?

aarch64 is still supported.

[travier]

Another option is to reach out to the Respins SIG and ask them to do one for Silverblue aarch64 as I can not find one in https://kojipkgs.fedoraproject.org/compose/38/ (have not checked all dates).

[JamesBelchamber]

I've put a message in the Respins SIG channel (seemingly the only way to contact them) but there hasn't been a response as of yet. I'll update as I get any.

[tpopela]

There are some updates in https://pagure.io/releng/issue/11385 - so we should follow what's going on there.

[JamesBelchamber]

This has been merged to the new website, which warns about the ISO delay and links here.

When we update the ISO we should also remove this again - seems obvious but could definitely be missed!

[wolverian]

Right now I'm not sure there's any way to install Sericea on aarch64. https://fedoraproject.org/sericea/download/ doesn't mention aarch64 at all. It's unclear to me if Sericea is under Silverblue or another team/responsibility.

[travier]

Please file Sericea issues in the Sway issue tracker: https://gitlab.com/fedora/sigs/sway/SIG/-/issues

[ghost]

Relatedly, the "Verify your download" link to the checksum file does not work (it produces a file that reads "error: invalid path"). I imagine this will be fixed when the new 38 ISO is released.

For those who wish to rebase, I observed the downloaded ISO was named 37-1.7. Modifying the release and version numbers in the URL will allow you to download the correct checksum file, like so:

https://download.fedoraproject.org/pub/fedora/linux/releases/38/Silverblue/aarch64/iso/Fedora-Silverblue-37-1.7-aarch64-CHECKSUM

I was able to verify my download this way, which has a SHA256 hash of: 460e21a00019a0df137890afef96178114bf3963e58f74e77ff67ea765cdb708.

[travier]

Thanks @jamesmotherway. I've filed https://gitlab.com/fedora/websites-apps/fedora-websites/fedora-websites-3.0/-/issues/249 to get it fixed.

[travier]

We did not fix this issue directly but we now have Fedora 39 ISOs so that's good enough.