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

Bug#967584: marked as done (libiodbc2: depends on deprecated GTK 2)

Your message dated Mon, 17 Jul 2023 14:37:53 +0000
with message-id <E1qLPMH-00FTT7-Pj@fasolo.debian.org>
and subject line Bug#967584: fixed in libiodbc2 3.52.9-4
has caused the Debian Bug report #967584,
regarding libiodbc2: 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.)


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

We believe that the bug you reported is fixed in the latest version of
libiodbc2, 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 967584@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 libiodbc2 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, 17 Jul 2023 16:09:27 +0200
Source: libiodbc2
Architecture: source
Version: 3.52.9-4
Distribution: unstable
Urgency: medium
Maintainer: Debian QA Group <packages@qa.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 967584
Changes:
 libiodbc2 (3.52.9-4) unstable; urgency=medium
 .
   * QA upload
   * Drop iodbc package (Closes: #967584)
Checksums-Sha1:
 122d880b79984d24b7ecf7d478a78a01efec19c0 1793 libiodbc2_3.52.9-4.dsc
 b125fb93be75981ba40e9396c7f8e0f603191957 9448 libiodbc2_3.52.9-4.debian.tar.xz
 1975e92c6f0b5a8cac2095897f37b0fedebdd087 6038 libiodbc2_3.52.9-4_source.buildinfo
Checksums-Sha256:
 683e0a377071412fed62fc365b455e7f89e0609d32daff9bd7193518f13d4ce3 1793 libiodbc2_3.52.9-4.dsc
 4a746836c382ad78fdc77ca08b000f45158b3a0624a594df31ae96b06bd322cf 9448 libiodbc2_3.52.9-4.debian.tar.xz
 c3d0655c1b88cf6d14103b7ee32fb5ad085a88cca2b973edddfe02d86c3c7fec 6038 libiodbc2_3.52.9-4_source.buildinfo
Files:
 75ec79c33a239e4b516bc79a3e981168 1793 libs optional libiodbc2_3.52.9-4.dsc
 f28c59ee365edcdd97afa3e59bd3d20e 9448 libs optional libiodbc2_3.52.9-4.debian.tar.xz
 0b2b50cc11e13cdbd426e455e35cb064 6038 libs optional libiodbc2_3.52.9-4_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmS1TXsQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFJ43C/96AU56HPRET74oLLQqRPIMaF1Kqq6eBwR/
S09fQSgOphAfM3Ry2cbY7FZ1wO5LdNN4aJo0nlfuZUt+HPiZLbZo6tGeW5+zxfuM
LpwskUJIG23BFvckPYvZby2onO1j48BpnwudvP7bgXkk4A996FODk9Ddl86nJRv1
aCVdlMoRFVnf/hW+DinrAKR8OGYrzbqXwxK4c9/GeoJN5u8+jziPlk7XD9TVUL6d
42U5jr9mO9pvHa3SDr3E/0zJ2QpmBTUoYTDiWKzqDLTSx6rIK+7YyEGSGjzaTuUW
yYOavbCP0FZAaTh5GJhmefXQvfWj63HdM28IwGUucIJaY+/r1aawkVAfLiDs0P5l
wnfUmHCz6GEkDcbb0RzoNwFifAwQdR1MZFQQFP60Zag7heOXKWQV/T8X9kC1wK4h
shZ2OS+lD2iqmQiQi0P+DFlSF/bzlljEEPHV7YdmUu40ewUfsmfmyC5aDbkfaCGy
X6fzJwa9ljYLiOHSOmz1LusD7dYCNYg=
=nxKy
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: