On Tue, Mar 03, 2009 at 10:58:37PM -0500, Omari Norman wrote: > On Tue, Mar 03, 2009 at 01:31:40PM +0000, Mark Hindley wrote: > > 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. > > That yields > > HTTP/1.1 200 OK > Connection: Keep-Alive > Date: Tue, 27 Jan 2009 15:27:02 GMT > Accept-Ranges: bytes > ETag: "1e7d-444df4a130980" > Server: Apache/2.2.3 (Debian) > Content-Length: 7805 > Content-Type: text/plain > Last-Modified: Tue, 29 Jan 2008 16:55:18 GMT > Client-Peer: 130.89.149.225:80 > Client-Response-Num: 1 > Keep-Alive: timeout=15, max=100 > > > 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. > > Any way to work around this--maybe just delete certain files then start > again? As long as I don't lose the few gigs of files in the cache, > that's okay.
Yes, if you delete the faulty header, next time the file is requested a new version should be fetched. The other files in your cache should be fine. Before you do that could you run bzcat /var/cache/apt-cacher/packages/security.debian.org_dists_stable_updates_contrib_binary-i386_Packages.bz2 I would live to know where this file has come from and make sure there isn't a bug hiding here somewhere. Thanks Mark -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
