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

Bug#967801: marked as done (whysynth: depends on deprecated GTK 2)

Your message dated Mon, 18 Sep 2023 12:55:10 +0000
with message-id <E1qiDmQ-006ywO-Kh@fasolo.debian.org>
and subject line Bug#967801: fixed in whysynth 20170701-3
has caused the Debian Bug report #967801,
regarding whysynth: 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.)


-- 
967801: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967801
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: whysynth
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: whysynth
Source-Version: 20170701-3
Done: Bastian Germann <bage@debian.org>

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

Debian distribution maintenance software
pp.
Bastian Germann <bage@debian.org> (supplier of updated whysynth 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: Mon, 18 Sep 2023 14:26:37 +0200
Source: whysynth
Architecture: source
Version: 20170701-3
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 967801
Changes:
 whysynth (20170701-3) unstable; urgency=medium
 .
   * Team upload
   * Drop GUI (Closes: #967801)
Checksums-Sha1:
 ab41b23e9436ca6054fed29b779e99ab5e0e02d7 1886 whysynth_20170701-3.dsc
 7d9364fcccadebbc8425aaba9a345df0bc555f94 3304 whysynth_20170701-3.debian.tar.xz
 dad830088831e29641ca3593f5f379da9073a268 5533 whysynth_20170701-3_source.buildinfo
Checksums-Sha256:
 14bdf3ac6d6baecbcd462d99137b833cd6ccac80187538c36e07cdc95d6118a8 1886 whysynth_20170701-3.dsc
 44b4aaabbf4a379e8870c7967061d3879fdab21d1de36215ace6ca28312cbbb1 3304 whysynth_20170701-3.debian.tar.xz
 594e21a486fcaa510d8c7870e5e9db08336506aea6a2a78e49a9286ac86e3636 5533 whysynth_20170701-3_source.buildinfo
Files:
 95c4b5e36931cdd7237077e6e2f33e18 1886 sound optional whysynth_20170701-3.dsc
 97650ce2cb6591d47e81be1e18c42d3f 3304 sound optional whysynth_20170701-3.debian.tar.xz
 9e1a1bfe5ae8d74948b7c9becd4edd26 5533 sound optional whysynth_20170701-3_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUIQkkQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFOD/DADZET/k7vYQSw6joZFQytDQKr8HIunAfgk0
RlDnToraD4F7iU1wdZuB4xJCnNVGC/dn6pXirISwZAkO9qxHdqlGlTB7c3o8IfKx
VE2OpkaUwakASuDp1S+PCRZNiv1EA5dpabEyBn0TQBq7FoouW6h5D6F8rUc2Lmh2
a62FwJzAgDseEQoOCE/rRNkpiC3R0fuEpuSdS4mxOCzRiD9eiOidkehb9+ujJdQt
6i+zPJac68Bi+s7Qu5H8tx+Th3pOw2iT0gfTOVS32/aEFsnwKBq16ZbsPQrqtqdi
VQgvHCtSp04CSpEIiTJ+K154cacraMZBjielwihYFeM4FaXCb+suMz8IKhgL/zKw
B736Wn6AQkfzM4eUCkUz0Fwe6nZzXCeStMb3x8dpWkgGvTYvv4zlGWmmli8vnl6D
SBETd1VoSLukjAf8aY1wicgPrn4rB4mW6yhDV8tvF+XuIbZeo3bGv8TXWfKPmmdn
X8l8OwHHfaKPgjKVsU1JGk3CvG78FGQ=
=rIZO
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: