Re: [Buildroot] [PATCH] utils/genrandconfig: always use BR2_BACKUP_SITE in the autobuilders

[Thomas Perale via buildroot <buildroot@buildroot.org>]

In reply of:
> > How and how often are the 'source.buildroot.net' backups generated right now ?
> 
> Pretty much constantly:
> 
> 3 */2 * * * flock -n /home/brmirror/br-mirror.lock /home/brmirror/bin/update-br-mirror.sh >/dev/null 2>&1 || true

Is the update-br-mirror.sh script available somewhere ?

> > By reading this paragraph I'm thinking the upstream location check could be
> > coupled to the generation of the backups instead.
> 
> I'm not sure to understand what you mean. The "upstream location
> check" is done by the build machines, which are completely distinct
> from the machine hosting sources.b.o and doing the mirroring.

Yes that's what I meant. Since doing this verification by the autobuilders is
an issue you could move the verification and publishing of the stale entries
from the machine hosting the sources. 

Since it already has the responsability to download all the entries, it seems
like a perfect candidate to detect stale locations.
Unless 'update-br-mirror' script only trigger a the download if a new location
is detected ?

What I'm afraid of with the HTTP header solution proposed is that it's gonna be
burried in logs that would be quickly forgotten about. The current solution
while generating a lot of false positive manage to catch some real stale
locations publicly.

PERALE Thomas
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot