Your message dated Mon, 12 Jan 2026 09:04:14 +0000
with message-id <[email protected]>
and subject line Bug#967267: fixed in basilisk2 0.9.20251105+dfsg-1.1
has caused the Debian Bug report #967267,
regarding basilisk2: 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 [email protected]
immediately.)


-- 
967267: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=967267
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: basilisk2
Severity: normal
User: [email protected]
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: basilisk2
Source-Version: 0.9.20251105+dfsg-1.1
Done: Alexandre Detiste <[email protected]>

We believe that the bug you reported is fixed in the latest version of
basilisk2, 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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Alexandre Detiste <[email protected]> (supplier of updated basilisk2 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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Mon, 12 Jan 2026 09:34:15 +0100
Source: basilisk2
Architecture: source
Version: 0.9.20251105+dfsg-1.1
Distribution: unstable
Urgency: medium
Maintainer: Jonas Smedegaard <[email protected]>
Changed-By: Alexandre Detiste <[email protected]>
Closes: 967267
Changes:
 basilisk2 (0.9.20251105+dfsg-1.1) unstable; urgency=medium
 .
   * Non-Maintainer Upload
   * Switch to Standards-Version 4.7.3, drop Priority: tag
   * Build with Gtk3 (Closes: #967267)
   * Add patch to fix build with Gtk-3
   * Add debian/salsa-ci.yml (can someone please enable Salsa CI ?)
   * Start migration from CDBS to short DH:
     * install the documentation with debhelper
     * rename files in debian/ for forward compatibility with debhelper 14/15
     * install more files with basilisk2.install
Checksums-Sha1:
 176e4d571ab09eb95bfde165a4e7010584db91b6 2252 
basilisk2_0.9.20251105+dfsg-1.1.dsc
 0cc22ef2c2a04f0c366e4ffff0633d61cd2b54cd 160952 
basilisk2_0.9.20251105+dfsg-1.1.debian.tar.xz
 e9c2b8bc47279d265b2da0a4dc44dd457aa42d78 15900 
basilisk2_0.9.20251105+dfsg-1.1_source.buildinfo
Checksums-Sha256:
 3594a5925803dd473363ce375aed756214b98f0dee84e22fd4778a61009dd0ea 2252 
basilisk2_0.9.20251105+dfsg-1.1.dsc
 932bc37ffd207616ac6e3e958ddf1f6eab6ad262e0af38f2f54abd5db8311c13 160952 
basilisk2_0.9.20251105+dfsg-1.1.debian.tar.xz
 194eb5c79a146bf71573a2b709770fbc1b2558c73c55a187f843ad764368a461 15900 
basilisk2_0.9.20251105+dfsg-1.1_source.buildinfo
Files:
 5c335095ee095ff4149f858c2123bd13 2252 contrib/otherosfs optional 
basilisk2_0.9.20251105+dfsg-1.1.dsc
 f6da08a6bd00211ca5b14ed397f90aec 160952 contrib/otherosfs optional 
basilisk2_0.9.20251105+dfsg-1.1.debian.tar.xz
 b4b57b9648af144a99ad1d4ff7f004ad 15900 contrib/otherosfs optional 
basilisk2_0.9.20251105+dfsg-1.1_source.buildinfo

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

iQJFBAEBCgAvFiEEj23hBDd/OxHnQXSHMfMURUShdBoFAmlks2ARHHRjaGV0QGRl
Ymlhbi5vcmcACgkQMfMURUShdBpGRRAAwuPghIrBMWD6CwxC3wOQ0Fyy+TGRLZlt
sqNzqxunoPWD9XUxZdzVh0fw4va4zd5yl9Hd2j+ODHa1De4bGD/6MSyZoHMAlFli
aj3DF93gAuHcMRc/j8EglB4T2yLOcGRlBwOU/OodewaGx3Bj9lmZUfvBPm/orYiH
6lY7XWWTZsIFvkQuq7T/32CUi0dK+zBIc28HEFjOmNbIfkSgL7HWA1b7d+Vcxmxu
94WyeGlZ46Jy1OB3+x5MqPUL7ejhF8rk22Qa4MekpxSJWhmiYfXeTGvlQTthkK/h
SgjCqJG1wK1iChnwv8vcww0XNdary33WhGfnNQ8bH9i0WRU73e4ed7e4ikOsf0KR
edmmh1Vxou4uLenFEoePBHfRftl0tb4n+UlS3OR7iHmrKg9sMPNsQq5bOO5lUBu4
HK97StF40L6yAbl9HNFNaGGvEZl7tIQR80C2liSX9drXGjA+x06K9m3q9lz+QqAp
KcGas0aFokkmn2Gtpib0GYBF1TT2PT6jOr6y0oVYiEhdrcgvtTig38msk/lWvTy2
YRv1iOItq3AL0YoxAKs3Q9wtP3naKRch/OJbUKNXjN0nSc3Osc2076vAmcAYrRXi
yGuxW1VwGIdvrTYOzxfZCTxBiUsDOHtpEUE4wKGcHFEHiGtruckkzDCsBiL4zkEE
M07rOuvXsE4=
=8vb1
-----END PGP SIGNATURE-----

Attachment: pgp2_fYS9T8Xo.pgp
Description: PGP signature


--- End Message ---

Reply via email to