From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18
Date: Mon, 19 Aug 2019 14:55:14 +0200 [thread overview]
Message-ID: <20190819145514.19722372@windsurf.home> (raw)
In-Reply-To: <20190819124959.quvccga35p2ggkrf@sapphire.tkos.co.il>
Hello,
On Mon, 19 Aug 2019 15:49:59 +0300
Baruch Siach <baruch@tkos.co.il> wrote:
> The list of packages versions in Buildroot seems to be take from the master
> branch. All these packages were updated in the next branch. I think that when
> the next branch is active (i.e. has commits not in master), the script should
> look there instead of master.
Yes, this is a limitation of how we work right now. I'm not sure how to
handle this exactly at this point.
Should the results of http://autobuild.buildroot.net/stats/ and
http://autobuild.buildroot.net/stats/index.json use the next branch
when available ?
Having a look at the state of the master branch in terms of missing
version updates could also be helpful to detect packages for which
we're missing security updates.
So really, I'm not sure what is the best course of action here.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-08-19 12:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190819054333.566812D8079@tinkie.tkos.co.il>
2019-08-19 12:49 ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-08-18 Baruch Siach
2019-08-19 12:55 ` Thomas Petazzoni [this message]
2019-08-19 21:28 ` Arnout Vandecappelle
2019-08-19 21:32 ` Thomas Petazzoni
2019-08-19 22:00 ` Peter Korsgaard
2019-08-20 19:10 ` Arnout Vandecappelle
2019-08-20 19:18 ` Arnout Vandecappelle
2019-08-21 7:51 ` Yann E. MORIN
2019-08-21 8:01 ` Peter Korsgaard
2019-08-21 9:13 ` Yann E. MORIN
2019-08-21 10:03 ` Peter Korsgaard
2019-08-21 20:58 ` Arnout Vandecappelle
2019-08-26 7:38 ` Thomas Petazzoni
2019-08-27 20:17 ` Peter Korsgaard
2019-08-28 12:37 ` Thomas Petazzoni
[not found] <5d5a3ea8.1c69fb81.80346.bed9SMTPIN_ADDED_MISSING@mx.google.com>
[not found] ` <CAFtSRGAfbahUOhw2FEZ5mD1F0s3NpN1kmW5PxkHmPr83yhrxyg@mail.gmail.com>
2019-08-19 12:03 ` Thomas Petazzoni
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=20190819145514.19722372@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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