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

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

Debian distribution maintenance software
pp.
Jörg Frings-Fürst <debian@jff.email> (supplier of updated xsane 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)
Format: 1.8
Date: Sat, 22 Aug 2020 20:33:33 +0200
Source: xsane
Architecture: source
Version: 0.999-9
Distribution: unstable
Urgency: medium
Maintainer: Jörg Frings-Fürst <debian@jff.email>
Changed-By: Jörg Frings-Fürst <debian@jff.email>
Closes: 963185 967834
Changes:
 xsane (0.999-9) unstable; urgency=medium
 .
   * debian/copyright:
     - Add year 2020 to debian/*.
     - Fix tag for po/de.po.
   * Declare compliance with Debian Policy 4.5.0 (No changes needed).
   * debian/control:
     - Switch to libgtk-3-dev (Closes: #967834).
     - Use debhelper-compat version 13.
       + New debian/not-installed.
   * Fix lintian breakout-link warning:
     - debian/xsane.install: copy xsane to plugin directory.
     - Remove debian/xsane.links.
   * New debian/patches/0925-utf8.patch: Convert to uft-8.
   * Refresh patches.
   * debian/xsane.install:
     - Copy xsane-startimage.pnm into /usr/share/sane/xsane (Closes: #963185).
Checksums-Sha1:
 3b4ec7e8f5671ec5ae838181b5c777508e91851d 1947 xsane_0.999-9.dsc
 6b56143ef0d840967ec4c09428396e5f28a811c4 129432 xsane_0.999-9.debian.tar.xz
 0920b1ae0d3d7ed156e0d2988adb0293e53b826c 16284 xsane_0.999-9_source.buildinfo
Checksums-Sha256:
 bc6b4a1c0a87ef1e630571254a18e203178382f3d921f8d328617e5c93abbe72 1947 xsane_0.999-9.dsc
 5ef573aa0e5398640cb4a632ae15d7e3d7dd41bb131a16f6b4e09288968f54c5 129432 xsane_0.999-9.debian.tar.xz
 19ee5fd0c1e64031d4cb63e75a25cb1c2e6392bd2f985cc4174e3e6b295df3e1 16284 xsane_0.999-9_source.buildinfo
Files:
 47d03bd4b25d4596ed4456049f3473b7 1947 graphics optional xsane_0.999-9.dsc
 e090872dd10d0c44e7898928776ed1a3 129432 graphics optional xsane_0.999-9.debian.tar.xz
 7b9ecafd3a02b3bbf0dd53ff60f48e0a 16284 graphics optional xsane_0.999-9_source.buildinfo
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkjZVexcMh/iCHArDweDZLphvfH4FAl9BftUACgkQweDZLphv
fH60jA/+ITDRxzZM5H14jygGtSr4AcBzcFB5mTXYmuX/H6ElDUYsEuN+1X19V0Ir
8JhvXUtcxPif+sVA2kd66g8EktYHiZhCqGKVCOOZJBWyMLQiLDdlnsinQXMN7s2e
isNAwcX/7ofzicN8crhhqYSgLSxfZpmvk0pQ2gIGenvmWImwv+uIob0ioTloudSY
CMVJ0Ks7UEiy7QfaKwH8/A+qQl399pBCLp4riGRvER/Nob0fWUm3hlIx/90z46KT
l8hBgGkF7jQ4OZWelqDfjhzwAT/BkN/EtJCUPOdzl+BdraJFs7TbaS3sPHIlblGj
38/UPY48ovxKo/tmunm3XnOR+KUWGtyh2CktXLOKh12YINrHPUyuMYJMqqonmeSh
gMsNq9jNloX6oInwTm5SdHWgZbJZA4Bz6y0RHgcr2/V5cgXPF+SRZD8o8rdeJ16s
GDgCiU75R0aBerRs/IYvvx4Dqz6vL8RU9KY/ISiIDiVviFM+NtaoJLkKvgbxaWp2
HXTB/G8MIoinIRRDPns5PMvrB6XvIwSufviMcdXR3wGlabQiOgTw5YU/e60ewqr4
33ppH9rr/LccDRQrHIOyZVLZWE+SAMWRGsC4eJQxkqAO5BDg+RtVLZIxkhlSfHLx
fpUlQD2bVDKCboVZArZ10lUbQ+tBvr+RoJFbD6S4pqi9/4qq+Cs=
=cRmK
-----END PGP SIGNATURE-----

There is a branch at https://gitlab.com/sane-project/frontend/xsane/-/tree/gtk3_porting

As announced [1], we are trying to remove gtk2 from forky. Therefore,
I am raising the severity of this issue.

[1] https://lists.debian.org/debian-devel/2026/01/msg00090.html

On behalf of the Debian GNOME team,
Jeremy Bícha

Do we have a fix for this? It seems we need to either re-write or drop
ClassicLadder.

unarchive 967834
reopen 967834
thanks

The switch to gtk-3 was never effective. The package was still building because libgtk2.0-dev is installed via
libgimp2.0-dev.

Hello,

Bastian Germann, le mer. 11 déc. 2024 20:03:01 +0100, a ecrit:

The branch was merged, the master branch now uses gtk3.

Last 0.999 release was 6 years ago, I guess we'd have to take a snapshot
of upstream.

Samuel