Package: apt-cacher Version: 1.5.3 This bug seems to be quite similar to #354548. This patch fixed it for me. I don't have the error messages at the moment because I deleted all those cron mails and don't know how to reproduce the original state. Additionally I'd write '-z' instead of '! -s' to check for an empty file.
--- apt-cacher-cleanup.pl | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/apt-cacher-cleanup.pl b/apt-cacher-cleanup.pl index f5f8461..07b0c81 100755 --- a/apt-cacher-cleanup.pl +++ b/apt-cacher-cleanup.pl @@ -165,7 +165,7 @@ for my $file (@ifiles) { flock($glck, LOCK_UN); close($glck); - if(-e $tmpfile && ! -s $tmpfile && $tmpfile=~/bz2$/) { + if(-e $tmpfile && ! -s $tmpfile && $tmpfile=~/(gz|bz2)$/) { # moo, junk, empty file, most likely leftovers from previous versions # of apt-cacher-cleanup where the junk was "protected" from beeing # deleted. Purge later by not having in %valid. -- 1.4.4.1 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]