FYI: the config option is named FreshIndexMaxAge.
FreshIndexMaxAge: 300 would therefore consider the information to be
fresh for 5 minutes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/872365
The changelog does not refer to this bug report, but the previous
version does:
apt-cacher-ng (0.6.8-1) unstable; urgency=low
* New upstream version
+ supports optional IP filters via libwrap (closes: #635454)
+ adds more helpers for detection/removal of corrupted cache
This bug was fixed in the package apt-cacher-ng - 0.6.8-2
---
apt-cacher-ng (0.6.8-2) unstable; urgency=medium
* Added libwrap0-dev to Build-Depends (closes: #646300)
* Added newer dpkg to Pre-Depends (for xz compression support)
-- Eduard Bloch bl...@debian.org Sun, 23 Oct
This feature does already exist, the current consider rotten after X
seconds value is hardcoded to 27 seconds.
I just need to assign an option name to the config parser. Any
suggestions?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does the setting refer to the lists used by apt-get update only, or is
it more generic? (i.e. does it affect all proxied content/files?)
The source refers to rotten only in one location:
./source/expiration.cc: snprintf(buf, _countof(buf),
Previously detected: %lu rotten package
Yes, it was about MAXTEMPDELAY (it's already converted to
acfg::maxtempdelay in my local branch).
Selecting an option name is always complicated, it should not contain
expir or rott to avoid further confusion.
But max-age sounds familiar, let's call it FreshIndexMaxAge: ...
--
You received
