Re: Bug#954422: transition: GNOME 3.36

On Fri, 10 Apr 2020 at 12:27:04 +0200, Emilio Pozuelo Monfort wrote:
> Let's go ahead.

gnome-desktop3 has migrated, but gnome-shell and mutter have not. We're
now getting reports that GNOME Shell in testing is crashing because it
indirectly loads more than one copy of gnome-desktop3.

Would it be possible to binNMU affected packages *in testing*, so that
everything is using the same version even before they migrate? (I'm
not sure whether that will work - they might FTBFS - but it seems worth
a try.)

Dependent packages that are not in sync between testing and unstable:

- mutter
- gnome-shell
- gnome-weather (for completeness, but probably doesn't matter here)

Or is there something else we should have done to make this transition
go more smoothly, like having gnome-desktop3 3.36.x Breaks older
gnome-shell and mutter?

Giving libgnome-desktop-3-19 a Conflicts on -17 and -18 doesn't seem
great because it defeats part of the purpose of the SONAMEs, but perhaps
that would have been the lesser evil?

Versioned symbols in gnome-desktop3 would not help us here, because the
GObject type system is a flat global namespace.

If you would prefer to solve this by getting GNOME Shell 3.36.x
into testing ASAP: it looks as though gnome-shell 3.36 is ready to
migrate if gnome-shell-xrdesktop, gnome-shell-extension-dashtodock,
gnome-shell-extension-easyscreencast are temporarily removed, and
gnome-shell-extension-appindicator is aged by at least a day.

    smcv