Your message dated Wed, 12 Dec 2018 11:05:50 +0100
with message-id <fd79bbfd133129cb3a13ae05d9bea709468af33e.ca...@debian.org>
and subject line Re: Bug#916197: libpaper1: postrm fails, uses ucf
unconditionally
has caused the Debian Bug report #916197,
regarding [piuparts] libpaper1 fails to purge: ucf not found
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.)
--
916197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916197
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libpaper1
Version: 1.1.25
Severity: serious
piuparts detected that libpaper1 fails to purge, because its postrm
doesn't check that ucf is available during purge.
https://piuparts.debian.org/sid/fail/libpaper1_1.1.25.log
Purging configuration files for libpaper1:amd64 (1.1.25) ...
/var/lib/dpkg/info/libpaper1:amd64.postrm: 16:
/var/lib/dpkg/info/libpaper1:amd64.postrm: ucf: not found
dpkg: error processing package libpaper1:amd64 (--purge):
installed libpaper1:amd64 package post-removal script subprocess returned
error exit status 127
Errors were encountered while processing:
libpaper1:amd64
It should test for ucf's presence, for example as openssh does:
if which ucf >/dev/null 2>&1; then
ucf --purge /etc/ssh/sshd_config
fi
(This is serious as it affects all reverse dependencies of libpaper1 in their
piuparts logs too)
Cheers,
OdyX
--- End Message ---
--- Begin Message ---
Hello,
the reported problem about ucf invocation in libpaper postrm script has
been fixed.
Thank you,
Giuseppe
--- End Message ---
