meta-openembedded/meta-oe
Wang Mingyu 31b3c8bec5
valkey: upgrade 9.0.0 -> 9.0.1
0001-src-config.h-Enable-HAVE_ARM_NEON-on-AArch64.patch
removed since it's included in 9.0.1

Changelog:
===========
- Authenticate slot migration client on source node to internal user
- Bug fix: reset io_last_written on c->buf resize to prevent stale pointers
- Sentinel: fix regression requiring "+failover" ACL in failover path
- Cluster: Avoid usage of light weight messages to nodes with not ready bidirectional links
- Send duplicate multi meet packet only for node which supports it in mixed clusters
- Fix: LTRIM should not call signalModifiedKey when no elements are removed
- Fix build on some 32-bit ARM by only using NEON on AArch64
- Fix deadlock in IO-thread shutdown during panic
- Fix COMMANDLOG large-reply when using reply copy avoidance
- Fix CLUSTER SLOTS crash when called from module timer callback

Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
2025-12-21 08:54:04 -08:00
..
classes meta-oe: image: optionally remove RAW image after sparse image creation 2025-09-15 09:55:16 -07:00
conf botan: add ptest support 2025-12-16 19:57:33 -08:00
dynamic-layers thingsboard-gateway: upgrade 3.7.4 -> 3.8.0 2025-12-21 08:54:01 -08:00
files static-passwd-meta-oe: add flatpak user 2025-04-19 14:36:07 -07:00
lib/oeqa/selftest/cases
licenses licenses: add licenses for ktx-software 2025-07-22 20:02:18 -07:00
recipes-benchmark fio: ignore CVE-2025-10824 2025-12-16 19:57:32 -08:00
recipes-bsp pointercal: Add HOMEPAGE variable 2025-12-10 08:58:48 -08:00
recipes-connectivity libwebsockets: upgrade 4.3.5 -> 4.5.2 2025-12-16 19:57:32 -08:00
recipes-core libconfig: drop recipe 2025-12-14 11:52:30 -08:00
recipes-crypto botan: add ptest support 2025-12-16 19:57:33 -08:00
recipes-dbs postgresql: upgrade 17.6 -> 17.7 2025-12-16 19:57:32 -08:00
recipes-devtools microsoft-gsl: upgrade 4.2.0 -> 4.2.1 2025-12-21 08:54:02 -08:00
recipes-extended valkey: upgrade 9.0.0 -> 9.0.1 2025-12-21 08:54:04 -08:00
recipes-gnome gtkmm4: update 2025-12-03 17:39:27 -08:00
recipes-graphics vk-gl-cts: Delete unused patch 2025-12-14 02:45:02 -08:00
recipes-kernel trace-cmd: Add HOMEPAGE variable 2025-12-10 08:58:47 -08:00
recipes-multimedia libopusenc: upgrade 0.2.1 -> 0.3 2025-12-20 11:41:03 -08:00
recipes-navigation Revert "proj: Fix do_package QA issue for unshipped bash-completion files" 2025-12-11 09:32:46 -08:00
recipes-networking/cyrus-sasl meta-openembedded/all: adapt to UNPACKDIR changes 2025-06-25 06:44:52 -07:00
recipes-printing cups-filters: patch CVE-2025-64524 2025-12-10 08:56:12 -08:00
recipes-security kernel-hardening-checker: upgrade 0.6.10.2 -> 0.6.17.1 2025-11-11 10:19:41 -08:00
recipes-shells dash: upgrade 0.5.13 -> 0.5.13.1 2025-10-21 20:02:39 -07:00
recipes-support switchtec-user: upgrade 4.2 -> 4.3 2025-12-21 08:54:04 -08:00
recipes-test cunit: inherit sourceforge-releases class 2025-11-12 09:38:58 -08:00
COPYING.MIT
README.md README.md: Change maintainer from Andreas to Khem for gnome, multimedia, xfce 2025-09-19 12:21:59 -07:00
SECURITY.md

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