Bug#640122: apt-get ignores apt.conf option "Acquire::Max-ValidTime" on amd64
On Fri, Sep 2, 2011 at 17:51, Jens Arnold <jens.arnold@vamed.com> wrote:
> We're using an internal mirror which is updated at a defined interval for consistency.
> The 'Release' files from security.debian.org set a quite short timeout in their Vaild-Until:
> header (10 days). If we're trying to update an internal system from this mirror a few days
> later (apt-get update), it complains about the 'Release' file being expired and ignores it
> by default.
I haven't looked at the bug itself this behavior is a symptom of, but I
want to clarify that as it is documented in the manpage apt.conf this option
can't be used in the way you intend to. What you would like to have is a
(not implemented) Acquire::Min-ValidTime.
The specified behavior of Max-ValidTime is that either the ValidUntil is
used or the one calculated from Date+Max-ValidTime, whichever is first,
so you can't use it to increase the validate time - only to decrease it.
Best regards
David Kalnischkies
P.S.: I am not sure (and IANAL), but i think disclaimers like yours at
the end of
the mail aren't very effective from a legal standpoint - beside that
they are pretty
useless in a mail to a public world-readable bugtracker. :)
(but i guess they are automatically added by your company)
Reply to: