Your message dated Sat, 10 Jan 2026 11:52:34 +0000
with message-id <[email protected]>
and subject line Released with 13.3
has caused the Debian Bug report #1122372,
regarding trixie-pu: package mutter/48.7-0+deb13u1
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.)
--
1122372: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1122372
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: trixie
X-Debbugs-Cc: [email protected], [email protected]
Control: affects -1 + src:mutter
User: [email protected]
Usertags: pu
[ Reason ]
Catch up with upstream bugfix releases
[ Impact ]
If not accepted, various bug fixes that happened upstream since Debian
13.0 will not be available to users of stable, for example #1121170 (a
crash after long screencast sessions).
[ Tests ]
A functionally-equivalent test-build is available from
<https://people.debian.org/~smcv/temp/2025/13.3/>. The only differences
between that and the proposed version are in debian/changelog. I have
been using this version on a GNOME desktop for a while, and recently
upgraded my work computer and my partner's daily-use laptop to match.
I asked for wider testing in
<https://lists.debian.org/debian-gtk-gnome/2025/11/msg00015.html> and
have not had any regression reports. (I haven't had any positive test
results either, though.)
I have not attempted to reproduce specific bugs.
There is unit test coverage, but it is unfortunately rather flaky (this
is an ongoing issue also affecting testing/unstable) and might need some
retries to get the proposed version through buildds and autopkgtest. In
this version I've left unit test failures as fatal rather than ignoring
them, for visibility.
48.5 was in unstable until it was superseded by 49.x. 48.6 and 48.7 were
never in unstable.
[ Risks ]
A Wayland compositor is not a simple codebase, so regressions are
possible. Upstream is generally good about solving regressions in their
next stable release (48.8 is due on around 2026-01-03, which is slightly
too late for our planned 13.3 point release on 2026-01-10).
[ Checklist ]
[x] *all* changes are documented in the d/changelog
[x] I reviewed all changes and I approve them
[x] attach debdiff against the package in (old)stable
[x] the issue is verified as fixed in unstable
[ Changes ]
All changes are described in the changelog. All changes came from
upstream, except for an update to d/libmutter-test-16.symbols to account
for new unit-test-only ABI, and routine updates to d/gbp/conf and
d/control to switch to the debian/trixie branch.
The attached debdiff was lightly filtered to exclude translations.
[ Other info ]
This version has only been tested together with the corresponding
gnome-shell update. I'm not aware of any explicit dependencies, but I
suggest accepting or deferring both, as a batch.
I have not yet uploaded this or the corresponding gnome-shell update to
proposed-updates, to avoid making it hard to do smaller updates if this
new-upstream-version update is rejected; but if the release team is
inclined to accept the new upstream versions, then I think it would be a
good idea to get them into proposed-updates soon so that they can have
wider testing. Please let me know if/when I can upload.
mutter_48.7-0+deb13u1.diff.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Package: release.debian.org\nVersion: 13.3\n\nThis update has been released as
part of Debian 13.3.
--- End Message ---
