Bug#740551: documentation for APT::Periodic::MaxSize v.s. processing in apt.cron.daily
Package: apt
Severity: minor
Version: 0.9.15.5
Near the top of /etc/cron.daily/apt, the documentation for the MaxSize
variable says:
# APT::Periodic::MaxSize "0"; (new)
# - Set maximum size of the cache in MB (0=disable). If the cache
# is bigger, cached package files are deleted until the size
# requirement is met (the biggest packages will be deleted
# first).
(This same text is also found in
/usr/share/doc/apt/examples/configure-index.gz )
However, later on in the script, starting around line 170, the loop that
actually deletes files when MaxSize is non-zero includes the comments
"reverse-sort by mtime" and "delete oldest file", and in fact the loop
that processes the files goes through them in "ls -rt" order....
(This mismatch was true in various Debian versions going back for a
while, and still seems to be true in the latest Git:
http://anonscm.debian.org/gitweb/?p=apt/apt.git;a=blob;f=debian/apt.cron.daily;hb=HEAD
, i.e.
http://anonscm.debian.org/gitweb/?p=apt/apt.git;a=blob;f=debian/apt.cron.daily;h=71ac76555f00611973d6f2ffaa9c9277c490efd5;hb=a4a5901577a2b0d72f1c973f036a8198046d937a
as of today.)
Nathan
Reply to: