From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Peter Korsgaard <peter@korsgaard.com>
Cc: Romain Naour <romain.naour@smile.fr>,
yann.morin@orange.com, buildroot <buildroot@buildroot.org>,
Julien Olivain <ju.o@free.fr>
Subject: Re: [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19
Date: Mon, 20 Apr 2026 13:48:11 +0200 [thread overview]
Message-ID: <aeYSHz0oMG2Lx3km@windsurf> (raw)
In-Reply-To: <87fr4qhreo.fsf@dell.be.48ers.dk>
On Mon, Apr 20, 2026 at 12:12:15PM +0200, Peter Korsgaard wrote:
> Yes, I noticed the same and mailed Thomas as I was away on holiday last
> week. I'm back now but with a big email backlog, and I will take a look
> once I get a bit of time unless someone else beats me to it.
We figured this out with Titouan earlier today. The "next" branch was
still referenced in the list of branches in
buildroot-test/web/branches, and the script takes the "next" branch as
the baseline when doing this "outdated packages" check. But since next
no longer exists on the main Buildroot Git repo, it was using whatever
old next branch was there.
Immediate fix: drop next from buildroot-test/web/branches (which is
the file telling the autobuilders which branches to test).
Long-term fix: somehow automate this.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-04-20 11:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <69e59cd7.050a0220.1ab584.974e@mx.google.com>
2026-04-20 9:32 ` [Buildroot] [autobuild.buildroot.org] Your daily results for 2026-04-19 yann.morin
2026-04-20 10:12 ` Peter Korsgaard
2026-04-20 11:48 ` Thomas Petazzoni via buildroot [this message]
2026-04-20 12:22 ` Peter Korsgaard
2026-04-20 12:30 ` yann.morin
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=aeYSHz0oMG2Lx3km@windsurf \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=peter@korsgaard.com \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.com \
--cc=yann.morin@orange.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox