Your message dated Tue, 26 Mar 2013 11:32:31 +0000
with message-id <[email protected]>
and subject line Bug#679590: fixed in binkd 0.9.11-1.1
has caused the Debian Bug report #679590,
regarding binkd: fails to purge: rmdir: failed to remove `/var/log/binkd/': No
such file or directory
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.)
--
679590: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=679590
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: binkd
Version: 0.9.11-1
Severity: important
User: [email protected]
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to purge.
According to policy 7.2 you cannot rely on the depends being available
during purge, only the essential packages are available for sure.
Filing this as important because a.) it's a clear policy violation (to
not clean up at purge) b.) having a piuparts clean archive is a release
goal since lenny and c.) this package being piuparts buggy blocks
packages depending on it from being tested by piuparts (and thus
possibly the detection of more severe problems).
>From the attached log (scroll to the bottom...):
Removing binkd ...
Purging configuration files for binkd ...
rmdir: failed to remove `/var/log/binkd/': No such file or directory
dpkg: error processing binkd (--purge):
subprocess installed post-removal script returned error exit status 1
Errors were encountered while processing:
binkd
cheers,
Andreas
binkd_0.9.11-1.log.gz
Description: GNU Zip compressed data
--- End Message ---
--- Begin Message ---
Source: binkd
Source-Version: 0.9.11-1.1
We believe that the bug you reported is fixed in the latest version of
binkd, 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.
Andreas Beckmann <[email protected]> (supplier of updated binkd 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: SHA256
Format: 1.8
Date: Tue, 19 Mar 2013 11:50:04 +0100
Source: binkd
Binary: binkd
Architecture: source amd64
Version: 0.9.11-1.1
Distribution: unstable
Urgency: low
Maintainer: Marco d'Itri <[email protected]>
Changed-By: Andreas Beckmann <[email protected]>
Description:
binkd - FidoTech TCP/IP mailer
Closes: 679590
Changes:
binkd (0.9.11-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Do not fail to purge if /var/log/binkd does not exist. (Closes: #679590)
Checksums-Sha1:
d8fb8bf8bdcb265e0e7577ea64fded4fab06c9a4 1639 binkd_0.9.11-1.1.dsc
5c21d57e5134e9a9a92f874766f330840de98f8c 7552 binkd_0.9.11-1.1.debian.tar.xz
a643e63808d54d09af8aa331b52f40cecef3f9be 105628 binkd_0.9.11-1.1_amd64.deb
Checksums-Sha256:
471dfc20a45dcd374bd104ef905139be9c491900af291dc8ab3a83fcda2c7c66 1639
binkd_0.9.11-1.1.dsc
7c407e51d10c41b211b053b2f1233d8c4eb8a4997b4f6a389e6bf9bb3ebfd08f 7552
binkd_0.9.11-1.1.debian.tar.xz
1a7c83167d5c951ba6799f8ad5823f43f5cc5af89bf5a5720091c56788024129 105628
binkd_0.9.11-1.1_amd64.deb
Files:
e13cb4e0bd310ffe92316e8dab809b89 1639 comm extra binkd_0.9.11-1.1.dsc
245024b103c4cf109896a77e954660f6 7552 comm extra binkd_0.9.11-1.1.debian.tar.xz
220623f095e051d8c8a36083ec7bcebc 105628 comm extra binkd_0.9.11-1.1_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCAAGBQJRSEP5AAoJEF+zP5NZ6e0IdPQP/iAHwYurC+Z9RwqyiMNit93s
9RBJAv8F7jfObHz+uZP117LfteLEEZ862qm8ApqqKJnBx1UE+DiYnMRffKTfjFCp
Ym5S4BCl5lJ+WOZCjdp1VyDqU7nm6Dsp043Ig2lf9jrgxViHqVzGGSRiqOzL4wLH
RJIynG5OSRQ8QRPv4AlUQ4mDPTYKlbf6ivI/Fgv8yTwYh0mkaif14j96T3QpzhYc
FHIp0FoLmYvHTEvRyZ/Rm5/bn2BCUqQGupqBDpIgzIDgXy44Cr80j7UZuEwEkEOu
oCnpNPO9oh5905KhNb/z4ck9nzOrzsIeunL4vUSJyU4LkMKkkwEK5RONVJ52Bkk5
6ujuDFaXlaKjzJZ3ZmsjiEocS+w0Q5zSpJ5zacm6krBK7tCylILLwsKgl3NB3lef
MfkHkrHtDcv6JuyOIqSpgHZfDBIyL0qqLy304RwVm9zF4tt62KtE6VO6dwXlOxz3
Y3NEgnhxQtLFiUmokyTLG30bo/SaR59/udswm8vOXNH4c7z1dougTQJarjQCv42Z
VfVYNEbOJzTgkneDeQafIi9fCVd2n31VTd6MAVEtqiuEUMSu/ebFGgYzNskJqJdz
MJrFs2eNOoTUNLms46F8Q7NtW89+UtPAWOcLZYU9tdV2PERsYMjlCC408pserhjH
c3r0FASbR5ElcWUApe2+
=XO0Z
-----END PGP SIGNATURE-----
--- End Message ---
