meta-openembedded/meta-oe
Leon Anavi de34d6fefa
valkey: Upgrade 8.0.0 -> 8.0.1
Upgrade valkey to version 8.0.1:

- Fix a build issue with RDMA when using additional make parameters
- Fix an issue where CLUSTER SLOTS might return the wrong tcp or
  tls port when called from inside a script or from a module
- Fix a crash when CLUSTER SLOTS or CLUSTER SHARDS is called from
  inside a script or from a module
- Fix a build issue on systems where <threads.h> is unavailable
- Fix an issue with the default sentinel.conf being invalid
- Build binary releases with systemd support
- Avoid .c, .d and .o files from being copied to the binary tar.gz
  releases
- (CVE-2024-31449) Lua library commands may lead to stack overflow
  and potential RCE
- (CVE-2024-31227) Potential Denial-of-service due to malformed ACL
  selectors
- (CVE-2024-31228) Potential Denial-of-service due to unbounded
  pattern matching

Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2024-10-11 07:52:22 -07:00
..
classes fitimage: add support to build arbitrary FIT images 2024-10-09 15:47:23 -07:00
conf ptest-packagelists-meta-oe.inc: Add asio 2024-10-10 12:53:49 -07:00
dynamic-layers nanopb: upgrade 0.4.8 -> 0.4.9 2024-09-30 07:34:23 -07:00
files influxdb: Add missing group to static id 2024-02-17 17:35:24 -08:00
lib/oeqa/selftest/cases
licenses
recipes-benchmark fio: upgrade 3.37 -> 3.38 2024-10-10 12:53:49 -07:00
recipes-bsp fwupd: upgrade 1.9.24 -> 1.9.25 2024-09-30 07:34:22 -07:00
recipes-connectivity telepathy-idle: Remove obsolete recipe 2024-09-30 23:54:17 -07:00
recipes-core fluentbit: Upgrade recipe to 3.1.9 2024-10-10 12:53:50 -07:00
recipes-crypto cryptsetup: fix udev PACKAGECONFIG 2024-10-10 12:53:50 -07:00
recipes-dbs mysql-python: Remove obsolete recipe 2024-09-30 23:54:17 -07:00
recipes-devtools xmlrpc-c: 1.59.01 -> 1.60.03 2024-10-09 15:47:21 -07:00
recipes-extended valkey: Upgrade 8.0.0 -> 8.0.1 2024-10-11 07:52:22 -07:00
recipes-gnome adw-gtk3: upgrade 5.3 -> 5.4 2024-09-30 07:34:22 -07:00
recipes-graphics tigervnc: upgrade 1.11.0 -> 1.14.0 2024-10-10 19:46:19 -07:00
recipes-kernel externalsrc: fix support in various components 2024-10-09 15:47:23 -07:00
recipes-multimedia sound-theme-freedesktop: Update SRC_URI 2024-10-11 00:25:41 -07:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-09-27 06:18:13 -07:00
recipes-networking/cyrus-sasl recipes: Start WORKDIR -> UNPACKDIR transition 2024-05-23 08:44:44 -07:00
recipes-printing cups-filters: include UPSTREAM_CHECK_URI to fix UNKNOWN_BROKEN status 2024-07-24 08:56:30 -07:00
recipes-security softhsm: add destroyed global access prevention patch 2024-09-27 10:08:14 -07:00
recipes-shells zsh: update 5.8 -> 5.9 2024-08-23 22:35:10 -07:00
recipes-support hwdata: upgrade 0.387 -> 0.388 2024-10-10 19:46:18 -07:00
recipes-test catch2: upgrade 3.7.0 -> 3.7.1 2024-09-29 10:01:07 -07:00
COPYING.MIT
README.md README.md: Hint at "git request-pull" 2024-09-14 08:43:55 -07:00

meta-oe

This layer depends on:

URI: git://github.com/openembedded/openembedded-core.git branch: master

luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below

pacman -S lib32-gcc-libs lib32-glibc

Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'

When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'

You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.

Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.

Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

layer maintainer: Khem Raj raj.khem@gmail.com