Your message dated Fri, 08 Sep 2023 10:19:23 +0000
with message-id <e1qeyab-00bucl...@fasolo.debian.org>
and subject line Bug#1025576: fixed in libgsecuredelete 0.3-3.1
has caused the Debian Bug report #1025576,
regarding libgsecuredelete: recommends transitional policykit-1 package
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.)


-- 
1025576: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025576
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libgsecuredelete
Version: 0.3-3
Severity: normal
User: pkg-utopia-maintain...@lists.alioth.debian.org
Usertags: policykit-1

This package has a Recommends on the transitional package policykit-1,
which has been separated into polkitd, pkexec and (deprecated)
polkitd-pkla packages.

If this package communicates with polkitd via D-Bus, please represent that
as a Depends, Recommends or Suggests on polkitd, whichever is appropriate
for the strength of the requirement.

If this package runs /usr/bin/pkexec, please represent that as a Depends,
Recommends or Suggests on pkexec, whichever is appropriate for the strength
of the requirement.

For packages that are expected to be backported to bullseye, it's OK to
use an alternative dependency: polkitd | policykit-1 and/or
pkexec | policykit-1.

This is part of a mass bug filing, see
<https://lists.debian.org/debian-devel/2022/10/msg00211.html>.

Thanks,
    smcv

--- End Message ---
--- Begin Message ---
Source: libgsecuredelete
Source-Version: 0.3-3.1
Done: Bastian Germann <b...@debian.org>

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

Debian distribution maintenance software
pp.
Bastian Germann <b...@debian.org> (supplier of updated libgsecuredelete 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: Thu, 07 Sep 2023 23:37:52 +0000
Source: libgsecuredelete
Architecture: source
Version: 0.3-3.1
Distribution: unstable
Urgency: medium
Maintainer: Debian Privacy Tools Maintainers 
<pkg-privacy-maintain...@lists.alioth.debian.org>
Changed-By: Bastian Germann <b...@debian.org>
Closes: 1025576
Changes:
 libgsecuredelete (0.3-3.1) unstable; urgency=medium
 .
   * Non-maintainer upload
   * Recommend pkexec instead of policykit-1 (Closes: #1025576)
Checksums-Sha1:
 4aa242be3673024ddc0272eccb8352b3eafe345d 2279 libgsecuredelete_0.3-3.1.dsc
 c7ccfd35a521f45b7b4d9c1d5e245afcf621814f 8592 
libgsecuredelete_0.3-3.1.debian.tar.xz
 103f8579283ed4c9d15e6766cdd55bc7c475f1ec 6478 
libgsecuredelete_0.3-3.1_source.buildinfo
Checksums-Sha256:
 5d92a028ffe5da5ea9cb38223887ab407efafc891ac91e7cc1ab069d88a2c7d4 2279 
libgsecuredelete_0.3-3.1.dsc
 a9ece9146bf010c0e0b29094a37ddd229dea9770dc9800f6a7a8adb5ab0e3e64 8592 
libgsecuredelete_0.3-3.1.debian.tar.xz
 e9ab8e2b813b3ffd807c5dbf6f4df3462be1f789a7ccea13de593a0e5bed1606 6478 
libgsecuredelete_0.3-3.1_source.buildinfo
Files:
 d2a586adc589620031b9438f0e915a8e 2279 gnome optional 
libgsecuredelete_0.3-3.1.dsc
 20006e8c29a7a16861beee085a0cd8ac 8592 gnome optional 
libgsecuredelete_0.3-3.1.debian.tar.xz
 5339dfe701f83dc4a48d119930d39721 6478 gnome optional 
libgsecuredelete_0.3-3.1_source.buildinfo

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

iQHEBAEBCgAuFiEEQGIgyLhVKAI3jM5BH1x6i0VWQxQFAmT68OUQHGJhZ2VAZGVi
aWFuLm9yZwAKCRAfXHqLRVZDFDDPDACVfHm19RbkNyw2Y0qV5z1DQh5G4NnJ/C5r
safnEHcd5NkTksHfbT2crcm1wlrsXyhNT8hkFB+eIGICV/eX9VNnTslx2yZfSaQm
FmSIf7qTb99BB2GA8/skGG3DKFAltq4U/aoLhcZWtrin5llLiHkthHBylnmYb4vo
K+0p2iqB5aeH9dT8wIChcVwdM07ICl/2Ky4SVbx+T9wWjPULhHrz+HIQZHFxFtwi
5DPKdTV6aOM7c9FW9akzdQA45qbFreXx0edV/DH+Kangj3Bt46oj3X0F9/vjnjuq
KtjAI6edZuAVqln1OkAOYKyuoRSYnz/5YX+0h8KhBc/L69KXtUVahvqsTfhSz4+Z
o+ook1qGMknbzXe6Sqz5VjhoxB00KzWVSTDOMwZ6bp+GeppFnUjy1289QR0f3IOZ
l0ygGRxvBOdekjdRoqW04iboYB6e/FLbce5h/ANeyNMovMnXN1Jx0A1jrZldF10d
KncRqB2c8lYwTdJYQKTgI7Wjjv8v09A=
=sobH
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to