On Tue, Feb 28, 2006 at 09:22:44PM +0100, Eduard Bloch wrote:
#include hallo.h
* Andrew Schulman [Mon, Feb 27 2006, 05:19:13AM]:
Package: apt-cacher
Version: 1.5.1
Severity: normal
/etc/cron.daily/apt-cacher fails with:
bzcat: Compressed file ends unexpectedly;
perhaps it is corrupted? *Possible* reason follows.
bzcat: Success
Input file =
http.us.debian.org_debian_dists_.._project_experimental_contrib_binary-i386_Packages.bz2,
output file = (stdout)
Hi people,
you all reported problems with apt-cacher with symptoms like those
described above. Please test the new package available in
http://rootfs.net/debs/apt-cacher_1.5.3_all.deb and report whether the
problem is solved for you.
The update enjoyed my usual inspections and test parcour, however better
make a backup copy of your cache before installing it:
cp -la /var/cacher/apt-cacher /var/cacher/apt-cacher-backup
(or similar command)
You can run the cleanup script manually as root or the correct user,
/usr/share/apt-cacher/apt-cacher-cleanup.pl .
Eduard.
Sorry for the slow response, but the nuisance messages have
disappeared. I believe that in my case the relevant files were
completely absent.
While looking at the apt-cacher-cleanup.pl code I noticed a few small
items in the comments:
1)
# add one argument like 1 to make it verbose
I tried this, but it didn't work. I think the comment is obsolete,
and the way to get verbose is with -v (which did work for me).
2)
# do locking, not loosing files because someone redownloaded the index
files
That's losing I think.
3)
# file state decissions, lock that area
decisions
4)
# headers for previosly expired files
previously
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
