Further details on this bug:
Looking at /usr/sbin/apt-cacher from apt-cacher 1.5.3, I see this code
snippet on line 707 (function handle_connection()):
my $response = &ua_act(1, $host, $uri);
#my $response = $ua->head("http://$host$uri";);
#include
* Richard Burton [Sat, Mar 11 2006, 11:00:07AM]:
>
> >From: Eduard Bloch <[EMAIL PROTECTED]>
> >> Package: apt-cacher
> >Which version?
>
> Sorry, filed the report on another machine so it didn't pick it up.
> Version is 1.5.3 (latest unstable).
>
> >Bad. There are checks to prevent ex
From: Eduard Bloch <[EMAIL PROTECTED]>
> Package: apt-cacher
Which version?
Sorry, filed the report on another machine so it didn't pick it up.
Version is 1.5.3 (latest unstable).
Bad. There are checks to prevent exactly this. The only scenario where I
can imagine this happening:
- the ser
#include
* Richard Antony Burton [Fri, Mar 10 2006, 10:35:44PM]:
> Package: apt-cacher
> Severity: important
Which version?
> Noticed a lack of cached packages, checked cache directory and found no debs
> older than 7th March. Checked log and found this from the cleanup script:
> Tue Mar 7 06:2
Package: apt-cacher
Severity: important
Noticed a lack of cached packages, checked cache directory and found no debs
older than 7th March. Checked log and found this from the cleanup script:
Tue Mar 7 06:25:45
2006|CLEANUPREFRESH|EXPIRED|0|ftp.debian.org_debian_dists_unstable_contrib_binary-i386
5 matches
Mail list logo