Re: Bug#954422: transition: GNOME 3.36
Control: tags -1 confirmed
On 08/04/2020 14:22, Sebastian Ramacher wrote:
> On 2020-04-08 11:46:59 +0100, Simon McVittie wrote:
>> On 21/03/2020 13:17, Simon McVittie wrote:
>>>> It would probably make most sense to treat gnome-desktop3 and mutter as
>>>> a single transition, as we have often done in the past: upstream will
>>>> not have tested arbitrary mixtures of 3.34 and 3.36.
>>
>> Progress on this:
>>
>> After chasing regressions for the last few days, I think we have Shell
>> in a good state to consider doing this transition. This would involve
>> uploading the following experimental GNOME packages to unstable as a batch:
>>
>> * gnome-desktop3
>> * gjs
>> * mutter
>> * gnome-shell
>> * gnome-shell-extensions
>>
>> Ubuntu have already done this transition for 20.04 'focal', so I hope
>> the Ubuntu people in the GNOME team can give us an idea of the level of
>> breakage without us having to do our own test-rebuild in Debian.
>> I'm told the only significant porting work needed in Ubuntu was in Unity.
>>
>> gnome-desktop3 ABI breaks have mostly been handled via binNMUs in the
>> past, without being particularly problematic.
>>
>> budgie will need rebuilding against the new mutter, but seems to have
>> already been patched to cope with either the old or new API/ABI.
>>
>> gnome-shell-xrdesktop (a "friendly fork" of gnome-shell with an
>> experimental 3D UI for VR headsets) will need either updating to 3.36.x
>> to match (#956147) or removing from testing for a while. I am not able
>> to test this, and I suspect the rest of the GNOME team are in the same
>> situation; I don't think we should let gnome-shell-xrdesktop (popcon: 0)
>> hold back gnome-shell (popcon: 37K votes).
>
> The xrdesktop stack is currently doing its own transition
> (libgulkan-0.13-0 -> libgulkan-0.14-0, libgxr-0.13-0 -> libgxr-0.14-0,
> and soon the same for libxrdesktop). It's currently blocked on xrdesktop
> in NEW.
Let's go ahead. The situation looks to be in a good state. Extensions have
always been treated this way, on a best effort basis during the transitions, so
we'll keep as many as we can but if any of them aren't compatible and don't get
updated in time we'll drop them from testing until they are fixed.
The xrdesktop/gulkan transition looks to be almost done now, but even if it
wasn't, the only point of entanglement is gnome-shell-xrdesktop which worst case
can be temporarily removed.
Cheers,
Emilio
Reply to: