Your message dated Thu, 17 Oct 2024 14:33:53 +0100 with message-id <[email protected]> and subject line Re: Bug#1081519: transition: gnome-shell 47 has caused the Debian Bug report #1081519, regarding transition: gnome-shell 47 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.) -- 1081519: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081519 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: release.debian.org Severity: normal X-Debbugs-Cc: [email protected] Tags: moreinfo Control: block -1 by 1080521 1079548 Control: affects -1 + src:gnome-shell src:mutter src:gnome-settings-daemon src:gnome-remote-desktop User: [email protected] Usertags: transition Forwarded: https://release.debian.org/transitions/html/gnome-shell-47.html The GNOME team is preparing GNOME 47 in experimental. As usual, we will need a transition to get a new libmutter SONAME into testing, and to get GNOME Shell and its extensions migrated. This is the GNOME release that is likely to be shipped in Debian 13, assuming a freeze date somewhere between December 2024 and March 2025. GNOME 47 is not fully released yet (release day is the 14th) but I'm opening this bug a little early to make the release team aware. Blockers ======== We should get GTK 4.16.x into unstable first (#1079548). We are waiting for GNOME 47 final releases which are due on Saturday (currently most of it is at release-candidate status), hence moreinfo tag. We should seriously consider getting gjs upgraded to 1.81.x/1.82.x either first or at the same time, which will require a mini-transition to remove it from armel (#1080521). Ideally gnome-settings-daemon would go along with this transition, but it has several very flaky build-time tests which cause FTBFS. If they can't be fixed soon, a mitigation would be to disable those tests (I suspect this is a problem with the test scaffolding rather than g-s-d itself). Packages involved ================= The core packages are all GNOME-team-maintained: gjs gnome-control-center gnome-kiosk gnome-remote-desktop gnome-settings-daemon gnome-shell gnome-shell-extensions mutter nautilus xdg-desktop-portal-gnome and then as usual, we will need to do a mass removal of any GNOME Shell extensions that have not been updated (several are already fixed in experimental and can be team-uploaded or NMU'd to unstable, but some will almost certainly need to be removed from testing): https://release.debian.org/transitions/html/gnome-shell-47.html https://udd.debian.org/cgi-bin/bts-usertags.cgi?user=pkg-gnome-maintainers%40lists.alioth.debian.org&tag=gnome-shell-47 Thanks, smcv
--- End Message ---
--- Begin Message ---On Wed, 16 Oct 2024 at 19:10:59 +0200, Paul Gevers wrote: > On 16-10-2024 12:24, Simon McVittie wrote: > > One thing that might be breaking this (although I don't see any obvious > > references to it in britney's log) is that the ftp team removed all of the > > binary packages from src:gdm3, not just gdm3.deb itself as I requested > > (the naming convention for removal bugs unfortunately does not distinguish > > between removing gdm3.deb, and removing all binaries from src:gdm3). > > That's what I'm seeing in output.txt: > trying: gdm3 > skipped: gdm3 (0, 95, 9) > got: 208+0: a-1:a-10:a-14:a-0:i-14:m-0:p-0:r-168:s-1 > * armel: gnome-shell > > > Or, if it would be helpful to binNMU gdm3 on armel, I believe the release > > team could schedule that at any time. > > I've triggered a rebuild, let's see where that brings us. Looks like that was sufficient to unblock the migration. The core parts of GNOME 47 have now arrived in testing; closing the bug. smcv
--- End Message ---
