All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Perale via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: Thomas Perale <thomas.perale@mind.be>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] utils/genrandconfig: always use BR2_BACKUP_SITE in the autobuilders
Date: Thu, 27 Aug 2026 17:29:22 +0200	[thread overview]
Message-ID: <20260827152922.453102-1-thomas.perale@mind.be> (raw)
In-Reply-To: <20260826155155.4146765-1-thomas.petazzoni@bootlin.com>

Hello Thomas,

In reply of:
> So in the end let's revert back to using BR2_BACKUP_SITE in all
> configurations to avoid those build failures. If we want to detect
> really stale upstream locations, as suggested by Arnout, we can
> instrument the autobuilder runs to inject a special HTTP header and
> then look at the logs of sources.buildroot.net to see which files are
> grabbed by the autobuilders and determine if upstream locations are
> really dead and packages need to be fixed accordingly.

How and how often are the 'source.buildroot.net' backups generated right now ?
By reading this paragraph I'm thinking the upstream location check could be
coupled to the generation of the backups instead.

Otherwise I think this change make sense.

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

  reply	other threads:[~2026-08-27 15:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-26 15:51 [Buildroot] [PATCH] utils/genrandconfig: always use BR2_BACKUP_SITE in the autobuilders Thomas Petazzoni via buildroot
2026-08-27 15:29 ` Thomas Perale via buildroot [this message]
2026-08-27 15:42   ` Thomas Petazzoni via buildroot
2026-08-27 17:33     ` Thomas Perale via buildroot
2026-08-27 20:17       ` Thomas Petazzoni via buildroot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260827152922.453102-1-thomas.perale@mind.be \
    --to=buildroot@buildroot.org \
    --cc=thomas.perale@mind.be \
    --cc=thomas.petazzoni@bootlin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.