On 2022-04-04 11:38:37, Simon McVittie wrote:
> On Mon, 28 Mar 2022 at 15:27:12 +0200, Graham Inggs wrote:
> > On Wed, 23 Mar 2022 at 17:21, Simon McVittie <s...@debian.org> wrote:
> > > As usual, lots of Shell
> > > extensions are affected by API changes and will need porting or removal,
> > > but as usual, I think removing the affected Shell extensions from testing
> > > is a better answer than waiting for all of them to be fixed
> 
> It looks as though the libgweather transition reaching bookworm has
> broken bookworm's version of gnome-shell 41 (#1008926), so I think it's
> time to take action to get gnome-shell 42 into testing. Please remove
> these extensions from testing:
> 
> # 1007906
> remove gnome-shell-extension-bluetooth-quick-connect/26-1
> remove gnome-shell-extension-draw-on-your-screen/11-2
> remove gnome-shell-extension-easyscreencast/1.5.0-1
> remove gnome-shell-extension-hamster/0.10.0+git20210628-2
> remove gnome-shell-extension-sound-device-chooser/39-1
> remove gnome-shell-extension-tiling-assistant/32-1
> remove gnome-shell-extension-top-icons-plus/27-6
> remove gnome-shell-extension-volume-mixer/41.1+dfsg-1
> remove gnome-shell-extension-weather/0.0~git20210509.d714eb1-2
> 
> Fixed versions of half of those packages are already available, so
> if you want to get them back into testing sooner, you could also put
> some appropriate age-days on these updated versions:
> 
> gnome-shell-extension-bluetooth-quick-connect/26-2
> gnome-shell-extension-hamster/0.10.0+git20210628-3
> gnome-shell-extension-top-icons-plus/27-7
> gnome-shell-extension-volume-mixer/41.1+dfsg-2
> gnome-shell-extension-weather/0.0~git20210509.d714eb1-3
> 
> but I think removing the broken versions and having the fixed versions
> migrate later is going to be a better outcome than having a broken
> gnome-shell in testing for a few more days.
> 
> I'm preparing a patch for gnome-shell 42 that should prevent a similar
> failure mode from happening at the 42 to 43 transition, but we cannot fix
> gnome-shell 41 without either testing-proposed-updates or a time machine.

Will this issue also affect bullseye to bookworm upgrades? Or will your
fix for 42->43 ensure that this won't happen?

Cheers
-- 
Sebastian Ramacher

Reply via email to