On Thu, Mar 23, 2006 at 02:54:48AM +0100, Miernik wrote: > Package: approx > Version: 2.03 > Severity: normal > > > I have set > > interval 525600 > > yet approx nevertheless checked the upstream for newer Release and > Packages files, while there where perfect ones fetched yesterday. > And of course some Packages.gz where updated, so it happily ditched my > old one, and used over 3 megs of my GPRS connection to download a new > one, only because there where a few packages updated, which I don't care > about - I was perfeclty happy with my yesterdays Packages.gz > > For .deb files it obey's the setting OK.
In order to support "secure apt" (apt >= 0.6), approx always checks upstream for Release and Release.gpg files. Otherwise, you might end up with an inconsistent pair of these (one from your cache, one from upstream), causing apt's signature verification to fail. (This is especially likely if you have mixed sarge and etch clients: the sarge ones only reference the Release files, while the etch ones reference both Release and Release.gpg, making it much more probable that the cache would get inconsistent.) Furthermore, apt does some "cache invalidation" when it downloads a new Release file -- any Packages files whose checksums no longer match what's in the new Release file are deleted from the cache, so fresh ones will be fetched on reference. So the behavior you observe is intended, but perhaps not ideal over a slow link. I'm open to suggestions for a better solution! -- Eric Cooper e c c @ c m u . e d u -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
