All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot 2023.02.7 released
Date: Tue, 14 Nov 2023 21:30:13 +0100	[thread overview]
Message-ID: <87cywccc2y.fsf@48ers.dk> (raw)

Hi,

Buildroot is a simple tool for creating complete embedded Linux systems
(http://buildroot.org).

Buildroot 2023.02.7 is released - Go download it at:

http://buildroot.org/downloads/buildroot-2023.02.7.tar.gz

or

http://buildroot.org/downloads/buildroot-2023.02.7.tar.xz

Or get it from Git:

git://git.buildroot.org/buildroot

Buildroot 2023.02.7 is a bugfix release on the current long term
release, fixing a number of important / security related issues
discovered since the 2023.02.6 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.02.6.

- 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: stm32mp157a-dk1, stm32mp157c-dk2: Unbreak TF-A build,
  stm32mp157c-odessey: Use a fixed TF-A version for reproducibility

- Security fixes for apache, arm-trusted-firmware, clamav, cups-filters,
  go, ksmbd-tools, minizip-zlib, nghttp2, opencv4, python-django,
  python-urllib3, python-web2py, rabbitmq-c, redis, suricata, tiff, tor,
  traceroute, vim, wireshark, wolfssl, xen, xlib_libX11, xlib_libXpm,
  zchunk

- Fixes for download/compilation/runtime/license issues in aufs,
  aufs-util, azure-iot-sdk, cjson, dhcpcd, freeradius-server, htop,
  kvmtool, libgdiplus, libopenssl, libosmium, libtommath, libupnp,
  libzlib, lxc, mender, mpd, mxsldr, nano, nettle, network-manager,
  nodejs, opencv4-contrib, openjdk-bin, openvpn, opusfile, paho-mqtt-c,
  perl-lwp-protocol-https, php, riscv64-elf-toolchain, tar, websocketpp,
  xdg-dbus-proxy, zabbix

For more details, see the CHANGES file:

https://git.buildroot.net/buildroot/plain/CHANGES?id=2023.02.7

Users of the affected packages are strongly encouraged to upgrade.

Many thanks to all the people contributing to this release:

git shortlog -sn 2023.02.6..

    35  Fabrice Fontaine
    22  Peter Korsgaard
    10  Yann E. MORIN
     8  Bernd Kuhls
     6  Adam Duskett
     2  Adrian Perez de Castro
     2  Angelo Compagnucci
     2  Scott Fan
     2  Woodrow Douglass
     1  Andreas Ziegler
     1  Andrew Donnellan
     1  Brandon Maier
     1  Christian Hitz
     1  Fabien Thomas
     1  Francois Perrad
     1  Giulio Benetti
     1  Kalpesh Panchal
     1  Maxim Kochetkov
     1  Michael Nosthoff
     1  Oleg Lyovin
     1  Thomas Petazzoni
     1  Titouan Christophe

-- 
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

                 reply	other threads:[~2023-11-14 20:30 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=87cywccc2y.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 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.