Wolfgang, On Tuesday, 2026-03-03 12:37:36 +0100, you wrote:
> ... > portage looks up the TTL in the package index file (Packages)¹ and > honors it unconditionally², so as a downstream user of a binhost, it's > not possible to override this setting. > > The default is 3600 seconds as defined by PORTAGE_BINHOST_TTL in > make.conf(5). Note that this setting defines which value is used when > creating the package index and not which value portage accepts when > updating. > > ¹ https://distfiles.gentoo.org/releases/amd64/binpackages/23.0/x86-64/Packages > ² > https://codeberg.org/gentoo/portage/src/commit/c492f93bccc3399c5fde86e969e168cff469a5ac/lib/portage/dbapi/bintree.py#L1561 Thank you for clarifying :-) But what are the consequences of an expired TTL? The Gentoo mirror I'm using is updated only every six hours. I just checked at about 11:00 and its "Packages" file contained TIMESTAMP: 1772598198 which corresponds to 2026-03-04 05:23:18 GMT+01. So how will Portage treat this over five hours old "Packages" file with a TTL of one hour? Sincerely, Rainer
