Your message dated Mon, 8 Oct 2007 20:42:38 +0600 with message-id <[EMAIL PROTECTED]> and subject line Close bug that fixed in the 0.9.9-1 version has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: polipo Version: 0.9.5-1 Severity: normal My system used to have polipo installed, but it has since been removed (but not purged). /etc/logrotate.d/polipo contains this postrotate script: PIDFILE=/var/run/polipo/polipo.pid [ -f "$PIDFILE" ] && kill -USR1 $(cat "$PIDFILE") The problem seems to be that when $PIDFILE does not exist, the exit code of the second line is 1, so logrotate thinks the postrotate script has failed. Changing to if [ -f "$PIDFILE" ] ; then kill -USR1 $(cat "$PIDFILE") ; fi would work around this problem by returning a 0 exit code if the pidfile does not exist, or the exit code of kill if it does. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.8-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages polipo depends on: ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an
--- End Message ---
--- Begin Message ---Package: polipo Version: 0.9.9-1 polipo (0.9.9-1) unstable; urgency=low * New upstream release (closes: #315655, #332411 CAN-2005-3163) * Fixed bug in logrotate script which causes an error when the pidfile does not exist (closes: #294442, thanks to Vineet Kumar) -- Tom Huckstep <[EMAIL PROTECTED]> Tue, 4 Oct 2005 14:35:02 +0100
--- End Message ---
