From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot 2023.08.3 released
Date: Tue, 14 Nov 2023 18:48:50 +0100 [thread overview]
Message-ID: <87h6locjjx.fsf@48ers.dk> (raw)
Hi,
Buildroot is a simple tool for creating complete embedded Linux systems
(http://buildroot.org).
Buildroot 2023.08.3 is released - Go download it at:
http://buildroot.org/downloads/buildroot-2023.08.3.tar.gz
or
http://buildroot.org/downloads/buildroot-2023.08.3.tar.xz
Or get it from Git:
git://git.buildroot.org/buildroot
Buildroot 2023.08.3 is a bugfix release, fixing a number of important /
security related issues discovered since the 2023.08.2 release.
- Per-package builds: Unbreak SDK relocation logic. Only drop the hard
links for the final host / target directory, fixing a build time /
size regression in 2023.08.2.
- Packages where a free-form version/site can be specified (E.G. Linux,
U-Boot, ..) can now have the corresponding tarballs of these custom
downloads checked by the download infrastructure based on .hash files
in the global patch directory. These hashes are optional unless
BR2_DOWNLOAD_FORCE_CHECK_HASHES is enabled.
A utils/add-custom-hashes helper script has been added to
assist in managing such hash files.
- Defconfigs: Avenger96: Downgrade to TF-A v2.5 to fix boot issue since
2023.08, stm32mp157a-dk1, stm32mp157c-dk2: Unbreak TF-A build,
stm32mp157c-odessey: Use a fixed TF-A version for reproducibility
- Security fixes for apache, clamav, cups-filters, go, ksmbd-tools,
libopenssl, minizip-zlib, nghttp2, opencv4, openvpn, python-django,
python-urllib3, python-web2py, rabbitmq-c, redis, suricata, tiff, tor,
vim, wireshark, wolfssl, xlib_libX11, xlib_libXpm, xen, zchunk
- Fixes for download/compilation/runtime/license issues in
arm-trusted-firmware, aufs, aufs-util, azure-iot-sdk, casync, cjson,
conmon, dhcpcd, docker-cli, docker-engine, freeradius-server, inadyn,
kvmtool, libgeos, libmdbx, libmemcached, libosmium, libtommath,
libupnp, libzlib, lightning, linux-pam, lxc, mender, mpd, mxsldr,
nano, nettle, network-manager, nodejs, opencv4-contrib, openjdk-bin,
opusfile, paho-mqtt-c, pango, perl-lwp-protocol-https, petitboot, php,
pistache, python-pycryptodomex, reproc, riscv64-elf-toolchain,
sedutil, snort3, tar, traceroute, websocketpp, xdg-dbus-proxy, zabbix
For more details, see the CHANGES file:
https://git.buildroot.net/buildroot/plain/CHANGES?id=2023.08.3
Users of the affected packages are strongly encouraged to upgrade.
Many thanks to all the people contributing to this release:
git shortlog -sn 2023.08.2..
49 Fabrice Fontaine
22 Peter Korsgaard
10 Bernd Kuhls
10 Yann E. MORIN
6 Adam Duskett
3 Reza Arbab
2 Adrian Perez de Castro
2 Oleg Lyovin
2 Stefan Agner
2 Woodrow Douglass
1 Alexey Romanov
1 Andreas Ziegler
1 Andrew Donnellan
1 Angelo Compagnucci
1 Brandon Maier
1 Christian Hitz
1 Daniel Lang
1 Fabien Thomas
1 Giulio Benetti
1 Joachim Wiberg
1 Kalpesh Panchal
1 Maxim Kochetkov
1 Michael Nosthoff
1 Paul Cercueil
1 Thomas Petazzoni
1 Titouan Christophe
1 Леонид Юрьев (Leonid Yuriev)
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
reply other threads:[~2023-11-14 17:49 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=87h6locjjx.fsf@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