Your message dated Mon, 16 Feb 2026 15:06:14 +0000
with message-id <[email protected]>
and subject line Bug#967599: fixed in lmemory 0.6c-14
has caused the Debian Bug report #967599,
regarding lmemory: depends on deprecated GTK 2
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.)
--
967599: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967599
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: lmemory
Severity: normal
User: [email protected]
Usertags: gtk2 oldlibs
Control: block 947713 by -1
This package has Build-Depends on GTK 2 (libgtk2.0-dev), or produces
binary packages with a Depends on GTK 2.
GTK 2 was superseded by GTK 3 in 2011 (see
<https://bugs.debian.org/947713>). It no longer receives any significant
upstream maintenance, and in particular does not get feature development
for new features like UI scaling on high-pixel-density displays (HiDPI)
and native Wayland support. GTK 3 is in maintenance mode and GTK 4 is
approaching release, so it seems like a good time to be thinking about
minimizing the amount of GTK 2 in the archive.
GTK 2 is used by some important productivity applications like GIMP, and
has also historically been a popular UI toolkit for proprietary software
that we can't change, so perhaps removing GTK 2 from Debian will never be
feasible. However, it has reached the point where a dependency on it is
a bug - not a release-critical bug, and not a bug that can necessarily
be fixed quickly, but a piece of technical debt that maintainers should
be aware of.
A porting guide is provided in the GTK 3 documentation:
https://developer.gnome.org/gtk3/stable/migrating.html
Some libraries (for example libgtkspell0) expose GTK as part of their
API/ABI, in which case removing the deprecated dependency requires
breaking API/ABI. For these libraries, in many cases there will already
be a corresponding GTK 3 version (for example libgtkspell3-3-0), in which
case the GTK 2-based library should probably be deprecated or removed
itself. If there is no GTK 3 equivalent, of a GTK 2-based library,
maintainers should talk to the dependent library's upstream developers
about whether the dependent library should break API/ABI and switch
to GTK 3, or whether the dependent library should itself be deprecated
or removed.
A few packages extend GTK 2 by providing plugins (theme engines, input
methods, etc.) or themes, for example ibus and mate-themes. If these
packages deliberately support GTK 2 even though it is deprecated, and
they also support GTK 3, then it is appropriate to mark this mass-filed
bug as wontfix for now. I have tried to exclude these packages from
the mass-bug-filing, but I probably missed some of them.
Regards,
smcv
--- End Message ---
--- Begin Message ---
Source: lmemory
Source-Version: 0.6c-14
Done: Bastian Germann <[email protected]>
We believe that the bug you reported is fixed in the latest version of
lmemory, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Bastian Germann <[email protected]> (supplier of updated lmemory package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Mon, 16 Feb 2026 15:24:19 +0100
Source: lmemory
Architecture: source
Version: 0.6c-14
Distribution: unstable
Urgency: medium
Maintainer: Debian Games Team <[email protected]>
Changed-By: Bastian Germann <[email protected]>
Closes: 967599
Changes:
lmemory (0.6c-14) unstable; urgency=medium
.
* Team upload
* Port to GTK 3 (Closes: #967599)
Checksums-Sha1:
c0547a50dabfe7a7f3f56006ada5af88ad43c468 1744 lmemory_0.6c-14.dsc
5f55e3676cd12b781c5aa322c369093f16be39ad 111812 lmemory_0.6c-14.debian.tar.xz
290a9c2ca3ede045118a5ff42462d8ca5f930b3d 13794 lmemory_0.6c-14_source.buildinfo
Checksums-Sha256:
06167a59f301debfe2a507a75f6746a07b5559d894e7e07cf744df1b9a04eb93 1744
lmemory_0.6c-14.dsc
496f602065080faedc0677059b0f42e467f17f39be55e07a69802c10ab1d7618 111812
lmemory_0.6c-14.debian.tar.xz
550d886e0daaea7ca5698e2e15ac070bb0ac0f47223cac3b5be9149e2d869df6 13794
lmemory_0.6c-14_source.buildinfo
Files:
a04ed5cd9b323fce59910786978cd6d2 1744 games optional lmemory_0.6c-14.dsc
35c6d19bb95b21461ce38185a1b415ae 111812 games optional
lmemory_0.6c-14.debian.tar.xz
f9d8a8cb811d8c5188f6eaf816b18cf2 13794 games optional
lmemory_0.6c-14_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmmTKMkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFHabC/4m+wbtL7+kFGC3XmvTPRvFfX0iZaJ92mR1
xXPKXnh1OnUNX9EpMFz4aECii4llC6WvGqNOlOLdWMjGTPUstN//fPFkospx+3l3
NLIRy8iUFXEgvo7DHibEmz3r/WnksI09DJXbXpbF32wcKQeeGm3CBPIHg4X4eDQj
hCsT51OLL4brcAw0eEgEn4TzV8DVQSNn9xXgDR+ug8Oyo8d6SxUyH//DFJcJPIB3
vb9bvwtVkGDqJ/Y3yHLIPAaDOzXJ/y7dFZN3PZq+uCHOihFNESDiJocaW/gTWuPK
OKFDchqQKlx8kY9ZIN3mM2QLgYnfr3EFYzuNNhK9rftErS1sey57kVVhb+zgX5M9
CH7mGb9CNPC2Xf4Qgr3QaKzwEbNXkxRMuARXDgSu4EwaRvmSeOnKARskwl1HsFeb
5xDAXmTIoCOIPqC18EeIM/7M9B3d43PGUE9SWpMh2Yiuz075qaIt6GkcLWDxNttS
dmuN/j/uAmygeTid9VQiSyR4SNh07Bg=
=9pK1
-----END PGP SIGNATURE-----
pgpjR59N3Ok0a.pgp
Description: PGP signature
--- End Message ---
