Advance the pinned SRCREV to the current tip of jchampio's master. The
latest tagged release is still 0.1.2 (already reflected in PV), and the
23 new commits are entirely test-infrastructure work: porting the test
suite from Python 2 to Python 3/asyncio/websockets and adding coverage
for the module APIs. None of them touch the module sources that get
built and installed, so the shipped mod_websocket.so is functionally
unchanged; this simply keeps the git-tracking recipe on the current tip.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upstream changes:
* 2.650: new Systemd Services, GRUB 2, and Kea DHCP modules; WebSocket
proxy support in Servers Index; Alpine Linux support; Let's Encrypt
IP-based certificate support; editable SSH public keys in Users and
Groups.
* 2.651: Certbot certificate request/renewal fixes; fix live activation
of Linux bond interfaces.
* 2.652: global per-user ACL to block URL downloads from non-public IPs;
fix hex HTML entity recognition; fix session checks with HMAC session
keys; fix Usermin switching to use one-time login URLs.
* 2.653: fix missing xmlrpc-lib.pl; fix partially installed Debian
package listing; Authentic theme improvements.
Recipe changes:
* Drop init-exclude.patch: both hunks (init/index.cgi commented-out
runlevel loop and init/init-lib.pl exclude= support) are now
incorporated in upstream webmin 2.653.
* Refresh net-generic.patch: upstream added alpine-linux to the
os_support line in net/module.info; refresh the patch context.
* Refresh net-lib.pl.patch: context shifted by 4 lines with fuzz 1;
refreshed against 2.653 (same fallback to debian-linux-lib.pl).
* Remove webmin-openrc-init from do_install: webmin 2.653 ships a new
webmin-openrc-init script that references /sbin/openrc-run, which is
not available on systemd-based distros; remove the file to avoid an
unresolvable RDEPENDS QA failure.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Major version jump (1.x → 2.x series). Key upstream changes:
* 2.x dropped the legacy Netdata Cloud Agent-Cloud-Link (ACLK) and
merged cloud-connectivity into the main binary; ENABLE_ACLK and
ENABLE_CLOUD cmake options removed. OpenSSL and libcurl are now
mandatory build dependencies (no longer optional via PACKAGECONFIG).
* Improved database engine, new collectors (systemd-units, OTel,
scripts plugin), and expanded Go plugin with SNMP overhaul.
* 2.10.x stabilization: fix ZFS-related crashes, eBPF shared-memory
pool leak, SNMP counter wrapping, database engine memory safety.
* 2.10.4: larger patch for stability, memory safety, and crash
resilience across database engine, streaming, and collectors;
backports new macOS hardware sensor collectors.
Recipe changes:
* Add curl and openssl to mandatory DEPENDS (both now REQUIRED by
cmake); remove PACKAGECONFIG[openssl] and PACKAGECONFIG[cloud].
* Remove webui_v0/v1/v2 PACKAGECONFIG entries and associated
do_install block (the webui architecture changed in 2.x).
* Remove -DENABLE_ACLK=OFF from EXTRA_OECMAKE (option no longer
exists); keep -DENABLE_EXPORTER_PROMETHEUS_REMOTE_WRITE=OFF.
* Refresh 0002-Do-not-hardcode-systemd-unit-directories.patch for
2.10.4 (the BUILD_FOR_PACKAGING/systemd service install blocks
shifted ~1119 lines; same substitution preserved).
* 2.x vendors its own libsensors copy which needs flex/bison to
generate its config lexer/parser at build time; add flex-native
and bison-native to DEPENDS.
* Protobuf detection now runs unconditionally (used by several 2.x
exporters/collectors even with the remote-write exporter disabled);
add protobuf and protobuf-native to DEPENDS and point cmake at the
native protoc via Protobuf_PROTOC_EXECUTABLE.
* Disable several 2.x features that reach out to the network at
configure time and cannot work in an offline build:
- ENABLE_PLUGIN_OTEL / ENABLE_PLUGIN_OTEL_SIGNAL_VIEWER (pull in
Rust/Corrosion via CMake FetchContent)
- ENABLE_PLUGIN_SCRIPTS (requires Go, same as ENABLE_PLUGIN_GO)
- ENABLE_ML (FetchContent-downloads dlib)
- ENABLE_LIBBACKTRACE (ExternalProject-downloads libbacktrace)
- ENABLE_DASHBOARD, now exposed as PACKAGECONFIG[dashboard] and
off by default (the local agent dashboard isn't shipped in the
release tarball; enabling it makes cmake fetch it from
app.netdata.cloud at configure time)
* BUILD_FOR_PACKAGING=ON now also installs sysusers.d/tmpfiles.d
snippets under ${nonarch_libdir}; remove them in do_install since
user creation is handled by useradd.bbclass and tmpfiles by our own
netdata-volatiles.conf, avoiding an "installed but not shipped" QA
failure from duplicate/unmanaged files.
* Fix three new-in-2.x reproducibility leaks that embed host build
paths into the packages (buildpaths QA, an error in oe-core's default
ERROR_QA):
- Add 0003-Do-not-record-the-configure-command-line-in-the-binar.patch:
2.x bakes the full cmake invocation into config.h for
"netdata -W buildinfo"; the collected flags include --sysroot= and
-ffile-prefix-map= and so leak ${WORKDIR} into the binary.
- Add 0004-libsensors-do-not-emit-line-directives-in-generated-s.patch:
pass bison -l / flex -L so the generated conf-parse.[ch] and
conf-lex.c do not carry absolute #line paths (these live in file
contents, so -ffile-prefix-map cannot rewrite them).
- Remove the shipped build-info-cmake-cache.gz in do_install: it is a
gzipped CMakeCache.txt kept only for buildinfo reporting and is full
of host paths.
Verified with buildpaths promoted back to ERROR_QA: netdata builds and
packages with no buildpaths diagnostics and no /home path remains
anywhere under the package tree.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
This fixes:
WARNING: hyprland-image-1.0-r0 do_rootfs: User colord has been defined as (colord, 998, 998, -, /home/colord, /bin/false) but sysusers.d expects it as (colord, -, -, colord colour management daemon, /var/lib/colord, -)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
New Features:
- Add symbol and sample text for Amharic and Inuktitut
- Add symbol text for N'Ko and Yi script
Bugfixes:
- Fix building the silo when shared-mime-info >= 2.5.1 is installed
- Fix RISC-V test failure
Signed-off-by: Ankur Tyagi <ankur.tyagi85@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
oe-core 3c2bb7bce1 ("cpan_build: disable .packlist and html doc") moved
--create_packlist=0 into cpan_build.bbclass and disabled html doc
generation there as well. Neither .packlist nor the html docs are
generated anymore, so the do_install:append() hooks that sed'ed TMPDIR out
of them now run find(1) over paths that no longer exist and hand sed an
empty argument list:
find: '.../image/usr/share/doc/perl/html/site/lib/HTML/': No such file or directory
sed: no input files
WARNING: exit code 4 from a shell command.
Remove the now dead hooks.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
cmake's check_symbol_exists() does not forward CMAKE_REQUIRED_FLAGS to the
try_compile() it runs, unlike check_include_file() and
Internal/CheckSourceCompiles which both pass it along as
-DCOMPILE_DEFINITIONS. So the -D_GNU_SOURCE=1 that SDL adds to
CMAKE_REQUIRED_FLAGS never reaches any symbol check, and every glibc
extension hidden behind __USE_GNU is detected as missing.
HAVE_GETRESUID being unset is fatal, since SDL_gtk.c then compiles its own
static fallback which collides with the <unistd.h> declaration:
SDL_gtk.c:90:19: error: static declaration of 'getresuid' follows
non-static declaration
Pass _GNU_SOURCE via CMAKE_REQUIRED_DEFINITIONS as well. This also restores
detection of memfd_create, ppoll, posix_spawn_file_actions_addchdir,
fopen64 and fseeko64, which were silently disabled.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
binutils 2.47 removed the bfd_boolean compatibility define along with the
TRUE/FALSE macros it brought in, see binutils commit 1d95b744c069 ("Remove
bfd_boolean definition from bfd"). This breaks oprofile:
opagent.c:81:2: error: use of undeclared identifier 'bfd_boolean'
create_bfd.c:68:18: error: 'FALSE' undeclared
Add a patch using bool/false from <stdbool.h> instead, which is what the
bfd API has been returning since binutils 2.36.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 0.141.1:
- Fix support for background tasks and headers from dependencies in
app.frontend().
- Document FASTAPI_ENV in FastAPI CLI guide.
Add DESCRIPTION and SUMMARY variables.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 1.0.0:
- Minimum supported Python is now 3.9 (Python 2 dropped).
- PatchedFile.path now also strips git mnemonic prefixes (c/ i/ o/
w/ and 1/ 2/), so git diff --cached paths resolve to the plain
filename (c/README.md -> README.md). Standard a//b/ diffs are
unaffected.
- File modes via source_mode/target_mode + an is_symlink property.
- PatchedFile.diff_line_no to locate hunkless/binary entries.
- Accept bytes input directly (decoded with the given encoding,
default UTF-8).
- Real PEP 484 type annotations + generics (typed iteration) and a
py.typed marker.
- Parse difflib empty-filename output and fix a trailing-newline
error on hunkless git format-patch files; includes the
quoted-filename fix missing from 0.7.5
- from_filename/from_string gain metadata_only; python -m unidiff
works; packaging on pyproject.toml with GitHub Actions CI.
Fixes:
WARNING: python3-unidiff-1.0.0-r0 do_check_backend: QA Issue:
inherits setuptools3 but has pyproject.toml with
setuptools.build_meta, use the correct class [pep517-backend]
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 1.4.2:
- Stop mutating global asyncio event loop policy on import
- Importing pika.adapters can break asyncio subprocesses on Windows
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upgrade to release 2.3.0:
- The __trunc__(), __floor__() and __ceil__() special methods are
now implemented by object proxies, delegating to math.trunc(),
math.floor() and math.ceil() applied to the wrapped object. As
with other special methods, these are only looked up on the class
type and not the instance, so they cannot rely on the __getattr__()
fallback of the proxy and must be implemented explicitly. Previously
calling math.trunc() on an object proxy raised TypeError. These
special methods sit somewhat outside the core Python object model
in that they are not used by any builtin operators, with the math
module being their only consumer. They are however documented as
part of the Python data model and the math module is a key module
in the standard library, so supporting them is warranted, in the
same way as the existing support for __round__(), which is
consumed by the round() builtin. Note that although math.floor()
and math.ceil() previously appeared to work when used on an object
proxy, they were silently falling back to converting the proxy
using __float__(). If the wrapped object provided its own
__floor__() or __ceil__() special methods these were ignored and
the result could differ from that when the wrapped object was
used directly. These now yield the same result as using the
wrapped object directly. With thanks to Vincent Gao for the PR.
- The __fspath__() special method of the os.PathLike protocol has
been added to the set of dunder methods which AutoObjectProxy
detects on the wrapped object and adds to the class it
generates, so a proxy it creates around a path-like object can
now be used with os.fspath(), the builtin open() and other
standard library functions accepting paths. Note that
__fspath__() is deliberately not implemented by the base
object proxy, since its presence on the proxy type would
cause every proxy to be classified as path-like by code
branching on isinstance(obj, os.PathLike). Also be aware
that AutoObjectProxy creates a new class for every proxy
instance, so it should not be used to wrap path-like
objects in large numbers due to the memory overhead. For
high-frequency use define a custom proxy class which adds an
explicit __fspath__() method instead. See the section on
wrapping path-like objects in the known issues documentation
for more details.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
This will align it to oe-core systemd recipe.
Download mirror will contain only one repository copy, not two.
Signed-off-by: Peter Marko <peter.marko@siemens.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
- Inherit ptest-python-pytest and include tests for py7zr.
- Switch from PyPI to using the source code from GitHub to
download the tests.
- Remove liblzma pre-stripped binaries because they are not
neeed and to avoid the already-stripped QA errors.
- Add python3-pytest-httpserver and other runtime dependencies
for the tests.
This work was sponsored by GOVCERT.LU.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Add recipe for pytest_httpserver, a HTTP server for pytest.
Changelog for release 1.1.5:
- Add bake() method for pre-configured request expectations
This work was sponsored by GOVCERT.LU.
Signed-off-by: Leon Anavi <leon.anavi@konsulko.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Upstream changes (NEWS):
* dump.exfat: prevent a heap buffer overflow in name parsing.
* Install lsdosattr and chdosattr in /bin instead of /sbin (covered by
the default FILES:${PN}, so packaging is unaffected).
* libexfat: use __builtin_popcountl() throughout and add an internal
exfat_count_used_clusters() helper (static lib, no ABI impact).
No dependency or build-system changes; configure.ac is unchanged, so
DEPENDS and the ptest install steps stay as-is.
While enabling the ptest image (meta-filesystems-image-ptest-exfatprogs)
on qemux86-64, the upcase_table test cases (present since 1.4.0, so this
is a pre-existing failure now exercised) failed because they used
`truncate` and `xxd -r - <file>`, which are unavailable in a BusyBox
core-image-minimal rootfs:
truncate: command not found
FAIL: to create corrupted image
Add 0001-tests-upcase_table-use-dd-printf-instead-of-truncate.patch,
which rewrites those scripts to size the image with dd and poke the
corrupted bytes with printf|dd (tools already present in the base
image). ptest result on qemux86-64 is now 23 of 23 passing.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
387 commits across 21 fortnightly releases (739 files changed,
+16397/-2042). 114 new tests added (xfs x44, generic x32, btrfs x16,
f2fs x14, ext4 x3, overlay x2, selftest x2, ceph x1) and one removed
(xfs/539).
Major themes:
* Multi-block atomic writes: new common/atomicwrites, fio atomic-write
helpers, fsx atomic-write support, and O_[D]SYNC / sudden-shutdown /
bigalloc / hardware-AWU atomic tests.
* XFS zoned / RT-device work: common/zoned with zloop helpers, zoned
growfs, zone-alignment mkfs checks, zone GC low-space, external and
internal realtime device support.
* New xfs_healer test family (background repair service).
* file_getattr(2)/file_setattr(2) support (new src/file_attr.c,
AC_HAVE_FILE_GETATTR probe), VFS delegation tests, and a new
fsnotify/fanotify error-reporting helper (src/fs-monitor.c).
* Infrastructure: treewide $MOUNT_PROG -> _mount conversion, temp
files moved to $TMPDIR, systemd-coredump collection in check.
Build-system: configure.ac gains AC_HAVE_FILE_GETATTR and a
btrfs_ioctl_received_subvol_args type check; src/Makefile adds
unlink-fsync, truncate, rw_hint, fs-monitor, btrfs_ioctl and a
conditional file_attr target. No new link libraries, so no DEPENDS
change is needed. LICENSE checksum unchanged.
Recipe patch changes:
* Drop 0002-Drop-detached_mounts_propagation-and-remove-sys-moun.patch:
its rationale (glibc sys/mount.h vs linux/mount.h clash reached via
src/vfs/utils.c) no longer applies because utils.c no longer includes
sys/mount.h, and the src/Makefile hunk no longer applied anyway.
* Add 0001-locktest-do-not-tie-struct-delegation-to-the-F_GETDE.patch:
glibc 2.43 defines F_GETDELEG/F_SETDELEG but neither glibc nor the
kernel UAPI declares struct delegation, so tying the struct to the
"#ifndef F_GETDELEG" guard leaves it undefined and locktest fails to
build with "variable has incomplete type 'struct delegation'".
Also bump the bundled unionmount-testsuite by one commit
(dir-weird-open-dir.py adjusted to the upstream kernel).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Move from the v2.2.y stable branch to the v2.3.y line (tag v2.3.1,
2026-06-19). v2.3.x carries all v2.2.6..v2.2.16 backports plus the
2.3.0 rework.
Security:
* CVE-2026-55392: validate s_log_block_size in nilfs_sb_is_valid().
A crafted NILFS2 image with s_log_block_size > 6 caused oversized
shifts / huge allocations in nilfs-tune, dumpseg and any tool
reading a device.
2.3.0 highlights:
* Utilities (lscp, lssu, nilfs-clean, ...) accept file/directory
arguments and auto-resolve the backing device.
* cleanerd: cap segments per cleaning step by free segments (avoids
stalling near ENOSPC) and against 32-bit size_t overflow; clean
SIGINT exit, SIGUSR1 state dump.
* Library refactor with an API/ABI break: obsolete APIs and internal
structs removed from public headers, new segment I/O / resize /
freeze-thaw APIs, types unified to uint32_t/uint64_t/bool.
* mkfs.nilfs2 sets the block-count read-only-compat flag by default.
Packaging-relevant build-system changes:
* Soname bump libnilfs/libnilfsgc 2 -> 3; libnilfscleaner is no longer
a shared library (now an internal convenience lib), so
libnilfscleaner.so.* correctly disappears from the runtime package.
* New pkg-config producer files (nilfs.pc, nilfsgc.pc) land in
${libdir}/pkgconfig -> require inherit pkgconfig.
* LT_INIT([disable-static]) means static libs are no longer installed.
* The old --with-base-sbindir knob was replaced upstream by an
--enable-usrmerge=(no|sbin|bin|auto) mechanism. Drop the local
0001-configure.ac-Add-knob-to-define-base-sbindir.patch and select
the hierarchy explicitly from DISTRO_FEATURES, because the "auto"
default probes the build host and is wrong when cross compiling.
LDCONFIG=true is still required.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Advance the SRCREV by 14 commits to the current master tip
(474b3acb, committed 2026-06-29) and bump PV to that commit date per
the recipe's date-based versioning convention.
Notable changes in this range (Aleph One / Charles Manning):
* yaffs_guts.c: fix the size of the allocated buffer for unmanaged
buffers (real bugfix).
* Fully deinitialise the cache when unmounting (real bugfix).
* yaffs_guts.c: use AND instead of remainder for hash calculation.
* Move Linux attribute handling out of the core into
yaffs_linux_attribs.c (affects only the out-of-tree kernel module,
which this recipe does not build).
* Remove K&R function declarations, silence gcc warnings on the dtest
filename array, several benign typo/whitespace cleanups, and
power-fail stress-test reporting improvements.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Two upstream stable point releases. The "2.4.99" that the automated
version checker reports is the OpenZFS development/META tag on master,
not a real release; 2.4.3 is the newest 2.4.x stable.
2.4.2:
* Linux mount API rewrite: a new fs_parse-based mount-parameter parser
replaces the legacy options parser and zpl_parse_monolithic; support
for the old mount API is removed and the build now refuses to build
without fs_context. vfs_t lifetime is tied to fs_context.
* Linux 7.0/7.1 compatibility: fs_context shims, explicit setlease
handler (also for directories), posix_acl_to_xattr() allocation,
blk_queue_nonrot()->blk_queue_rot(), removal of the minimum kernel
version check.
* dRAID fixes: checksum errors after rebuild with degraded disks,
import failure after disk replacement, data corruption after disk
clear, sequential-resilver reads from degraded vdevs.
* Data-integrity fixes: read corruption after block-clone-after-
truncate, range-tree corruption race in dnode_sync(), a
use-after-free in dmu_write_direct_done(), "kernel BUG at
mm/usercopy.c".
* New feature: POSIX_FADV_DONTNEED support.
* Build: SPDX tags + spdxcheck enforcement, "make dist" uses pax tar,
objtool taken from $kernelbuild.
2.4.3:
* Security/robustness hardening: enforce exact decompressed length for
lz4/gzip/zstd, validate size fields/strings and reject un-terminated
strings in packed nvlists, sharenfs invalid-character check, extended
zfs_ioc_set_prop() secpolicy, key lookup failures always return
EACCES, ZVOL encryption-key check for block cloning, and removal of
/etc/sudoers.d/zfs.
* Correctness: double free for blocks cloned after DDT prune, off-by-
one in the redaction handler dropping the last block, several
lock-ordering/lockdep fixes, FreeBSD cache_vop_rename panic fix.
* Linux: properly apply ro/rw mount option to the superblock, Linux 5.6
fs_parse API mismatch fix, spl_kvmalloc strips __GFP_COMP before
vmalloc().
* aarch64 build failure fixed by removing earlyclobber.
Supported kernel range is now 4.18 - 7.0.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
python3-black RDEPENDS on python3-pytokens, so extending black to native and
nativesdk only moves the "Nothing RPROVIDES" warning one level down unless
pytokens is extended as well.
pytokens has no runtime dependencies of its own and only needs
python3-mypy-native to build, so it is safe to extend.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
python3-pytest-examples is built for native and nativesdk and RDEPENDS on
python3-black, but black itself was never extended, so parsing universe warns:
WARNING: Nothing RPROVIDES 'nativesdk-python3-black' (but
virtual:nativesdk:...python3-pytest-examples_0.0.18.bb RDEPENDS on or
otherwise requires it)
WARNING: Nothing RPROVIDES 'python3-black-native' (but
virtual:native:...python3-pytest-examples_0.0.18.bb RDEPENDS on or
otherwise requires it)
and both python3-pytest-examples-native and nativesdk-python3-pytest-examples
end up unbuildable and get dropped.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
tests/cc passes -DCMAKE_CURRENT_BINARY_DIR="${CMAKE_CURRENT_BINARY_DIR}" to
every test object so the tests can find archive.zip, the debuginfo libraries
and dummy_proc_map.txt at runtime. That put 13 copies of the absolute build
directory into the installed test binary:
QA Issue: File /usr/lib/bcc/ptest/tests/cc/test_libbcc_no_libbpf in package
bcc-ptest contains reference to TMPDIR [buildpaths]
and, on autobuilders whose TMPDIR sits below $HOME, additionally:
QA Issue: ... contains a reference to the build host HOME directory.
The recipe worked around this by installing the assets to ${D}${B}/tests/cc,
i.e. by reproducing the build path inside the image, and by demoting
buildpaths to a warning.
Add a patch introducing a TEST_ASSET_DIR cache variable, defaulting to
CMAKE_CURRENT_BINARY_DIR so the upstream default is unchanged, and point it at
${PTEST_PATH}/tests/cc. The assets are now installed next to the test binaries
and no build path is embedded, so the buildpaths overrides can go away.
Also install dummy_proc_map.txt, which the tests reference but which was never
shipped.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
wxPython's pyproject.toml declares setuptools.build_meta, so do_check_backend
warns:
QA Issue: inherits setuptools3 but has pyproject.toml with
setuptools.build_meta, use the correct class [pep517-backend]
Switching to python_setuptools_build_meta is not possible though. The sdist
ships a build.py in its top level directory which shadows the "build" module
that pyproject-build imports itself, so do_compile dies before it even looks
at the recipe:
File ".../recipe-sysroot-native/usr/bin/pyproject-build", line 5, in <module>
from build.__main__ import entrypoint
ModuleNotFoundError: No module named 'build.__main__'; 'build' is not a package
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
uefi-firmware-parser's pyproject.toml declares setuptools.build_meta as its
build backend, so setuptools3 is the wrong class and do_check_backend warns:
QA Issue: inherits setuptools3 but has pyproject.toml with
setuptools.build_meta, use the correct class [pep517-backend]
Unlike setup.py, pyproject-build honours the declared build requirements, so
the setuptools_scm dependency has to be provided explicitly, otherwise
do_compile fails with:
ERROR Unmet dependencies ...
setuptools-scm>=8.0
wanted: >=8.0
found: not installed
setup.py passes use_scm_version to setup(), which was silently discarded
before ("Unknown distribution option: 'use_scm_version'"), so the package used
to ship its metadata as uefi_firmware-0.0.0.dist-info. Pin the version to
${PV} so the directory is now correctly named uefi_firmware-1.16.dist-info.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
canopen's pyproject.toml declares setuptools.build_meta as its build backend,
so setuptools3 is the wrong class and do_check_backend warns:
QA Issue: inherits setuptools3 but has pyproject.toml with
setuptools.build_meta, use the correct class [pep517-backend]
Unlike setup.py, pyproject-build honours the declared build requirements, so
the setuptools_scm dependency has to be provided explicitly, otherwise
do_compile fails with:
ERROR Unmet dependencies ...
setuptools_scm>=8
wanted: >=8
found: not installed
setuptools_scm was silently ignored before, so the package used to ship its
metadata as canopen-0.0.0.dist-info. Pin the version to ${PV} so the
directory is now correctly named canopen-2.4.1.dist-info.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
thrift's pyproject.toml declares setuptools.build_meta as its build backend,
so setuptools3 is the wrong class and do_check_backend warns:
QA Issue: inherits setuptools3 but has pyproject.toml with
setuptools.build_meta, use the correct class [pep517-backend]
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changes:
- Add floating panes: non-modal panes that sit above the tiled layout,
created with the new new-pane command (bound to * by default). Early,
currently limited release (move/resize via mouse only).
- Allow run-shell arguments after the shell command to be expanded as
#{1}, #{2}, and so on.
- Add -g to kill-session to kill all sessions in a session group.
- Add line numbers in copy mode via the new copy-mode-line-numbers option
(off/default/absolute/relative/hybrid) plus matching styles.
- Tighten read-only checks on attach-session, detach-client and
switch-client; various control-mode and paste-detection fixes.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changes across the 6.24.13 - 6.24.16 maintenance releases:
- Handle redirections in bracketed expressions, e.g. if { foo > /dev/null }.
- Recognize history searches in history expansion (!?foo<tab>).
- Fix !^:h and !^:t failing when no / is found.
- Add cross-build support for the gethost helper; add support for $?<.
- Fix issues with S-JIS handling; improve nls/Makefile.in compatibility hacks.
Makefile changed the gethost host-helper rule to use
CPPFLAGS_FOR_BUILD / CFLAGS_FOR_BUILD, which lack the -I. -I$(srcdir) include
paths, so the configure-generated config.h was invisible and do_compile failed.
Set EXTRA_OEMAKE CC_FOR_GETHOST and {CFLAGS,CPPFLAGS,LDFLAGS}_FOR_BUILD from
the BUILD_* vars and simplified do_compile:prepend to 'oe_runmake gethost'.
The *_FOR_BUILD vars are only consumed by the gethost rule, so the target
build is unaffected.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Version-locked to oe-core's gstreamer1.0 1.28.4; this jump spans the 1.24,
1.26 and 1.28 stable cycles.
Notable GES changes by 1.28:
- GESPipeline manages a shared task pool (auto-sized to the number of
processors), with apps able to supply their own via context negotiation.
- New thread-safe controller API for control-point access, fixing
use-after-free issues in the old API.
- The OpenTimelineIO formatter moved to a standalone Python plugin in
gst-python.
- Framepositioner z-order is now exposed/controllable; new APIs for detecting
clip layer movement, a GES error domain, and improved timeline error
reporting.
License-Update: COPYING and COPYING.LIB
(6762ed442b3822387a51c92d928ead0d -> 69333daa044cb77e486cc36129f7a770).
Upstream replaced the stale "GNU LIBRARY General Public License, Version 2"
text with the correct "GNU LESSER General Public License, Version 2.1" file;
the declared LICENSE (GPL-2.0-or-later AND LGPL-2.1-or-later) is unchanged and
is now more accurately matched.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changes (2.10; 2.09 shipped no separate release notes):
- Recognize new languages and file types: Beluga, C3, CodeQL, DAML, Quxlang,
Rhai and Slang.
- Skip the contents of .venv directories.
- Add --by-percent support with the --fmt formatting styles.
- Support process substitution as input to --sum-reports (Unix-like systems).
- Treat wscript as a filename rather than an extension; assorted bug fixes.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changes within the 7.0 LTS branch:
- 7.0.28: raise the maximum supported MariaDB (12.3), MySQL (9.7) and
TimescaleDB (2.27) versions; update VMware alarm discovery; fix excessive
history upload delay for Zabbix agents (ZBX-27495); assorted frontend/agent
fixes.
- 7.0.29: raise the maximum supported TimescaleDB version to 2.28; fix a
potential VMware collector crash on vCenter connectivity loss (ZBX-27975);
fix RabbitMQ template duplicate discovery keys; fix trend-average producing
inf values (ZBX-27453); fix remote command execution for trigger actions
when the target host is monitored by a proxy group (ZBX-27665).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Deliberately switch from the conservative 2.0.x branch to upstream's
recommended 2.1.x line (upstream describes 2.0.x as "provided for the more
conservative distros" and recommends 2.1.x for most users).
Notable changes across the 2.1.x arc:
- Remove the flashrom plugin (2.1.0).
- Add native CBOR parsing and drop the libcbor2 dependency (2.1.2).
- No longer depend on json-glib, libarchive or protobuf-c (2.1.2).
- Add a systemd-pcrlock plugin wired into UEFI updates; add MTD lock and TCG
disk-encryption security attributes and support for externally-managed EFI
signature lists; enable more plugins when compiling for Android.
- Security/robustness: require trusted metadata for device updates, disallow
force installs over D-Bus, and numerous segfault / out-of-bounds-read fixes.
2.1.x removed the cbor, libarchive, plugin_flashrom and protobuf
meson options. Removed plugin_flashrom and protobuf from the default
PACKAGECONFIG, deleted the now-dead PACKAGECONFIG for libarchive,
plugin_flashrom, protobuf
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Khem Raj
Markus Volk
Ankur Tyagi
Ross Burton
Leon Anavi
Jason Schonberg
Peter Marko
Gianfranco Costamagna
Wang Mingyu
Khem Raj