Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Subject: [Buildroot] Buildroot 2023.02.9 released
Date: Mon, 15 Jan 2024 20:58:44 +0100	[thread overview]
Message-ID: <878r4qjrm3.fsf@48ers.dk> (raw)

Hi,

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

Buildroot 2023.02.9 is released - Go download it at:

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

or

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

Or get it from Git:

git://git.buildroot.org/buildroot

Buildroot 2023.02.9 is a bugfix release on the current long term
release, fixing a number of important / security related issues
discovered since the 2023.02.8 release.

- Infrastructure:

  - Download: Revert a permission fixup step in the tarball creation
    logic, which lead to a hash mismatch issue in two cargo-vendored
    packages, ripgrep and sentry-cli.

  - Build: Pass GIT_DIR=. in the environment (through
    HOST_MAKE_ENV/TARGET_MAKE_ENV) to the build steps to workaround
    packages trying to detect if they are building in a git checkout and
    getting confused when building in a sub directory of a Buildroot git
    checkout.

- Security fixes for cjson, dropbear, exim, faad2, freeswitch, giflib,
  go, gst1-plugins-bad, jq, ksmbd-tools, libcurl, libebml, libssh,
  libssh2, libuev, micropython, mp4v2, opensc, openssh, php, proftpd,
  putty, python-werkzeug, shim, squid, strongswan, tinyssh, tor, uftp,
  wireshark, wolfssl, xserver_xorg-server, xwayland

- Fixes for download/compilation/runtime/license issues in apcupsd,
  arm-trusted-firmware, botan, cups, duktape, edk2, gcc, gdal, gdb,
  glibc, go, google-breakpad, gst-omx, gstd, gst1-devtools, gst1-libav,
  gst1-plugins-bad, gst1-plugins-base, gst1-plugins-good,
  gst1-plugins-ugly, gst1-python, gst1-rtsp-server, gst1-vaapi,
  gstreamer1, gstreamer1-editing-services, ipcalc, json-for-modern-cpp,
  libaio, libcamera, libcap-ng, libgtk3, libiec61850, libraw,
  libsigsegv, libwebsockets, liquid-dsp, lvm2, madplay, mesa3d,
  micropython, orc, pipewire, postgis, postgresql, python-sip,
  rng-tools, sway, tree, valijson, xwayland

For more details, see the CHANGES file:

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

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.8..

    49  Fabrice Fontaine
    39  Peter Korsgaard
    25  Bernd Kuhls
     9  Adam Duskett
     7  Thomas Petazzoni
     3  Baruch Siach
     3  Peter Seiderer
     2  Alexey Brodkin
     2  Christian Hitz
     2  Michael Nosthoff
     2  Yann E. MORIN
     1  Alexander Dahl
     1  Christian Stewart
     1  Francois Perrad
     1  Julien Olivain
     1  Louis Chauvet
     1  Maxim Kochetkov
     1  Ralf Dragon
     1  Raphael Pavlidis
     1  Sébastien Szymanski
     1  Thomas Devoogdt

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

                 reply	other threads:[~2024-01-15 19:58 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=878r4qjrm3.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