Your message dated Tue, 16 Jun 2026 12:24:03 +0200
with message-id <[email protected]>
and subject line Re: Bug#1132301: transition: gnome-shell 50
has caused the Debian Bug report #1132301,
regarding transition: gnome-shell 50
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1132301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1132301
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Control: tags -1 + moreinfo
X-Debbugs-Cc: [email protected]
Control: affects -1 + src:gnome-shell
User: [email protected]
Usertags: transition
We now have GNOME Shell 50 in experimental (I'm typing this email into
it) and I've just done the usual MBF asking extensions authors to
update. This will also be the GNOME release used in Ubuntu 26.04 LTS.
Jeremy, Marco: are we ready to ask for a transition slot? (Tagged
moreinfo for now.)
This time, the group of entangled packages is:
* gdm3
* gnome-kiosk
* gnome-remote-desktop
* gnome-session
* gnome-shell
* mutter
all of which are GNOME-team-maintained.
The headline change is that GNOME 50 doesn't support being run as an X11
session using Xorg, at all: it's Wayland or nothing. X11 apps can still
run inside the session via Xwayland as usual.
libgdm1 has an ABI break with no SONAME bump (sigh) as a result of its
X11 functionality being removed, but that library is not widely used and
it seems that the symbols that were removed were only used within gdm3
or by gnome-kiosk, so we can probably get away with using a versioned
Breaks on gnome-kiosk (already present) rather than bumping the package
name to libgdm1a.
https://release.debian.org/transitions/html/auto-mutter.html tracks the
mutter SONAME bump. When we upload gnome-shell to unstable, it will
presumably also generate an auto-upperlimit- tracker.
Usertagged bugs (all Shell extensions right now, but we can use the same
usertag for any other blockers):
https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org&tag=gnome-shell-50
As usual, the automated tests for gnome-shell and mutter are not as
reliable as we would like, so some retries might be necessary. I'm
reluctant to disable them completely because they're our only
opportunity to find out whether things are completely broken on non-x86,
but we can if we have to.
Thanks,
smcv
--- End Message ---
--- Begin Message ---
On 12/06/2026 11:56, Jeremy Bicha wrote:
I believe the transition will need a hint, since every GNOME Shell
transition in Debian and Ubuntu for years has needed a hint. My guess is
that the versioned dependencies from extensions to gnome-shell are too
complex for britney to automatically handle.
Thank you,
Jeremy Bícha
On Fri, Jun 12, 2026, 04:40 Simon McVittie <[email protected]> wrote:
Control: tags -1 + pending
On Fri, 05 Jun 2026 at 17:07:23 +0200, Emilio Pozuelo Monfort wrote:
On Mon, 30 Mar 2026 at 11:23:28 +0100, Simon McVittie wrote:
We now have GNOME Shell 50 in experimental
Go ahead.
This looks ready to migrate, I think we are just waiting for
gnome-shell-extension-easyscreencast (1 day remaining) at which point
the whole group should be able to migrate:
* gdm3
* gnome-kiosk
* gnome-session
* gnome-shell
* mutter
* gnome-shell-extension-easyscreencast
* gnome-shell-frippery
The release team could apply some age-days to
gnome-shell-extension-easyscreencast if you want to get this done.
gnome-remote-desktop already migrated, which surprised me, because it
has a versioned Breaks on gdm3 (but of course it's possible to install
the new g-r-d onto a minimal system, just not onto a complete GNOME
desktop). With hindsight, perhaps we should have given it an
artificial/unnecessary B-D on libgdm-dev to force them to migrate
together?
This transition is done now. Closing.
Cheers,
Emilio
--- End Message ---
