Upgrade to release 3.3.5:
- Control setting local nodes outside of the supposed local's
constructor
- Fix Python 3.13 compatibility re: collections.abc
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade to version 5.3.0:
- reno: Update master for unmaintained/zed
- Remove old excludes
- Update master for stable/2024.1
- reno: Update master for unmaintained/xena
- reno: Update master for unmaintained/wallaby
- reno: Update master for unmaintained/victoria
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
This commit modifies the PACKAGECONFIG entry for zlib to ensure that the
mod_deflate module is enabled with the appropriate zlib configuration.
By adding the --with-zlib=${STAGING_LIBDIR}/../ option, we direct the
configure script to use the zlib library from the staging directory
instead of relying on the host system's zlib installation.
Without that configure will search the host for zlib headers and lib.
This change resolves build failures related to zlib dependency when
mod_deflate is enabled and ensures a consistent build environment across
different host configurations.
Signed-off-by: Valeria Petrov <valeria.petrov@spinetix.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Affected components:
- cpupower
- intel-speed-select
- spidev-test
When the externalsrc class is used the tasks listed in SRCTREECOVEREDTASKS
are deleted to prevent them being executed. If externalsrc is used for
the kernel then this will include virtual/kernel:do_patch.
Signed-off-by: Andrej Valek <andrej.v@skyrain.eu>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
The FIT image support in OE is quite limited:
1) No support to build an arbitrary number of FIT images since the FIT
image generation is tightly coupled to the kernel image.
2) A lot of U_BOOT-specific variables which may not be necessary for
other bootloaders.
3) No usage of the meta-oe signing.bbclass for signed FIT images.
This alternative class is added to solve the above-mentioned problems:
1) The class can be inherited by an arbitrary number of
<fit-image-name>.bb recipes to generate FIT images
2) No U_BOOT-specific variables are used
3) <fit-image-name>.bb recipes can prepend the do_fitimage() to
provide the key using the signing.bbclass e.g.:
do_fitimage:prepend() {
signing_prepare
signing_use_role "${FITIMAGE_SIGNING_KEY_ROLE}"
}
Then enable and configure signing as follows:
FITIMAGE_SIGN = "1"
FITIMAGE_MKIMAGE_EXTRA_ARGS = "--engine pkcs11"
FITIMAGE_SIGN_KEYDIR = "${PKCS11_URI}
This class is inspired by the meta-phytec fitimage.bbclass [1].
[1] https://git.phytec.de/meta-phytec/tree/classes/fitimage.bbclass
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
Signed-off-by: Enrico Jörns <ejo@pengutronix.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
wtmpdb installs a PAM plugin in "${base_libdir}/security/pam_wtmpdb.so".
This path is not in default FILES.
Add this path to FILES:${PN} to fix this error:
ERROR: wtmpdb-0.11.0-r0 do_package: QA Issue: wtmpdb: Files/directories were installed but not shipped in any package:
/lib/security/pam_wtmpdb.so
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
wtmpdb: 1 installed and not shipped files. [installed-vs-shipped]
ERROR: wtmpdb-0.11.0-r0 do_package: Fatal QA errors were found, failing task.
ERROR: Logfile of failure stored in: .../poky/build-master/tmp/work/core2-64-poky-linux/wtmpdb/0.11.0/temp/log.do_package.939726
ERROR: Task (.../poky/meta-openembedded/meta-oe/recipes-extended/wtmpdb/wtmpdb_0.11.0.bb:do_package) failed with exit code '1'
Signed-off-by: Yoann Congal <yoann.congal@smile.fr>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
python3-pyyaml-include already supports native and nativesdk builds.
Starting from version 2.0, fsspec was introduced as a dependency for
pyyaml-include.
This commit adds support for native and nativesdk builds in the fsspec recipe.
Signed-off-by: Peng Zhang <peng.zhang1.cn@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Starting from version 2.0, fsspec was introduced in pyyaml-include,
allowing the inclusion of files from various sources such as HTTP,
SFTP, and S3. As a result, pyyaml-include now depends on fsspec for
both local and remote file inclusion, making it a required runtime
dependency.
Signed-off-by: Peng Zhang <peng.zhang1.cn@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade to version 4.11.0:
- Add natural_list
- filesize: support the ronna and quetta prefixes
- Update French translations for numbers
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade to version 8.0:
- Changes related to added support of gcov JSON intermediate format
- Detect suspicious counter values in gcov output
- Add --html-single-page to create a single page report (static or
with Javascript)
- Upload standalone applications as release artifacts
- Add support for gcov JSON intermediate format
- Add Exclusion markers to exclude a while function
- Change sort order in JSON output files
- Add source exclusion markers to exclude source branch from target
line
- Implement consistent sorting of files with no lines, or one line
with zero coverage
- Use replacement value of 0 for function call count NAN %
- Fix erroneous deprecation warning
- Fix display filename in HTML report
- Fix bundle of standalone executable with Python 3.12
- Fix merging of function coverage data
- Fix inefficient regular expression
- Fix missing output of gcov if execution fails
- Move tests to directory in the root
- Add MacOs to the GitHub test workflow
- Remove test exclusions for MacOs and adapt tests and reference
data
- Link correct documentation version in copyright header
- Move tag creation before publish the distribution because tag
from pipeline doesn't trigger additional runs
- Fix scrubber for date in HTML test data
- Add test with Python 3.12
- Add gcc-14 to the test suite
- Skip coverage upload if executed in a fork
- Only execute pipeline if pushed on main and add button to execute
workflow manual
- Check spelling in test pipeline
- Merge the test and deploy workflow to a single CI workflow
- Add Codacy to CI workflow for tracking coverage and code quality
- Add bandit to the linters
- Remove Codecov upload from pipeline
- Add test with bazel tests
License-Update: Adapt to new format, remains BSD 3-Clause License
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Upgrade to version 6.1.0:
- Covered the unreachable code path in
multidict._multidict_base._abc_itemsview_register() with typing
- Added support for Python 3.13
- Removed Python 3.7 support
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Add the specific udev rules needed for device mapper notifications to
the libdevmapper package. This is needed to get notifications for
device mapping to work with systemd.
Move the remaining udev rules files to the lvm2 package as there is no
real reason to have them packaged separately.
List all udev files explicitly in the FILES variables so that someone
will have to make an active decision where to package any new udev files
added in the future.
Co-authored-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Fredrik Hugosson <fredrik.hugosson@axis.com>
Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
rocksdb is not compatible with libc-musl:powerpc and armv5, so remove 'rocksdb'
from PACKAGECONFIG. Otherwise it complains error:
| ERROR: Nothing PROVIDES 'rocksdb' (but /path_to/meta-oe/recipes-extended/minifi-cpp/minifi-cpp_0.15.0.bb
DEPENDS on or otherwise requires it)
| rocksdb was skipped: incompatible with host arm-poky-linux-gnueabi (not in COMPATIBLE_HOST)
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Update xmlrpc-c from 1.59.01 to latest stable version 1.60.03. The
SRCREV is one more fix commit after release 1.60.03 in the stable
series. And remove 0002-fix-formatting-issues.patch which has been fixed
in upstream.
Signed-off-by: Kai Kang <kai.kang@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
ld.hugetlbfs is munging certain linker commandline options
and presenting a differently named options to its users, in
summary its expecting linker process to call ld.hugetlbfs
which calls the final linker with additional decorations.
This patch makes space for that by adding -B option to compiler
so it finds this the linker in S and then we creates symlinks
for linker name that clang/gcc are expecting.
Fixes
libhugetlbfs/2.24/recipe-sysroot-native/usr/bin/x86_64-yoe-linux/x86_64-yoe-linux-ld.bfd: unrecognized option '--hugetlbfs-link=B'
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Changes in 47.1
=================
- Fix the capabilities for the print dialog
Changes in 47.0
=================
- Translation updates
Changes in 47.rc
=================
- Fix restoring last used folder in the File Chooser portal
- Fix selecting multiple window on single selection
- Do not block xdg-desktop-portal-gnome when connecting to Nautilus
- Fix incorrectly set mimetype in the File Chooser portal
- Translation updates
Changes in 47.beta
=================
- Use GNOME Shell's private API for the Notification portal
- Use Nautilus for the File Chooser portal
- Translation updates
Changes in 47.alpha
=================
- Expose the new accent colors setting
- Various cleanups to the screencast widget
- Add support for the "supported_output_file_formats" option in the Print
portal
- Fix default layout mode of the ScreenCast/Remote Desktop portal
- Translation updates
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Change log found at https://gitlab.xfce.org/xfce/xfce4-panel/-/tags/xfce4-panel-4.18.5
- pager: Do not adapt upper value of spin button in viewport mode
- pager: Update workspace layout also on window manager change
- pager: Fix aspect ratio for viewport (V2)
- actions: Fix memory leak
- pager: Delay GdkScreen signal handlers
- panel: Do not scale background image when UI scale > 1
- popup-command: Do not block autohide when popped up at pointer
- Fix memory leaks when using gtk_css_provider_new()
- panel: Clear item list before repopulating item dialog
- panel: Remove autosave timer for plugins
- wrapper: Really ensure we don't call gtk_main_quit() twice
- panel: Block autohide when the panel has input focus
- clock: Fix sync timeout for seconds display
- clock: Implement ConsoleKit sleep monitor
- Add/Sharpen icons at 48-128px
- Adjust 32px icon margins, new separator icon
- Sharpen icons at 16px and 32px
- Increase margins for 24px icons
- Make 24px icons sharper
- icons: Fix wrong exported sizes
- Translation Updates:
Basque, Catalan, Danish, Estonian, French, Italian, Kazakh, Polish,
Russian, Slovenian, Spanish
Signed-off-by: Jason Schonberg <schonm@gmail.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
In order to improve the readability of the file, arrange value lines
of variables with multiple values in alphabetic order.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Remove the duplicate 'yajl' entry from value of
RDEPENDS:packagegroup-meta-oe-devtools variable.
Signed-off-by: Niko Mauno <niko.mauno@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
cve-check.bbclass reported unpatched vulnerabilities in libtar
[1,2,3,4,5]. The NIST assigned base score for the worst vulnerability
is 9.1 / critical.
The patches were taken from the libtar [6] master branch after the
latest tag v1.2.20 (the changes in libtar master mostly originate from
Fedora and their patches), and from the Fedora 41 libtar source package
[7] and the Debian libtar package 1.2.20-8 [8] where the patches were
not available in the libtar repository itself.
The Fedora patch series was taken in its entirety in order to minimize
differences to Fedora's source tree instead of cherry-picking only CVE
fixes. Minimizing the differences should avoid issues with potential
inter-dependencies between the patches, and hopefully provide better
confidence as even the newest patches have been in use in Fedora for
nearly 2 years (since December 2022; Fedora rpms/libtar.git commit
e25b692fc7ceaa387dafb865b472510754f51bd2). The series includes even the
Fedora patch libtar-1.2.20-no-static-buffer.patch, which contains
changes *) that match the libtar commit
ec613af2e9371d7a3e1f7c7a6822164a4255b4d1 ("decode: avoid using a static
buffer in th_get_pathname()") whose commit message says
Note this can break programs that expect sizeof(TAR) to be fixed.
The patches applied cleanly except for the Fedora srpm patch
libtar-1.2.11-bz729009.patch, which is identical with the pre-existing
meta-oe patch 0002-Do-not-strip-libtar.patch and is thus omitted.
The meta-openembedded recipe does not include any of the patches in
Kirkstone [9] nor the current master [10].
libtar does not have newer releases, and the libtar master doesn't
contain all of the changes included in the patches. Fedora's
libtar.1.2.11-*.patch are not included in the libtar v1.2.20 release
either but only in the master branch after the tag v1.2.20. The version
number in the filename is supposedly due to the patches being created
originally against v1.2.11 but have been upstreamed or at least
committed to the master only after v1.2.20.
The commit metadata could not be practically completed in most of the
cases due to missing commit messages in the original commits and
patches. The informal note about the author ("Authored by") was added to
the patch commit messages where the commit message was missing the
original author(s)' Signed-off-by.
*) The patch also contains the changes split to the libtar commits
495d0c0eabc5648186e7d58ad54b508d14af38f4 ("Check for NULL before
freeing th_pathname") and 20aa09bd7775094a2beb0f136c2c7d9e9fd6c7e6
("Added stdlib.h for malloc() in lib/decode.c"))
[1] https://nvd.nist.gov/vuln/detail/CVE-2021-33643
[2] https://nvd.nist.gov/vuln/detail/CVE-2021-33644
[3] https://nvd.nist.gov/vuln/detail/CVE-2021-33645
[4] https://nvd.nist.gov/vuln/detail/CVE-2021-33646
[5] https://nvd.nist.gov/vuln/detail/CVE-2013-4420
[6] https://repo.or.cz/libtar.git
[7] https://src.fedoraproject.org/rpms/libtar/tree/f41
[8] https://sources.debian.org/patches/libtar/1.2.20-8/CVE-2013-4420.patch/
[9] https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/libtar/libtar_1.2.20.bb?h=kirkstone&id=9a24b7679810628b594cc5a9b52f77f53d37004f
[10] https://git.openembedded.org/meta-openembedded/tree/meta-oe/recipes-support/libtar/libtar_1.2.20.bb?h=master&id=9356340655b3a4f87f98be88f2d167bb2514a54c
Signed-off-by: Katariina Lounento <katariina.lounento@vaisala.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Our provided netdata.conf contained a lot of keys which are no longer
supported by netdata. Netdata allows to regenerate the configuration
file and present all possible keys with their default values. This
refreshed file will be more easy to configure by our users.
To generate this file, I basically ran the documented command and
replaced the file paths with our variables when applicable.
Signed-off-by: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Netdata now provides its own systemd service files. They provide better
hardening than the one we were defining in the recipe.
Unfortunately, the CMakeLists.txt file wants to install them into /lib
rather than /usr/lib. I added mv commands to put them in the expected
location depending on usrmerge.
Signed-off-by: Enguerrand de Ribaucourt <enguerrand.de-ribaucourt@savoirfairelinux.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
