RFH: GNOME updates for Trixie, especially Evolution, online accounts and multimedia

On Thu, 05 Jun 2025 at 07:54:21 -0400, Jeremy Bícha wrote:
>My workload is rather high and I don't really have spare capacity
>currently to work on updating GNOME packages for Trixie. I'm letting
>y'all know so that someone else can pick up these updates if wanted.

On Thu, 05 Jun 2025 at 14:17:19 +0100, Simon McVittie wrote:
>I can try to find time for some review, testing and unblock paperwork.

I have been trying to do this, but there's a lot, and I am not going to 
be able to do all of it. Other GNOME team members or those with an 
interest in our default desktop environment: please help! I can't do 
this alone.

In particular, I am **NOT** going to do stable updates for the Evolution 
family. I don't routinely use these applications and neither do the 
users I support, so I am not sufficiently familiar with them to know 
where extra care is needed.

Similarly, I am unlikely to touch gnome-online-accounts any time soon. 
If someone who knows about Microsoft account integration wants #1100711 
to happen for trixie, they will have to take responsibility for that - I 
don't routinely use Microsoft online services, and I don't know whether 
the Passport account that I used to use for MSNP is even still valid.

I'm also unlikely to do anything with gnome-user-share or the multimedia 
family (grilo, gssdp, gupnp and so on).

The release team is now discussing going into full freeze [1] so there 
will presumably be a higher bar for updates getting into 13.0 from now 
on. Please be extra-careful with updates that could have implications 
for other packages, and if in doubt, upload them to experimental.

[1] https://lists.debian.org/debian-release/2025/07/msg00500.html

For updates that have been verified to be low-risk (especially in leaf 
packages), I think we can still go to unstable, but we need to be aware 
that the "unblock" requests will need to turn into "trixie-pu" requests 
for 13.1 if they don't make it into 13.0. For libraries - especially 
pango1.0, but also libadwaita and libdex - we should be extra-careful 
not to have an impact on their dependent packages, including 
accidentally introducing a dependency on the new library.

     smcv