Your message dated Sun, 24 Mar 2024 16:49:59 +0000
with message-id <e1ror2l-00958l...@fasolo.debian.org>
and subject line Bug#1067175: fixed in exaile 4.1.3+dfsg-3
has caused the Debian Bug report #1067175,
regarding exaile: hard-coded dependency on libgtk-3-0 will become uninstallable 
on armel/armhf
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 ow...@bugs.debian.org
immediately.)


-- 
1067175: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067175
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: exaile
Version: 4.1.3+dfsg-2
Severity: serious
Justification: blocker for 64-bit time_t transition
User: debian-...@lists.debian.org
Usertags: time-t
Control: block 1036884 by -1

exaile is an Architecture: all package, but has a direct dependency on
libgtk-3-0, as well as an indirect dependency on libgtk-3-0t64 via
gir1.2-gtk-3.0.

On the architectures affected by the 64-bit time_t transition (notably
armel and armhf), this is an impossible dependency, because libgtk-3-0 and
libgtk-3-0t64 conflict.

Please remove the explicit dependency on libgtk-3-0. For Python code
that uses GTK via GObject-Introspection, it is sufficient to depend
on gir1.2-gtk-3.0.

More information about this transition is available on
<https://wiki.debian.org/ReleaseGoals/64bit-time>.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: exaile
Source-Version: 4.1.3+dfsg-3
Done: luzip665 <luzip...@posteo.de>

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

Debian distribution maintenance software
pp.
luzip665 <luzip...@posteo.de> (supplier of updated exaile 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 ftpmas...@ftp-master.debian.org)


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

Format: 1.8
Date: Sat, 23 MAR 2024 12:32:16 +0200
Source: exaile
Architecture: source
Version: 4.1.3+dfsg-3
Distribution: unstable
Urgency: low
Maintainer: luzip665 <luzip...@posteo.de>
Changed-By: luzip665 <luzip...@posteo.de>
Closes: 1067175
Changes:
 exaile (4.1.3+dfsg-3) unstable; urgency=low
 .
   * Removing direct dependency to libgtk-3-0 (Closes: #1067175)
Checksums-Sha1:
 811c6f6f80802fef389acaa43783c371f4f79b89 1648 exaile_4.1.3+dfsg-3.dsc
 153307431d7cb9ff136213055f34c14ccfdc98bc 71512 
exaile_4.1.3+dfsg-3.debian.tar.xz
 5ad55f2903e5319a11b5ef8d8d16392ddc9904a1 7683 
exaile_4.1.3+dfsg-3_source.buildinfo
Checksums-Sha256:
 3781db7404e307d9d3952c5d9f6082501cb835d22562270f1d81f8df12a653e4 1648 
exaile_4.1.3+dfsg-3.dsc
 082f0b3c1aba972e284a0792d9d0f6aa874cf12be84e07ae89ace7eb65049555 71512 
exaile_4.1.3+dfsg-3.debian.tar.xz
 2bbf66f243e34984cf74465167da461865553ca8f66c1050c6359d123eca555e 7683 
exaile_4.1.3+dfsg-3_source.buildinfo
Files:
 71a514e238ff2704b26e901e78a92c59 1648 sound optional exaile_4.1.3+dfsg-3.dsc
 9dd265e54ad6c1670e36c9129a24c0d4 71512 sound optional 
exaile_4.1.3+dfsg-3.debian.tar.xz
 5cb83f67c8b4b2820fcba151b5de8728 7683 sound optional 
exaile_4.1.3+dfsg-3_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmYAVaIQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFIBAC/9cYUq7Z9AWPX4yLp17SeOmt2aCwD/XwTVg
BXYH6TZst3tzh5ioRroRkVlBxUPyiuDBwHwThZr/ysrToG7ji9t2LMo9FcoAW2gD
sNc2FeO2Yf61yOR8JgKTSVi+4Qs2tG6dDikoMjPAjSWf/HVoG9hesYMOdT5E9+nh
R50pALAW75RXv2cad0XMHfupuCcNUsO2ilmVSk7/ndCGii6NXg0b2RGPJRj1m6Vo
xkhtZKboslB2u0VAsR6syr07dg9zMPV3RZxSBf0PvNgXJ1YT2QRIoxG12p+RoIRF
0saUKHLY8+e2lCHikHTiADJnq0BIz+inKXEhlwjRtnOu+jUPmCkzmCxDkwD8rsYg
JEyIL1VJabtAnhFkDRdRGNS9pV3pIF8OiWPXdK/WEWLwOPO2PRT2KnBtD+cAM/gk
xGwOP9uzqSQej8e4neqvDpyuBdRh2vz0wveSuaJ0BXV3TkoySb6yBVybQQNpDxOO
3fiZEHeXVMx7VeOdnlMDRnGGVIFtIcU=
=AY2f
-----END PGP SIGNATURE-----

Attachment: pgpj4JYs5h40g.pgp
Description: PGP signature


--- End Message ---

Reply via email to