On Sat, Oct 07, 2006 at 12:54:41AM +1000, Ted Percival wrote:
> Package: suphp-common
> Version: 0.6.1-1
> Severity: normal
> Tags: patch
> 
> When suphp-common is removed (not purged) and there are no logfiles in
> /var/log/suphp, that directory is removed. This causes the
> /etc/logrotate.d/suphp-common script to fail with the following output:
> 
> > /etc/cron.daily/logrotate:
> > error: error accessing /var/log/suphp: No such file or directory
> > error: suphp-common:1 glob failed for /var/log/suphp/*.log
> > run-parts: /etc/cron.daily/logrotate exited with return code 1
> 
> The simplest solution seems to me to be to put a placeholder file in
> /var/log/suphp so it is not removed on package removal. I will attach a
> patch that does so, but I am unable to get suphp to build at the moment
> and therefore haven't tested it.
> 


humm, lintian doesn't like this:

W: suphp-common: file-in-unusual-dir var/log/suphp/.placeholder
N:
N:   This file or symbolic link is in a directory where files are not
N:   normally installed by Debian packages.
N:


I will look on other packages using logrotate ;)


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to