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
qTox does not seem to use GTK / GDK / Glib stuff, though d/control still lists them in Build-Depends. File statusnotifier.c still includes their headers, but this file is not mentioned in CMake scripts and does not affect the result. So these dependencies can be safely removed with no harm, and binaries remain the same.
We believe that the bug you reported is fixed in the latest version of
qtox, 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 967718@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Nicholas Guriev <guriev-ns@ya.ru> (supplier of updated qtox 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 ftpmaster@ftp-master.debian.org)
Format: 1.8
Date: Tue, 28 Jun 2022 21:53:37 +0300
Source: qtox
Architecture: source
Version: 1.17.6-0.1
Distribution: unstable
Urgency: medium
Maintainer: Yangfl <mmyangfl@gmail.com>
Changed-By: Nicholas Guriev <guriev-ns@ya.ru>
Closes: 967718 1004815
Changes:
qtox (1.17.6-0.1) unstable; urgency=medium
.
* Non-maintainer upload.
* New upstream release.
- Compatibility with FFmpeg 5.0 (Closes: #1004815).
* Exclude unused build dependencies, libglib2.0-dev, libgtk2.0-dev,
libgdk-pixbuf-2.0-dev (Closes: #967718).
Checksums-Sha1:
8a1b50c7634a22cbc738aebbfb2dcce203937b87 2254 qtox_1.17.6-0.1.dsc
7ec6356da1c52cfe39c2cdfc3587664543ec9248 4777590 qtox_1.17.6.orig.tar.gz
4ca299df443033b2a006744bf9b8093b3b0d7bea 833 qtox_1.17.6.orig.tar.gz.asc
12172ee98f41ab132445f92fa82fd36987e190f3 20316 qtox_1.17.6-0.1.debian.tar.xz
7274db7bc48dc1f567b62db79396b2a308afcd73 9373 qtox_1.17.6-0.1_source.buildinfo
Checksums-Sha256:
59d13353449deee481d99997307cfc1dfa5c8f0c01989310d79b22326b67512b 2254 qtox_1.17.6-0.1.dsc
3900764667319baa8a0da95e051e0a6c167f9c2c67e4b9c98d108f7b7bf888d6 4777590 qtox_1.17.6.orig.tar.gz
d9c54cbca379bdf3746e1550d852d1016c2020b9397049dbbf90bee4ce244703 833 qtox_1.17.6.orig.tar.gz.asc
6f1c97a7cf50c9ab47524384677dd78a4bd0a8cd10181c3f0ddc84d0a34abcd3 20316 qtox_1.17.6-0.1.debian.tar.xz
c252e73fae761ad1c39154c6c2b1285680e302cacc4300127f0290a6e4d315f3 9373 qtox_1.17.6-0.1_source.buildinfo
Files:
f072bef79f7130cb2fa83ec42680033a 2254 net optional qtox_1.17.6-0.1.dsc
0bf7bc4133b55e1acf8c800c64e1f1c3 4777590 net optional qtox_1.17.6.orig.tar.gz
5c3c3b081f128f43dcbce43bb4aa3c1e 833 net optional qtox_1.17.6.orig.tar.gz.asc
996ee3a0c22a2bee8b6ccd815bd216d0 20316 net optional qtox_1.17.6-0.1.debian.tar.xz
7b374aed7c8f562a480402104002f28d 9373 net optional qtox_1.17.6-0.1_source.buildinfo
-----BEGIN PGP SIGNATURE-----
iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmK+tmsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOdeC/wJKeaTnhSzdXtE5JThOBpACdU9NAzf92ld
NYl/gsgJjgF6jPmWa5gMG/SVFbY8UtBhAfEWmE7K9Bl9Ax3+5YPokmkk2AkEn5jU
yOHSLTlRvbA6RZ6D1XgcY87G+5WtN50Z9vinTixsSCPuNuFfgLDxiC4MENFWyZbw
xmGZppDn+rJ4fH+Q90cstqlmKn4qpoRFZFfXy391VgXlDveed6w97hrUKx49jmrE
KJtcreQlKvd0bMedMhNsKq9HRYEQodq1eO5lN4O9zHzXt7W/KYTbjSl1Prs0ib5j
OcbT+mEbWOBwrPXGEkvmwGrF4igu7DOPbzUL/GFSdGYlUSFxUo+FTyWkTihJgrWC
ExDR+aBLcTY+3aeWbGd3BFcmlNuIzj0MJed1HIUW6qPuW2akhLOxMUXzEx6H6lpy
vy1SBeAYLcW/DfF0JCgi60a9KM5DzVrF56fdjvKg5xGKjjvqNm3cR5loLZ5O27Ps
G4UFSUxp99FfKf+0ywt8dBEboNucVqY=
=hsV4
-----END PGP SIGNATURE-----