Your message dated Mon, 12 Aug 2013 14:19:38 +0100 with message-id <[email protected]> and subject line Re: Bug#611867: Logrotate bug in cups when deleted but not purged has caused the Debian Bug report #611867, regarding Logrotate bug in cups when deleted but not purged 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.) -- 611867: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611867 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: cups Version: 1.4.4-7 When cups is deleted via aptitude, but not purged, the following email if generated every day: /etc/cron.daily/logrotate: error: error accessing /var/log/cups: No such file or directory error: cups:1 glob failed for /var/log/cups/*log error: found error in /var/log/cups/*log , skipping The fault spears to be in: ~$ cat /etc/logrotate.d/cups which has a wild card which can never expand under these circumstances: /var/log/cups/*log { daily missingok The "missingok" is also useless, since the error will occur before the contents of the braces are parsed. Reported from my android phone, sorry that I could not use "reportbug"
--- End Message ---
--- Begin Message ---fixed 611867 cups/1.4.4-7+squeeze3 thanks On Thu 03 Feb 2011 at 15:20:15 +1100, John N wrote: > When cups is deleted via aptitude, but not purged, the following email if > generated every day: > > /etc/cron.daily/logrotate: > error: error accessing /var/log/cups: No such file or directory > error: cups:1 glob failed for /var/log/cups/*log > error: found error in /var/log/cups/*log , skipping Tried this with cups 1.4.4-7+squeeze3 and 1.5.3-5. /var/log/cups and its usual complement of files remains on the system and running logrotate does not generate any mail, I can only suppose any problem has been fixed. Regards, Brian.
--- End Message ---
