Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-24
Date: Mon, 25 Nov 2019 11:56:30 +0100	[thread overview]
Message-ID: <20191125115630.66ffb5f0@windsurf> (raw)
In-Reply-To: <0d328fb7-d1a9-aef5-2846-82bd2d55bac9@railnova.eu>

Hello Titouan,

On Mon, 25 Nov 2019 10:13:05 +0100
Titouan Christophe <titouan.christophe@railnova.eu> wrote:

> >               name              | found by |        link to release-monitoring.org        |   version    |   upstream
> > -------------------------------+----------+----------------------------------------------+--------------+--------------
> >                           redis |  DISTRO  | https://release-monitoring.org/project/04181 | 5.0.5        | 5.0.7
> >   
> 
> This is lagging behind, Redis was already bumped to 5.0.6 one week ago, 
> and to 5.0.7 over the week-end :)

When a next branch exists, we use the next branch as the source of
information for what is the current version of each package in
Buildroot. We do this because typically, next is more "up to date" than
master.

However, in this specific case, redis was bumped to 5.0.7 in master,
but not in next, so until next gets merged back into master, our
tooling will think redis is at 5.0.5, because that's the version used
in next.

Perhaps this could be improved by grabbing both master and next, and
retaining the highest version between both, for each package. But oh
well, that's quite some additional complexity :/

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

       reply	other threads:[~2019-11-25 10:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5ddb8024.1c69fb81.357d6.9264SMTPIN_ADDED_MISSING@mx.google.com>
     [not found] ` <0d328fb7-d1a9-aef5-2846-82bd2d55bac9@railnova.eu>
2019-11-25 10:56   ` Thomas Petazzoni [this message]
2019-11-25 13:58     ` [Buildroot] [autobuild.buildroot.net] Your daily results for 2019-11-24 Titouan Christophe
2019-11-25 14:05       ` 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=20191125115630.66ffb5f0@windsurf \
    --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