archive mirror
 help / color / mirror / Atom feed
From: Peter Korsgaard <>
Subject: [Buildroot] Buildroot 2022.02.12 released, 2022.02.x EOL
Date: Thu, 04 May 2023 22:48:21 +0200	[thread overview]
Message-ID: <> (raw)


Buildroot is a simple tool for creating complete embedded Linux systems

Buildroot 2022.02.12 is released - Go download it at:


Or get it from Git:


Buildroot 2022.02.12 is a bugfix release on the previous long term
release, fixing a number of important / security related issues
discovered since the 2022.02.11 release.

- Security fixes for agentpp, apache, containerd, git, intel-microcode,
  libmicrohttpd, libxml2, postgresql, python-web2py, runc, samba4, sudo,
  tcpdump, uclibc, vim, webkitgtk, wpewebkit, xserver_xorg-server

- Fixes for download/compilation/runtime/license issues in
  ca-certificates, coremark, dcron, eudev, ffmpeg, matio, poppler,
  s390-tools, snmppp

For more details, see the CHANGES file:

Users of the affected packages are strongly encouraged to upgrade.

Many thanks to all the people contributing to this release:

git shortlog -sn 2022.02.11..

    11  Fabrice Fontaine
     7  Bernd Kuhls
     4  Peter Seiderer
     3  Peter Korsgaard
     2  Adrian Perez de Castro
     2  Angelo Compagnucci
     2  Christian Stewart
     2  Francois Perrad
     2  Julien Olivain
     2  Luca Ceresoli
     2  Maxim Kochetkov
     2  Waldemar Brodkorb
     1  Bagas Sanjaya
     1  Daniel Lang
     1  Dario Binacchi
     1  Giulio Benetti
     1  James Hilliard
     1  James Knight
     1  Joel Stanley
     1  Lang Daniel
     1  Mario Haustein
     1  Stefan Ott
     1  ʎɐH ǝʌǝʇS

Notice: This will be the last update for 2022.02.x. Please migrate to
the 2023.02.x series instead.

Bye, Peter Korsgaard
buildroot mailing list

                 reply	other threads:[~2023-05-04 20:48 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

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

  git send-email \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).