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

Bug#967704: marked as done (planner: depends on deprecated GTK 2)

Your message dated Mon, 02 Jan 2023 01:35:38 +0000
with message-id <E1pC9jm-006rHj-6q@fasolo.debian.org>
and subject line Bug#967704: fixed in planner 0.14.91-1
has caused the Debian Bug report #967704,
regarding planner: 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.)


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

We believe that the bug you reported is fixed in the latest version of
planner, 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 967704@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 planner 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: Sun, 01 Jan 2023 18:59:47 +0100
Source: planner
Architecture: source
Version: 0.14.91-1
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 967704 967882
Changes:
 planner (0.14.91-1) unstable; urgency=medium
 .
   * QA upload
   * New upstream release, dropping all patches (upstream or autotools-related,
     Closes: #967882, #967704)
   * Build with meson
   * Drop planner-dev package
Checksums-Sha1:
 e107ba6f10986ac53160319e3826c7e1daddbf1b 1841 planner_0.14.91-1.dsc
 c805760753e06b930a5d8016c25801798d2e1fa0 3887084 planner_0.14.91.orig.tar.xz
 7fe88fda19198e775d4b7255eae5212b4f7cd544 12488 planner_0.14.91-1.debian.tar.xz
 b185a22e7cc64289de7eb71740b777b2330804d7 15131 planner_0.14.91-1_source.buildinfo
Checksums-Sha256:
 8b1dae4b22cbe713e6a82d182fbda156739c02634161d815aeae795e9ce2bc3f 1841 planner_0.14.91-1.dsc
 1efa58290b112a28ef80c1a850c69ce903b80612b488d2a5848fd1e0094d5ae7 3887084 planner_0.14.91.orig.tar.xz
 80a877c33d28b64b1611ea22971439484599f81c23a1c3fe739d8a6a267251e3 12488 planner_0.14.91-1.debian.tar.xz
 0f466566352af5ec48a2e5723e97c6d843579934d2cf2a8b464c96a00621c5fd 15131 planner_0.14.91-1_source.buildinfo
Files:
 b2523e549c41313379bf5e7d4e9db775 1841 gnome optional planner_0.14.91-1.dsc
 37bea29812a672d1c00918bbe6474b8e 3887084 gnome optional planner_0.14.91.orig.tar.xz
 7ac95a0c187fc9a4f20d79c7a061d057 12488 gnome optional planner_0.14.91-1.debian.tar.xz
 13c7bdbf62b0ebfb56f274b0151f4fe2 15131 gnome optional planner_0.14.91-1_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmOyMF8QHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIlxC/4rTtjC64LbxaLiqa8Acc3rjGPte4fq6sdi
yINtktWWvG+wulU6qBluXBmFS/mutc2M/A/LJnc8KXwpMpOF11lilXaG3ppMGs6C
i/+2hzMs0MFgbIUU0mkxteieZBEzI/V8HeNLIZp44n52KoOU3PPw+SltMRPlFpyk
LbYAy4g2xv7qlCFd0NCAuACAQCuXgCSP0TDGuU17x5HemQ1oEEPqylVLCliim+Cr
9hB0kc5EjDv3GIRdmhfI+OqqWeCELWjwPc2KlKMcZCkH8AAzUpb2H4fhEwJg0Qa5
UGzcN0Jn3cdx2lX33VuDetSX1Qb+LgAPvbttwwFwBGzGBFEPt44WT0Xl6fCdfdVU
pQB5ojnoVt5qrGvi6in65viXzK76WuW++ftXlxvG5Xw2SqurPcignjnzqifB68Ff
ycs5r4xW2byIVKJ/AhMwioKyhqCNkMDPusZoZ3jJZTMrUguxhreT5FOqEhjghLtf
1tyuJoBCEOOFkY7PSK4+YvBb4tZ5AYM=
=4iX+
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: