Your message dated Fri, 5 Apr 2024 18:38:44 +0200
with message-id
<trinity-0fc78728-0769-4bd3-9d94-2379d8cf8b48-1712335124515@3c-app-gmx-bap14>
and subject line stretch is long gone
has caused the Debian Bug report #852135,
regarding debdelta: installation leaves gpg-agent process running
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.)
--
852135: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852135
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debdelta
Version: 0.56
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Control: affects -1 + debdelta-doc
Hi,
during a test with piuparts I noticed your package left processes
running after the package has been removed and/or purged.
In https://lists.debian.org/debian-devel/2009/08/msg00182.html and
followups it has been agreed that these bugs are to be filed with
severity serious.
>From the attached log (scroll to the bottom...):
0m49.3s ERROR: FAIL: Processes are running inside chroot:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
gpg-agent 11803 root cwd DIR 0,21 440 3463512416
/tmp/piupartss/tmpGfwH0w
gpg-agent 11803 root rtd DIR 0,21 440 3463512416
/tmp/piupartss/tmpGfwH0w
gpg-agent 11803 root mem REG 0,21 1787812 3463515254
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libc-2.24.so
gpg-agent 11803 root mem REG 0,21 132408 3463515240
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libpthread-2.24.so
gpg-agent 11803 root mem REG 0,21 87432 3463515211
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libgpg-error.so.0.21.0
gpg-agent 11803 root mem REG 0,21 842884 3463515213
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/libgcrypt.so.20.1.5
gpg-agent 11803 root mem REG 0,21 146716 3463515258
/tmp/piupartss/tmpGfwH0w/lib/i386-linux-gnu/ld-2.24.so
gpg-agent 11803 root 0r CHR 1,3 0t0 3463498470
/tmp/piupartss/tmpGfwH0w/dev/null
gpg-agent 11803 root 1w CHR 1,3 0t0 3463498470
/tmp/piupartss/tmpGfwH0w/dev/null
gpg-agent 11803 root 2w CHR 1,3 0t0 3463498470
/tmp/piupartss/tmpGfwH0w/dev/null
This agent is automatically started by the gpg command in the postinst script
unfortunately there is no option to automatically terminate such a temporary
agent. But you could add the following command to your postinst,
directly after the gpg command, to terminate the agent:
gpgconf --homedir ${GPG_HOME} --kill gpg-agent || true
cheers,
Andreas
debdelta_0.56.log.gz
Description: application/gzip
--- End Message ---
--- Begin Message ---
Even if this was not fixed in stretch as well; as stretch is not maintained
anymore, let's close this.
--- End Message ---
