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

Bug#967344: marked as done (fluidsynth-dssi: depends on deprecated GTK 2)

Your message dated Sat, 14 Oct 2023 13:49:26 +0000
with message-id <E1qrf1C-00E2gN-4H@fasolo.debian.org>
and subject line Bug#967344: fixed in fluidsynth-dssi 1.0.0-9
has caused the Debian Bug report #967344,
regarding fluidsynth-dssi: 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.)


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

We believe that the bug you reported is fixed in the latest version of
fluidsynth-dssi, 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 967344@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 fluidsynth-dssi 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, 14 Oct 2023 13:23:19 +0000
Source: fluidsynth-dssi
Architecture: source
Version: 1.0.0-9
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 967344
Changes:
 fluidsynth-dssi (1.0.0-9) unstable; urgency=medium
 .
   * Team upload
   * Drop GTK support (Closes: #967344)
 .
   [ Debian Janitor ]
   * Use secure URI in Homepage field
   * Fix field name typo in debian/copyright (X-Comment => Comment)
   * Update standards version to 4.6.1, no changes needed
   * Remove constraints unnecessary since buster (oldstable)
Checksums-Sha1:
 8ea99ae520432bd8c8c5a5e70edf0a02c6e28fce 2067 fluidsynth-dssi_1.0.0-9.dsc
 1dcd4e13318036106488b570af5f0ef9cbb3e14b 6128 fluidsynth-dssi_1.0.0-9.debian.tar.xz
 826a33127c018b0d6a389a64b99d69c1919a6d02 5877 fluidsynth-dssi_1.0.0-9_source.buildinfo
Checksums-Sha256:
 93d5a5e76651754a6810bda7a955d80de15d8abf38a620677e86627994beeaa5 2067 fluidsynth-dssi_1.0.0-9.dsc
 80f73408d6b98cdec71546897b16129e1e19a8ea633458f32cd6c27d5a935709 6128 fluidsynth-dssi_1.0.0-9.debian.tar.xz
 65916cae01725a129e596c3c8efd32e751c60647705a90314b151cde8f377879 5877 fluidsynth-dssi_1.0.0-9_source.buildinfo
Files:
 72f923f38721a60b91a8bfa67b0c46d9 2067 sound optional fluidsynth-dssi_1.0.0-9.dsc
 21b6d95a5d88ca6515e4ac3d9d0f9c0b 6128 sound optional fluidsynth-dssi_1.0.0-9.debian.tar.xz
 60bcfac76031a4f8dda3bb07483bd62e 5877 sound optional fluidsynth-dssi_1.0.0-9_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUqmtMQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFInfDAC7pqLThuqf62GjUal5PKQFK2FzDVCmj2AV
/bryCNkC66AHi1R/EoQxrEu63rw1xFwZma8pHMdHm/p9JwmRGYVWn57dbuEjkDYx
lzY830CrLtrS1WqguhZETJWbeNEentn1pR7VCLDbIzEeuTIT5O2wHOH4VtnFxAbL
LicCkNs9FzAW/aD/jcR4+QkPtx/9GJDtv+zse3q0kg3icIq1A34g2tfKMuIjawSI
pVv0g1WwIC9tB9L3A5Nir1a0rESeab+fae/1rFzd82BWyneDgDVhEQpNc+LfeVVp
d5vUd0RU/L3e4nM0ysrfTRUX544YZRHKaPuNLdoIKmISHyd8vWFRlGeB2MV2jSXW
LBnXoBAFbj/41NsQaJwVduyR+/399ezJoWkqMVaT/w1HWZFRdCBcGaG+FGlMYKAo
LZa9zestsxNhAN42kvcD2NbT2Cc+ZVq4qoKTAvabIeylcCTd2NRPiHtRmSKG1jlS
wg1iygzZWW8hzJQi3h9wkgjYD9+jqjs=
=nbK4
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: