From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH=2020.02.x] package/redis: bump version to 5.0.9
Date: Mon, 29 Jun 2020 14:07:38 +0200 [thread overview]
Message-ID: <20200629140738.7dd4749d@windsurf> (raw)
In-Reply-To: <CAAXf6LWhoLwig3i8FNjC3OQ65h27y50cbu5ROZkBHKnnXsjSUw@mail.gmail.com>
Hello,
On Mon, 29 Jun 2020 12:51:02 +0200
Thomas De Schampheleire <patrickdepinguin@gmail.com> wrote:
> Which reminds me of the fact that the package stats and associated CVE
> detection is currently only running on the master branch (that I know of).
> Which means that we are missing the CVE detection on the LTS branch.
> Does it take a lot of resources / Is it hard to do, enabling this on the
> LTS branch too (mostly the CVE part) ?
Running pkg-stats on other branches is really easy, I can make it
generate autobuild.buildroot/stats/2020.02.x.{html,json} for example.
However, what needs a bit more effort is to modify the e-mail
notification script to make use of that.
Note that my colleague Gr?gory is working on improving the CVE
infrastructure so that you can run a script on your specific Buildroot
version and configuration, and get the list of CVEs you are affected
by. I.e the same results as pkg-stats, but really tailored to your
Buildroot version/configuration. Hopefully Gr?gory will send the
patches soon.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-06-29 12:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-21 21:39 [Buildroot] [PATCH=2020.02.x] package/redis: bump version to 5.0.9 Peter Korsgaard
2020-06-22 7:49 ` Titouan Christophe
2020-06-29 10:51 ` Thomas De Schampheleire
2020-06-29 12:07 ` Thomas Petazzoni [this message]
2020-06-29 12:16 ` Thomas De Schampheleire
2020-06-29 15:30 ` Titouan Christophe
2020-06-29 18:47 ` Thomas Petazzoni
2020-07-05 20:46 ` Peter Korsgaard
2020-07-05 20:48 ` Peter Korsgaard
2020-07-06 11:20 ` Thomas De Schampheleire
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=20200629140738.7dd4749d@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 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.