From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot 2022.08.1 released
Date: Mon, 03 Oct 2022 08:47:33 +0200 [thread overview]
Message-ID: <87o7uttncq.fsf@dell.be.48ers.dk> (raw)
Hi,
Buildroot is a simple tool for creating complete embedded Linux systems
(http://buildroot.org).
Buildroot 2022.08.1 is released - Go download it at:
http://buildroot.org/downloads/buildroot-2022.08.1.tar.gz
or
http://buildroot.org/downloads/buildroot-2022.08.1.tar.xz
Or get it from Git:
git://git.buildroot.org/buildroot
Buildroot 2022.08.1 is a bugfix release, fixing a number of important /
security related issues discovered since the 2022.08 release.
- Security fixes for busybox, docker-engine, expat, git, heirloom-mailx,
libconfuse, libxml2, mariadb, python3, tinyproxy, unbound, unzip, vim
- Fixes for download/compilation/runtime/license issues in botan,
docker-cli, haproxy, icu, imx-gpu-viv, libmdbx, libupnp,
ltp-testsuite, m4, makedevs, mesa3d, meson, mosquitto, ncurses,
openssh, pango, qlibc, qt5xmlpatterns, rtl8189es, rtl8723bu,
rtl8723ds, rtl8812au-aircrack-ng, runc, sox, uacme, xtables-addons
For more details, see the CHANGES file:
https://git.buildroot.net/buildroot/plain/CHANGES?id=2022.08.1
Users of the affected packages are strongly encouraged to upgrade.
Many thanks to all the people contributing to this release:
git shortlog -sn 2022.08..
11 Fabrice Fontaine
11 Giulio Benetti
5 Yann E. MORIN
4 James Hilliard
4 Lang Daniel
4 Luca Ceresoli
4 Peter Korsgaard
4 Thomas Petazzoni
3 Christian Stewart
3 Francois Perrad
2 Nicola Di Lieto
2 Quentin Schulz
1 Baruch Siach
1 Joachim Wiberg
1 Joel Stanley
1 Kyle Harding
1 Michael Klein
1 Peter Seiderer
1 Petr Vorel
1 Леонид Юрьев (Leonid Yuriev)
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2022-10-03 6:47 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:
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=87o7uttncq.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
/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