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

Bug#1041795: marked as done (eq10q: depends on unmaintained gtkmm2.4, and indirectly on GTK 2)



Your message dated Sat, 14 Oct 2023 22:49:17 +0000
with message-id <E1qrnRd-00FsBl-DX@fasolo.debian.org>
and subject line Bug#1041795: fixed in eq10q 2.2~repack0-5
has caused the Debian Bug report #1041795,
regarding eq10q: depends on unmaintained gtkmm2.4, and indirectly on 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.)


-- 
1041795: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041795
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Source: eq10q
Version: 2.2~repack0-4
Severity: normal
Tags: trixie sid
User: pkg-gnome-maintainers@lists.alioth.debian.org
Usertags: gtk2 oldlibs
Control: block 947713 by -1
Control: block 967497 by -1

eq10q Build-Depends on packages from src:gtkmm2.4, a C++ binding for
GTK 2. GTK 2 was superseded by GTK 3 in 2011 (see
<https://bugs.debian.org/947713>). It has been discontinued by its upstream
developer and no longer receives any upstream maintenance at all.

The direct replacement for gtkmm2.4 is gtkmm3.0, a C++ API for GTK 3.
Please see <https://wiki.gnome.org/Projects/gtkmm/PortingToGtkmm3> for
information about porting from gtkmm2.4 to gtkmm3.0, and
<https://docs.gtk.org/gtk3/migrating-2to3.html> for general information
about porting from GTK 2 to GTK 3.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: eq10q
Source-Version: 2.2~repack0-5
Done: Bastian Germann <bage@debian.org>

We believe that the bug you reported is fixed in the latest version of
eq10q, 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 1041795@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 eq10q 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, 15 Oct 2023 00:15:15 +0200
Source: eq10q
Architecture: source
Version: 2.2~repack0-5
Distribution: unstable
Urgency: medium
Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org>
Changed-By: Bastian Germann <bage@debian.org>
Closes: 1041795 1044400
Changes:
 eq10q (2.2~repack0-5) unstable; urgency=medium
 .
   * Team upload.
   * Prevent gui build (Closes: #1041795)
   * Clean generated and built files (Closes: #1044400)
Checksums-Sha1:
 e39b6fa3ef58a8cba0e16251c8b8be982a956c42 1856 eq10q_2.2~repack0-5.dsc
 2fff152e479c125e859d6fb5099153e23763b728 6088 eq10q_2.2~repack0-5.debian.tar.xz
 a70cb33cac03c41f0cb048e8eea169e83da4a0e2 6468 eq10q_2.2~repack0-5_source.buildinfo
Checksums-Sha256:
 87fb6800cd676877d2e854dee997decc5900e2abeab661149cba05bc590d205e 1856 eq10q_2.2~repack0-5.dsc
 9c8b5fb0ec4ea341abff058100b71a3d7ba5adcbbe2bd6197b377220dca0bf8b 6088 eq10q_2.2~repack0-5.debian.tar.xz
 198d7062d6ace3b08886783ee4020dea9322250bb18b101041815ccde40d1520 6468 eq10q_2.2~repack0-5_source.buildinfo
Files:
 f206829a4d8ce336901974366d15e0ce 1856 sound optional eq10q_2.2~repack0-5.dsc
 f4b6727ebaea41e9df0fcca4e9fed9f6 6088 sound optional eq10q_2.2~repack0-5.debian.tar.xz
 4efb017739b318c66eebd56d1d10aa77 6468 sound optional eq10q_2.2~repack0-5_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmUrFBUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFPJGDADIZhPSib5du+pu27jnXWVXtPl2TkT1d9IP
Ru8jAP0rfrX7kakz7se/aLRnc4z/x9aLLSkZVe7C8AbujEXTBOkPAI2NQK8kIYH1
xpoYwPPXX7G9kzeI10+r8FuVmUYFWr/nwVSOFvHNBysmGTE6Ai63Ze04rxJ7HaoD
KoWo3jumUvWO7Bg4etbEexeoFjUknoSNpLVz14rVIUuVZS6j5EF27Sf5dgakIBS2
wLLhwPOr65Ioa0Cqr8XDHVxKa3HEMb36Idg6964TdmXsHjifKLERKOi15tP/FtGz
kHhDavlHkMEOF+DXuxm6T+O1eYagWjEOva+A0Nih1CEq7O0B6V/tqqL5CuGop1Jb
PiNrsB9hSyQNfg6S+0zH50td44DiBULsstkkx9656OtX50wsEWd1urV3Wkfx91CY
qBzSTfkZukmFvZLcn0/j/he6HsgEb5p+O5v/6utetHn6kayanKQ0YhL8/xIUiv10
FsOsaSBBgcKs4f7QRU2/n5jzG5LYJM0=
=oQJF
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: