In the blocker review meeting today, @decathorpe highlighted that none of the Rust-based apps in GNOME - including at least gnome-tour , loupe , snapshot and dependencies - has been updated for GNOME 47, though the rest of the desktop is up to date. He says he has worked to prepare everything to make builds possible and asked for co-ordination but received no interest.
It's obviously not good to ship GNOME 47-but-missing-rust-stuff in Fedora 41. Can we get these packages updated (ideally before freeze), and hopefully work more constructively with Fabio in future? Thanks a lot.
Set for tomorrow's meeting.
Metadata Update from @ngompa: - Issue set to the milestone: Fedora 41 - Issue tagged with: default-apps, experience, meeting
@decathorpe can you make it to tomorrow's Workstation WG meeting (2pm UTC)?
Yes - just ping me on Matrix in case I lose track of time.
FWIW, here's what I already worked on to unblock gnome loupe / snapshot / glycin updates for the GNOME 47 cycle, without any responses (or help) from the GNOME package builders for this cycle:
As far as I can tell now, the only blockers that are remaining before I can submit PRs for loupe v47.0 and snapshot v47.0.1:
So most of the work is already done, just some last blockers remaining.
I've completed the reviews for glycin and reis for you.
glycin
reis
Hi @amigadave would you be able to attend the meeting tomorrow? (Calendar link)
Thanks to some quick help from Neal, I was able to push what I had been working on over the finish line:
As soon as all prerequisites are available in Fedora 41 too, I'll push the glycin 1.1.1 update there too.
That should get most things on track for Fedora 41, except for librsvg2, which is still blocked by packaging issues and / or potential upstream regressions in 2.59 (see linked librsvg2 draft PR).
status update:
I'll start working on preparing Rust dependencies for F41.
After liberal application of buildroot overrides (for F41 updates that I had already done but which were not stable yet), the updates for F41 are now ready too:
https://bodhi.fedoraproject.org/updates/FEDORA-2024-0a6327cbf8
I think only the librsvg2 update is left now.
After liberal application of buildroot overrides (for F41 updates that I had already done but which were not stable yet), the updates for F41 are now ready too: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0a6327cbf8 I think only the librsvg2 update is left now.
In future it might be best to use a side tag for all related builds. I'm worried that now if the app update gets pushed stable ahead of the updates it depends on, stuff might break. Or is it only build-time rather than run-time dependencies? But thanks for the work!
After liberal application of buildroot overrides (for F41 updates that I had already done but which were not stable yet), the updates for F41 are now ready too: https://bodhi.fedoraproject.org/updates/FEDORA-2024-0a6327cbf8 I think only the librsvg2 update is left now. In future it might be best to use a side tag for all related builds. I'm worried that now if the app update gets pushed stable ahead of the updates it depends on, stuff might break. Or is it only build-time rather than run-time dependencies? But thanks for the work!
Yes, it's only build-time dependencies. Runtime dependencies should all be satisfiable from the builds in the update I linked here. (I would have preferred to use a side-tag for everything together too, but I had already prepared some of the dependencies in two other side-tag updates, so I couldn't merge everything together even if I wanted to, I think.)
librsvg2 2.59.1 is ready too:
And we've set up a video call between GNOME and Rust packagers for Oct. 14 where we'll discuss improving this situation for future release cycles.
Unless something new comes up until then, I'd consider this issue resolved for now.
Great news!
Metadata Update from @adamwill: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @ngompa: - Issue untagged with: meeting
Log in to comment on this ticket.