meta-openembedded/meta-oe
Peter Marko fb3726d664 gattlib: mark CVE-2019-6498 as fixed
Our hash does not point to exact tag and CVE patch is already in.

We use: 33a8a275928b186381bb0aea0f9778e330e57ec3
Fix: 60b813a770

git describe --tags --match=v0.2 33a8a275928b186381bb0aea0f9778e330e57ec3 60b813a770e42fdb0e85c1d2da7a55327784b8d6
v0.2-262-g33a8a27
v0.2-85-g60b813a

Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit e5a12d5252)
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2025-01-16 09:17:32 -05:00
..
classes Add class for appending dm-verity hash data to block device images 2024-04-23 15:18:30 -07:00
conf pegtl: add ptest support 2024-08-29 09:37:50 -07:00
dynamic-layers netplan: upgrade 1.0.1 -> 1.1 2024-09-15 07:46:44 -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 libhugetlbfs: Fix contains reference to TMPDIR [buildpaths] error 2024-11-19 13:13:26 -08:00
recipes-bsp cleanup after polkit fix 2024-09-01 15:54:30 -07:00
recipes-connectivity gattlib: mark CVE-2019-6498 as fixed 2025-01-16 09:17:32 -05:00
recipes-core mm-common: upgrade 1.0.4 -> 1.0.6 2024-09-11 21:15:33 -07:00
recipes-crypto cryptsetup: fix udev PACKAGECONFIG 2024-11-19 13:13:28 -08:00
recipes-dbs mariadb: Ensure compatibility with ARMv9 by updating .arch directive 2025-01-16 09:17:32 -05:00
recipes-devtools abseil-cpp: Do not leak -Wnon-virtual-dtor into the .pc files 2025-01-16 09:17:32 -05:00
recipes-extended vlock: fix do_fetch error 2024-11-19 13:13:29 -08:00
recipes-gnome cleanup after polkit fix 2024-09-01 15:54:30 -07:00
recipes-graphics openjpeg: upgrade 2.5.0 -> 2.5.2 2024-09-15 07:46:44 -07:00
recipes-kernel kernel-selftest: Update to allow for turning on all tests 2024-11-19 13:13:28 -08:00
recipes-multimedia sound-theme-freedesktop: Update SRC_URI 2024-11-19 13:13:28 -08:00
recipes-navigation gpsd: condition the runtime dependence of pyserial on the pygps 2024-11-19 13:13:24 -08: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 nmap: Fix off-by-one overflow in the IP protocol table. 2024-11-19 13:13:29 -08:00
recipes-shells dash: set CVE_PRODUCT 2025-01-16 09:17:32 -05:00
recipes-support lvm2: Remove the lvm2-udevrules package 2024-11-25 13:29:59 -08:00
recipes-test catch2: upgrade 3.6.0 -> 3.7.0 2024-09-16 23:01:22 -07:00
COPYING.MIT
README.md meta-openemnedded: Add myself as styhead maintainer 2024-09-29 13:58:53 -07:00

meta-oe

This layer depends on:

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

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][styhead]' 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][styhead][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: Armin Kuster akuster808@gmail.com