The << version requirements are just cosmetic, to silence Debian packaging warnings. The version requirements can easily be removed but that wouldn't change the libmutter version numbers.
I don't see breaking gnome-shell as sensible when all consumers of old libmutter would be broken. And I expect it will be correct to add another breaks each cycle, as annoying as that might seem. If you want to fix it properly then the common files would need to move to a version-specific subdirectory so they can coexist (and no "common" package!), but I'm not sure how or if GNOME can support that. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2118736 Title: mutter-common upgrades prematurely [Settings schema 'org.gnome.mutter.x11' is not installed] Status in mutter package in Ubuntu: Fix Released Bug description: My mutter-common was prematurely upgraded to 49 when all other packages remain at 48. This leaves the shell unable to start: > Running GNOME Shell (using mutter 48.1) as a Wayland display server > Settings schema 'org.gnome.mutter.x11' is not installed Workaround: wget https://launchpad.net/ubuntu/+source/mutter/48.1-1ubuntu4/+build/30731469/+files/mutter-common_48.1-1ubuntu4_all.deb sudo dpkg -i mutter-common_48.1-1ubuntu4_all.deb To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2118736/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
