Guys at Firefox asked me to try a newer version after I filled a bug report. The new version for rawhide was released more than 24 hours ago and I still don’t get it.
I can not check which mirror already got the update, but even if I could, the process of selecting the mirror is impossible to remember.
Any ideas how to make the contribution process smooth for people? I do have plenty of time, because I have no job and no money, and it still feel daunting.
After a package is built, there needs to be a successful compose and then that compose synced to mirrors. This inevitably introduces delay. If there is urgency, though, you can download the build directly. You can find the build right from the bodhi page you linked – see the “Builds” tab and follow the link to Koji and download from there. (There is also a koji command line to download builds, but for infrequent use, just downloading from the web interface seems less complicated to me.)
successful compose
Here is the update. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d93dabdfaf Where is its compose?
and then that compose synced to mirrors. This inevitably introduces delay.
Yea, the question is how to reduce the inevitable sync delay. There are like a lot of solutions for near real-time sync in 2023, but Fedora engineering team needs to be interested, otherwise it won’t gonna happen.
for infrequent use, just downloading from the web interface seems less complicated to me
It is infrequent, indeed, but the friction is killing me. I would rather spend my braincells on something more useful than remembering necessary commands and workflow, because the real problem I need to solve is more likely different from the bug I run into.
successful compose
Here is the update. https://bodhi.fedoraproject.org/updates/FEDORA-2023-d93dabdfaf Where is its
compose?
Here’s the devel list report on that compose:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/EPEJDFOICLXKE6YLOXA2PS3HAI3OTVPZ/
rawhide starts composing at 05:15UTC every day. It takes 4-5hours to
complete, then syncs out.
and then that compose synced to mirrors. This inevitably introduces delay.
Yea, the question is hoow to reduce the inevitable sync delay. There are like a lot of solutions for near real-time sync in 2023, but Fedora engineering team needs to be interested, otherwise it won’t gonna happen.
I think releng is interested in improving things, but… it’s not a
simple problem.
for infrequent use, just downloading from the web interface seems less complicated to me
It is infrequent, indeed, but the friction is killing me. I would rather spend my braincells on something more useful than remembering necessary commands and workflow, because the real problem I need to solve is more likely different from the bug I run into.
Lots of ways to get builds to test. 
If it’s just a build and doesn’t have an update yet, you can use:
koji download-build firefox-113.0.1-4.fc39
If it has an update in bodhi, or there’s a bunch of builds in an update
you want:
bodhi updates download --updateid FEDORA-2023-d93dabdfaf
Unfortunately, https://bodhi.fedoraproject.org/updates/FEDORA-2023-d93dabdfaf doesn’t propose these commands. It proposes the command that doesn’t work.
sudo dnf upgrade --refresh --advisory=FEDORA-2023-d93dabdfaf
And as a result I can only report back to guys 4 days later (and only because I’ve left this tab open).
There is an open issue for the Bodhi tool about this: Announcements for new packages give instructions for upgrading · Issue #2564 · fedora-infra/bodhi · GitHub. That’s probably the best place to suggest that — or, I’m sure, patches would be welcome.
That ticket is 5 y/o. Is this the right diagram with the update delivery process?
graph LR
src{{sources}} --> koji --> pkg{{package}} --> bodhi --> up{{update}} --> out{{compose}} --> mirror
style bodhi stroke-width:4px,fill:#555,color:#eee
style koji stroke-width:4px,fill:#555,color:#eee
style mirror stroke-width:4px,fill:#555,color:#eee
Yes, that looks approximately right to me. Note that sources can create multiple packages, and bodhi updates will include all packages from a build in koji and can also include multiple builds (useful when two interrelated packages need to be updated together). And then the compose brings together everything that was released to updates that day.
A complete picture should probably also include updates-testing…