On Tue, Mar 03, 2009 at 11:02:21PM -0500, Omari Norman wrote: > On Tue, Mar 03, 2009 at 01:45:36PM +0000, Mark Hindley wrote: > > On Tue, Mar 03, 2009 at 01:31:40PM +0000, Mark Hindley wrote: > > > > > 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. > > > > Actually, are you using the patch mode in apt-cacher-cleanup? That may > > have caused this. > > I have no idea what patch mode or apt-cacher-cleanup is, and I can't > find it in apt-cacher.conf, so unless it's the default or I enabled it > by mistake, I don't think I'm using it :)
It is experimental code in apt-cacher-cleanup to use pdiffs to update the cached files by patching, rather than redownload the whole file again. It is mentioned in apt-cacher.NEWS and /usr/share/apt-cacher/apt-cacher-cleanup.pl --help. You enable it in /etc/cron.daily/apt-cacher by adding the -p option. But it sounds like you haven't! Mark -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
