linux/meta-openembedded.git/meta-filesystems, branch stable/kirkstone-nut

ntfs-3g-ntfsprogs: Upgrade 2022.5.17 to 2022.10.3

2023-11-03T14:48:35+00:00

Changes: Rejected zero-sized runs Avoided merging runlists with no runs Fix CVE-2022-40284 Dunfell and master both have latest version of ntfs-3g-ntfsprogs 2022.10.3. Therefore, upgrade the version on kirkstone too. Signed-off-by: Omkar Patil Signed-off-by: Khem Raj (cherry picked from commit 5d5e8854718dab02c2737e3faf288f830a514841) Signed-off-by: Sana Kazi Signed-off-by: Armin Kuster

fuse3: fix ptest test_passthrough_hp failure

2022-08-16T18:47:31+00:00

fix test_passthrough_hp failure with error: 21 unlinked testfile checks failed Signed-off-by: Changqing Li

fuse3: support ptest

2022-08-16T18:47:14+00:00

fuse3 test is designed to run under source dir, there are many places like "progname = pjoin(basename, 'example', 'ioctl')" in the testcases, which will try to find compiled program. As our S != B, and the don't run test under source dir. Test will fail with following errors: No such file or directory: '/usr/lib64/fuse3/ptest/test/../example/printcap' Fix by install needed programs for the test Signed-off-by: Changqing Li

ntfs-3g-ntfsprogs: upgrade to 2022.5.17

2022-07-09T19:10:44+00:00

Upgrade from 2021.8.22 to 2022.5.17. This upgrade mainly include CVE fixes. According to https://github.com/tuxera/ntfs-3g/releases: """ Changelog: * Improved defence against maliciously tampered NTFS partitions * Improved defence against improper use of options * Updated the documentation """ Signed-off-by: Chen Qi Signed-off-by: Armin Kuster

ntfs-3g-ntfsprogs: Set CVE_PRODUCT to "tuxera:ntfs-3g"

2022-06-15T13:57:55+00:00

Set CVE_PRODUCT to 'tuxera:ntfs-3g' for ntfs-3g-ntfsprogs recipe, cve-check class is setting default CVE_PRODUCT to 'ntfs-3g-ntfsprogs' which ignores the ntfs-3g-ntfsprogs CVEs from NVD Database. Reference: CVE-2019-9755 Link: https://nvd.nist.gov/vuln/detail/CVE-2019-9755 Signed-off-by: Akash Hadke Signed-off-by: Akash Hadke Signed-off-by: Armin Kuster

meta-openemnedded: Add myself as kirkstone maintainer

2022-04-24T00:14:31+00:00

Signed-off-by: Armin Kuster Signed-off-by: Khem Raj

smbnetfs: upgrade 0.6.1 -> 0.6.3

2022-03-16T15:32:19+00:00

configure.patch refreshed for new version. Changelog: ======== add files for debian packaging Signed-off-by: Wang Mingyu Signed-off-by: Khem Raj

recipes: Update LICENSE variable to use SPDX license identifiers

2022-03-05T01:41:45+00:00

Signed-off-by: Khem Raj

layer.conf: change layer priority to match oe-core

2022-02-28T16:39:26+00:00

Layer priority is the ultimate decider of what recipe is used: if layer A has recipe foo_1 and layer B has recipe foo_2, if layer A's priority is higher than B then foo_1 will be used, even though the version in B is higher, and even if PREFERRED_VERSION_foo is set to 2. This complicates recipes moving between layers, for example when a newer version of a recipe (say, python3-wheel) is taken from a layer with a higher priority (say, meta-python) and moved to a layer with a lower priority (say, oe-core) then it has to be removed before it is added: there is no way to have it in both layers and work correctly. Higher priorities are useful in distribution layers where you may want to override specific recipes without any other fuss. However as all of the layers in meta-oe simply add more recipes in defined areas, there's no need to have a higher layer priority. Signed-off-by: Ross Burton Signed-off-by: Khem Raj

layers: Bump to use kirkstone

2022-02-22T02:12:04+00:00

its not going to be backward ABI compatible with honister due to variable renaming. Signed-off-by: Khem Raj