> Tue Mar 3 07:53:49 2009|debug [17547]: Add curl handle #108: for > http://security.debian.org/dists/stable/updates/contrib/binary-i386/Packages.bz2 > > Tue Mar 3 07:53:49 2009|debug [17547]: libcurl: setting up for HEAD request > > > Tue Mar 3 07:53:49 2009|debug CURLINFO_TEXT [17547]: Re-using existing > connection! (#1) with host security.debian.org > > Tue Mar 3 07:53:49 2009|debug CURLINFO_TEXT [17547]: Connected to > security.debian.org (212.211.132.250) port 80 (#1) > > Tue Mar 3 07:53:49 2009|debug CURLINFO_TEXT [17547]: Expire cleared > > > Tue Mar 3 07:53:49 2009|debug CURLINFO_TEXT [17547]: Connection #1 to host > security.debian.org left intact > > Tue Mar 3 07:53:49 2009|debug [17547]: curl handle #108 completed, status: 0 > > > Tue Mar 3 07:53:49 2009|debug [17669]: libcurl reading of headers complete > > > Tue Mar 3 07:53:49 2009|debug [17669]: Found EOF marker and status > FrT;@2|$1|0$0| > > Tue Mar 3 07:53:49 2009|debug [17669]: cached file is up to date or more > recent, Tue, 29 Jan 2008 16:55:18 GMT <-> Sun, 08 Apr 2007 07:20:40 GMT
This is the problem. Somehow you have got a recent modification date in the cached header file. Could you cat /var/cache/apt-cacher/headers/security.debian.org_dists_stable_updates_contrib_binary-i386_Packages.bz2 and post the contents I think it will say Tue, 29 Jan 2008 16:55:18 GMT whereas it should be Sun, 08 Apr 2007 07:20:40 GMT. Having said that, I am not sure how it has happened. It could be that a cache/server has lied at some point and you end up with bad data. If that is the case, it is difficult to see how to work round it. Mark -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
