[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#967784: marked as done (tucnak: depends on deprecated GTK 2)

Your message dated Wed, 13 Oct 2021 20:51:42 +0000
with message-id <E1malDy-0005OL-BA@fasolo.debian.org>
and subject line Bug#967784: fixed in tucnak 4.32-1
has caused the Debian Bug report #967784,
regarding tucnak: 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 owner@bugs.debian.org
immediately.)


-- 
967784: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967784
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: tucnak
Severity: normal
User: pkg-gnome-maintainers@lists.alioth.debian.org
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: tucnak
Source-Version: 4.32-1
Done: Ondřej Nový <onovy@debian.org>

We believe that the bug you reported is fixed in the latest version of
tucnak, 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 967784@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Ondřej Nový <onovy@debian.org> (supplier of updated tucnak 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)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Wed, 13 Oct 2021 21:54:45 +0200
Source: tucnak
Architecture: source
Version: 4.32-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Hamradio Maintainers <debian-hams@lists.debian.org>
Changed-By: Ondřej Nový <onovy@debian.org>
Closes: 967784
Changes:
 tucnak (4.32-1) unstable; urgency=medium
 .
   * New upstream release.
   * Bump required version of libzia.
   * Switch to GTK 3 (Closes: #967784).
   * Drop d/p/gen-intl.patch: Applied upstream.
   * Bump standards version to 4.6.0.
Checksums-Sha1:
 2112a50e474dd1866eb7cd0685f383679c0002c2 2130 tucnak_4.32-1.dsc
 ca3ebe51b32792a3944d7d0417d0e954207268c0 3595195 tucnak_4.32.orig.tar.gz
 bd1fe695ac9ffe62723b7d90c52fda6236144e77 5852 tucnak_4.32-1.debian.tar.xz
 068c60dbb9ebd1344a0dd8d82ef8f763172332a8 15624 tucnak_4.32-1_amd64.buildinfo
Checksums-Sha256:
 e572b7c30dcf5ba87c5d19dc43be0e05de98286f84d4abde7a9a56eaa08b6605 2130 tucnak_4.32-1.dsc
 fb359d1bff288c0c820c3cd5087ed6601895d903143f16cbe9e5d9ce07082540 3595195 tucnak_4.32.orig.tar.gz
 a40c237321b2ee2ee16b9e05f3b75093d7dfc5b4e98f152cfff663d20e1d6278 5852 tucnak_4.32-1.debian.tar.xz
 6760cfc00524b1f58f9d78e1c5f1ddf1682bdc9aa53e08ef953288d45b05cd11 15624 tucnak_4.32-1_amd64.buildinfo
Files:
 0a32c3d28de7cae6cfe782d94c1888b2 2130 hamradio optional tucnak_4.32-1.dsc
 44a6f42fe13964972114c09fc9228b99 3595195 hamradio optional tucnak_4.32.orig.tar.gz
 27f8df763b3d98c7fd24067968f67289 5852 hamradio optional tucnak_4.32-1.debian.tar.xz
 4050e7664f6c399e372834005a98ea6e 15624 hamradio optional tucnak_4.32-1_amd64.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPZg8UuuFmAxGpWCQNXMSVZ0eBksFAmFnP5QACgkQNXMSVZ0e
BksySg/+MBqA9Cgv9+2MmhLJm0tgs428VWhQzDhRKG4PMU3Ms5RRg9K+UuFsVgOb
WAX2CUoe7URKQ2aDgq2biLeQ33JFPZW3LMj5Tc+H2WbM4U7gSaVwHVTnIxF9k9W2
gpNwnseeQv7CZBhIMb15lHUjJ7LNFgrC6KiibtKQiewJfDdg85D/lttBB2+BxHVT
9ucgNgQUlKors2tJ1yMPQZo4pgLxDLCMAyfU2pxPiuKkBC3vP6Nd1HDnadIqrFqr
v+F3dWb65w7VTSHN8KYLZkWj+u46KWUPUCCEReCvnpsI3u2FUaPuyHVAuO9fM10d
b+GAei2EGcq/O5/gjRNCWDWeksMDfaK1CpbFjrL1/JNZ1LP4P6cnnmeHByYjU6w2
42OMphnE5SH/j0RBchrPnD6bE7F1t5B23mkX2EgMTDhacQ/2kMmqgZXHiFZB2/rM
PBY2wCvPxyK9nJEBH/bc/ttsm17OTfVcyqRjRRBSId6g0ILx3xuijDTNlIBKmgAI
vm3TOCxl0AHmX4Z1YJUMlawxsJWtv1TSCvmVmiXYo2TjKZT37RFWIYtrYvldGq18
5MX06lkFqtqz1dHgjYrGLnYOtSK7agNOQqr0Y+8gE8jdcZaKQll3mGXtQONagfCq
ZFDIwlD3tn0/yHnjzcHJ3Evu+N/ajnctxaaLJVEPCW+05vIfGnE=
=/Why
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: