On Sun, July 27, 2008 16:54, Eric Cooper wrote: >> We're using approx to download packages only once for our network of >> about 40 hosts. However it seems that approx doesn't check every time >> whether its cache is still fresh. > [...] > >> For clarity, what I expect approx to do: >> 1) On every request check Release / Packages do still be fresh wrt >> to the mirror. E.g. by using the timestamps of those files and comparing >> them locally, or other mechanisms. If not fresh download it. 2) Serve the >> requested packages files either from cache or downloaded first from >> mirror depending on availability. > > This was fixed in version 3.0.0. Prior to that, approx tried to avoid > contacting remote repositories if files were "recent" enough. But there > are lots of inter-file consistency requirements (Release must match > Release.gpg, etc.) that made this approach unworkable. > > > Please consider upgrading to the current version. There's a version of > 3.3.0 in backports (http://packages.debian.org/etch-backports/approx).
Ah, good to know, thanks. I did indeed check the changelog of newer versions but couldn't find an obvious reference. Good to know that upgrading will indeed solve that. Thijs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
