The final rc-1.5 f39 compose had a few failing deliverables that were non blocking.
Even though they were non blocking, we want to try and provide them if possible. In some cases they were also missing from F38, making it hard to tell users to use a previous release.
Some of these failed due to a transitory (and really hard to track down) 502 error when mirroring ostree content. Some of these failed due to a transitory and anoying SIGILL in python, causing the installer to crash.
Failed artifacts are:
missing ostree install images: Onyx - x86_64 Sericea - x86_64 Kinoite - ppc64le Silverblue - aarch64 missing Live images: Security - x86_64 Astronomy_KDE - x86_64 LXQt - aarch64 KDE - aarch64 Workstation - aarch64
I have run composes against the 1.5 rc content for all the ostree install images and we have boot.isos from those.
I ran security live: https://koji.fedoraproject.org/koji/taskinfo?taskID=108494543
Astronomy-KDE failed due to broken deps, so there's not much we can do.
I will do the last 3 aarch64 live composes later today.
Once we have them all in place we need to:
Put them in /pub/alt/releases/39/respin/ Create checksum files for them and sign those. Have websites adjust to them.
CC: @adamwill @darknao
CC @amoloney to keep an eye on this and make sure it all gets synced up with websites team
Problem: conflicting requests\n - nothing provides cfitsio = 4.2.0 needed by kst-fits-2.0.8-45.fc39.x86_64
kst-2.0.8-46.fc39 has just been pushed stable after freeze end, so there are chances that the next build will complete fine.
Yeah, but we can't really compose a version with updates enabled and then call it 'f39 ga'... it wouldn't be.
Images and their checksums are under /pub/alt/releases/39/respins
Is that their final location, or are we planning to copy them to /pub/fedora/linux/releases/39/ before the release? Like for Onyx: /pub/fedora/linux/releases/39/Onyx/aarch64/iso/Fedora-Onyx-ostree-x86_64-39-1.5-respin.iso
/pub/fedora/linux/releases/39/
/pub/fedora/linux/releases/39/Onyx/aarch64/iso/Fedora-Onyx-ostree-x86_64-39-1.5-respin.iso
Any plans for Workstation and Spins (LXQt & KDE)?
That is the final location. we don't want to mix them in with the rc-1.5 compose...
workstation/aarch64, kde/aarch64, lxqt/aarch64 I just did, we need to put them in place, generate and sign checksums...
Metadata Update from @phsmoura: - Issue tagged with: medium-gain, medium-trouble, ops
workstation / aarch64: https://koji.fedoraproject.org/koji/taskinfo?taskID=108662990 kde /aarch64: https://koji.fedoraproject.org/koji/taskinfo?taskID=108662997 lxqt / aarch64: https://koji.fedoraproject.org/koji/taskinfo?taskID=108661826
(still need to move into place/get checksums/get signed).
All artifacts should be in place with checksums.
Thanks for the work here for the ostree images. Very much appreciated.
There's been some call to have torrents for at least the live images... not sure how easy that would be to do (while making clear they are respins).
Yeah, we have the torrent files for the respun artifacts. Some work needs to be done to get it consumed by the tracker. I plan to look into it on Friday.
A good few of these are spins that I use, so as soon as the torrents are put up, I intend to grab them and seed them as well.
The body of Fedora-Sericea-ostree-39-respin2-1.5-x86_64-CHECKSUM looks like this:
Hash: SHA256 Hash: SHA256 629ac505c5d82bcbb1036da6aa8f9190a86e26c0724286dcea24a825a181d66e /pub/alt/releases/39/respins/Sericea/x86_64/Fedora-Sericea-ostree-x86_64-39-1.5-respin2.iso
Having the full path there seems to be causing the provided instructions for verifying the image to fail (using sha256sum -c).
sha256sum -c
I was preparing for our talk on immutable desktops at SCaLE today and noticed these torrents were missing as well. Curiously, some of the ones missing for GA still have the Fedora 39 Beta versions available.
So, we have an existing ticket going on here: https://pagure.io/fedora-infrastructure/issue/11689; I have to create a new torrents for this and that will fix the issue, closing this ticket against that issue, if there is anything else, please let us know!
Metadata Update from @jnsamyak: - Issue close_status updated to: Duplicate - Issue status updated to: Closed (was: Open)
This is close to fixed... being tracked in:
https://pagure.io/fedora-infrastructure/issue/11689
Metadata Update from @kevin: - Issue close_status updated to: Fixed (was: Duplicate)