Your message dated Wed, 05 Mar 2025 04:49:09 +0000
with message-id <e1tpggv-005hku...@fasolo.debian.org>
and subject line Bug#1098960: fixed in gtklock-playerctl-module 4.0.0-2
has caused the Debian Bug report #1098960,
regarding gtklock-playerctl-module: unsatisfiable dependency
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.)


-- 
1098960: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1098960
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: gtklock-playerctl-module
Version: 4.0.0-1
Severity: serious

https://tracker.debian.org/pkg/gtklock-playerctl-module says that the
package is unable to migrate because of an unsatisfiable dependency.

By clicking through the piuparts links, it reveals:

  The following packages have unmet dependencies:
   gtklock-playerctl-module : Depends: gtklock (< 4.0+) but 4.0.0-1 is
to be installed

Thank you,
Jeremy Bícha

--- End Message ---
--- Begin Message ---
Source: gtklock-playerctl-module
Source-Version: 4.0.0-2
Done: Maytham Alsudany <mayt...@debian.org>

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

Debian distribution maintenance software
pp.
Maytham Alsudany <mayt...@debian.org> (supplier of updated 
gtklock-playerctl-module 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: Wed, 05 Mar 2025 12:25:10 +0800
Source: gtklock-playerctl-module
Architecture: source
Version: 4.0.0-2
Distribution: unstable
Urgency: medium
Maintainer: Maytham Alsudany <mayt...@debian.org>
Changed-By: Maytham Alsudany <mayt...@debian.org>
Closes: 1098960
Changes:
 gtklock-playerctl-module (4.0.0-2) unstable; urgency=medium
 .
   * Fix dependency on gtklock (Closes: #1098960)
   * Update Vcs-* fields to reflect move to Debian namespace
   * Update my maintenance address
   * Bump Standards-Version to 4.7.2 (no changes)
Checksums-Sha1:
 0deff12730759bec982194aa7aa3e3a4bb8f96a8 2083 
gtklock-playerctl-module_4.0.0-2.dsc
 f64dc63eaf4185e845c51037ecb77add5a195c66 2668 
gtklock-playerctl-module_4.0.0-2.debian.tar.xz
 7950d732c417b696948165ba52ed12231c11a0e3 15816 
gtklock-playerctl-module_4.0.0-2_amd64.buildinfo
Checksums-Sha256:
 f394e826eeeea069d45f9940926cc22239ae8815c01a3a3cacdade1472717f97 2083 
gtklock-playerctl-module_4.0.0-2.dsc
 471d635de2dc9d1182a8280c03629e994faebddb1c4a418c9bee4a28b3cd7373 2668 
gtklock-playerctl-module_4.0.0-2.debian.tar.xz
 ec131de5e3e4369ba9c6358fea3051d62cc8307053991fb2d9cc303481400585 15816 
gtklock-playerctl-module_4.0.0-2_amd64.buildinfo
Files:
 dae67aa7bce18a21cdd4e382a193c3bd 2083 misc optional 
gtklock-playerctl-module_4.0.0-2.dsc
 7eae1bb82b48266bb0395cab368ca52b 2668 misc optional 
gtklock-playerctl-module_4.0.0-2.debian.tar.xz
 c0565535d52bd27bc25127b817f0465f 15816 misc optional 
gtklock-playerctl-module_4.0.0-2_amd64.buildinfo

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

iQIzBAEBCgAdFiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmfH0pUACgkQ1ZeJcgbF
8H+hTg//cHqBNRhY/PbZgITxKTaVyMHN7VZlfH28O3YnF4ezp67G9GMxYCYVFtst
30sGxwVpc1mtj8sqenAiGsyGMcK3v+ZDh39vHlD7JEOrRwYuAFal9/ul0RMQij+A
GqSCBc4hcJGjMzOp3eBfc9t9UINNJoUztkY1gqiLPF0wWeJNAbC/PxP/Hud0aTJg
flSYE2KIOnemEfzMWs28gfXFnLBqWiuJazMjMqvoNM+qTjbySAv2d/rMhINcaNyj
EO0eQ5aLb5BpKyT9B4vLpmSc0bmYf+AVop0vOX9PKUCxXYICgFFhJ+4rUHZ19/2L
MHKrDJn5KpEYbFIeVy8XG4l8J9D4LyqKDZhPa6VfkdyNmF5tt4SMJSUmJXwgYiUz
2DizxM/f0Q06LQTHLryH7Ntm8//IIesLQlN6RzSBzd5D57bHhTJeuVHpK2ggNnjJ
OoBogNj6l3CYoO452w5fmsL3wYeGa4TEDi9aCTCKzu1LrBTjOGRFIqAxX9lakHyN
0TjdygPPmiEg0NLNdAAaT12d33bRxxs1IuoQuX7BnV/aw/B+kjTmy9y2TwxOCXQZ
MlT/t1LqyC1qr3Hhmn44zRCadouPLHL/CqZBMUfPgLLamrnWuQvEQhpfbOWdLCYo
CHqiGRFQh8h4+y3EJxA3bARcQ6VjjFVkxd7FYHv6KlyzNAbryRg=
=Y8cz
-----END PGP SIGNATURE-----

Attachment: pgpRGwbtiQtpL.pgp
Description: PGP signature


--- End Message ---

Reply via email to