Re: [pacman-dev] [PATCH 1/1] support http header to indicate an expected failure

28 May 2021

      -----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On Fri, 28 May 2021, Christian Hesse wrote:
...
Well, out-of-date is a term that does barely match here... pacman does known
about the date of its current database files only. So yes, more recent
database files are used as long as they are newer than the local ones - even
if out-of-date compared with a mirror.
That's why the pacredir documentation tells you to run `pacman -Sy` twice to
be sure: First run fetches the newest database from local network, second run
(where pacredir returns 404) fetches from mirror if a newer version is
available.
Just some side-idea: why not consider all databases which are older than x 
minutes (where x is configurable) "out of date"? This would rely on having 
systemtimes in sync, but otherwise would get rid of the cumbersome 
double-`pacman -Syu`.

regards,
Erich

P.S.: I'm running something similar as you - but by far not as elaborate: 
two (for redundancy) nginx servers which cache packages and download 
databases directly.

Re: [pacman-dev] [PATCH 1/1] support http header to indicate an expected failure

Erich Eckner