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

Bug#967551: marked as done (kasumi: depends on deprecated GTK 2)

Your message dated Sat, 28 Oct 2023 10:19:43 +0000
with message-id <E1qwgPv-00GOIi-QI@fasolo.debian.org>
and subject line Bug#967551: fixed in kasumi 2.5+debian1-1
has caused the Debian Bug report #967551,
regarding kasumi: 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.)


-- 
967551: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967551
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: kasumi
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: kasumi
Source-Version: 2.5+debian1-1
Done: Boyuan Yang <byang@debian.org>

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

Debian distribution maintenance software
pp.
Boyuan Yang <byang@debian.org> (supplier of updated kasumi 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: Sat, 28 Oct 2023 05:46:52 -0400
Source: kasumi
Architecture: source
Version: 2.5+debian1-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Input Method Team <debian-input-method@lists.debian.org>
Changed-By: Boyuan Yang <byang@debian.org>
Closes: 967551
Changes:
 kasumi (2.5+debian1-1) unstable; urgency=medium
 .
   * Team upload.
   * Incorporate changes from GitHub GTK3 port.
     + Migrate to GTK3. (Closes: #967551)
   * Generate Debian 2.5+debian1 pseudo upstream release.
     + po/ja.po: Converted from EUC-JP to UTF-8.
   * debian/patches: Dropped, merged in the release.
   * debian/copyright: Updated.
   * debian/gbp.conf: Dropped, useless.
Checksums-Sha1:
 c08d56ce8df11c1fc1480d053b40f96c49c16fa8 1913 kasumi_2.5+debian1-1.dsc
 e3f67cc2ea4c50b91d12e5f83d7a33f366ed03f5 52964 kasumi_2.5+debian1.orig.tar.gz
 7a672b7475717b9605c3b7d463cfcb1cb20771e7 4588 kasumi_2.5+debian1-1.debian.tar.xz
 b58509917658e8b87a192d07e5aabca4d6a6b92e 15269 kasumi_2.5+debian1-1_amd64.buildinfo
Checksums-Sha256:
 bca0029ff67c8daa9336a44aa523a26615422e0dc2968e57c64a1f0317bd772f 1913 kasumi_2.5+debian1-1.dsc
 a0aed61cde97dcbda6de70b0645e0910ccdfb9ce2eec5dfc33b4da9ac88f6575 52964 kasumi_2.5+debian1.orig.tar.gz
 ac2eef2b1dcac66dbe68046f5fdda6b10b82aae3dcf7a3945c606aab406fc10f 4588 kasumi_2.5+debian1-1.debian.tar.xz
 32ab7d6735a9234e052fdc993db129ea272cb46b2b043f5284d65c229ba523f1 15269 kasumi_2.5+debian1-1_amd64.buildinfo
Files:
 2901e55cd125b8d23f390f7ef2d37a98 1913 x11 optional kasumi_2.5+debian1-1.dsc
 d6a3ff3ac63ffdcbc55e346954bbffa7 52964 x11 optional kasumi_2.5+debian1.orig.tar.gz
 c6b866652c85905fb38e58d021cd42a4 4588 x11 optional kasumi_2.5+debian1-1.debian.tar.xz
 6647b27546ae1436505333e0909dbcd6 15269 x11 optional kasumi_2.5+debian1-1_amd64.buildinfo

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

iQIzBAEBCgAdFiEEfncpR22H1vEdkazLwpPntGGCWs4FAmU83AMACgkQwpPntGGC
Ws7t0w/9FgH79RSsK+bx64rLew5EuOLszzLmygZu2XyvUmCNjt5jWB2MqtDugNnD
zgBlBRgMvJYdAidGY3AEyLkBNvfBHbXsM3tIVERpNgSzdHg1Tk8IRypny+tNTCd3
ufFldouSNJq5C/hknbDwefmtBLMnf8b0xNeuNpyZMeyS84yoxlyXftTRcE3AC8ZD
NiYgK2+uiZn0vCsIDkOx2C4oiChgwEmhz4NPM6IGqutCf9QEWRidCVqyW+XYt5EH
/7ckWlhJ7uIq9IV0yNIZ2GXug2GMnrZxTkyKp2eMTzUD6TnUgrKZv3Hfy/jUR7MO
UrzWUZ8vvkesOFpyb7DUdybmIpcd/LiiHvrnbtk5z9NeszDkjXkSN+txdVC7ojSv
/738N97RjRqbnMR60vcbW0NfHFmMNxzN+I2Ie3vazu/6eNhYbDJJni5Bb7C/vegf
AIFi/OCDz+EqLGzCrKPf+dI0/tUY5/DN1pI+LVYAjhAXT+rkOEYk0PmLPKhB5NZ5
4KlHEa0k+Fjbmsrr3+LJ78orndC3UZkqj2auejcJAbI9horwLUzETdDQttSVcumh
nIblW4prg8aRcSCB7NZJ994kkJ1lgH4yQ/BY+HPfq3q8yWZksUNBqw2/inxIMKqp
ZwDmysLjhtasvS6vtizxuiJ55t7SncxZtlAYXALaxbJtM+M414M=
=oO0f
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: