The cross-canadian variant did not build. Several issues:
1. DEPENDS used :append on top of crash.inc's target DEPENDS. cross-canadian
does not remap DEPENDS to nativesdk, so the target zlib/readline/ncurses/
gmp/mpfr stayed in the dependency set and staged a real target usr/lib into
the recipe sysroot, clashing with the nativesdk toolchain (clang-glue
provides usr/lib as a symlink) during do_prepare_recipe_sysroot. Override
DEPENDS with the nativesdk set instead (matching gdb-cross-canadian) and add
the -native build tools the build needs.
2. do_compile hardcoded ${HOST_PREFIX}gcc, which does not exist on clang based
SDKs (TOOLCHAIN = "clang"), giving "C compiler cannot create executables".
Use the toolchain-aware ${CC}/${CXX} like the other variants.
3. crash's gdb merge re-enters the top-level crash Makefile from gdb's link
rule ("make -C ../.. ... library") without passing the compiler, so crash's
own objects fell back to the Makefile default $(CROSS_COMPILE)gcc and failed
to find a compiler on clang SDKs. Forward CC/CXX through that recursion in
the bundled gdb-16.2.patch; this is harmless where ${cross}-gcc exists.
Verified by building crash, crash-native, crash-cross and
crash-cross-canadian-x86-64 for a clang based SDK (qemux86-64).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The bundled gdb 16.2 hard-requires GMP and MPFR (crash 8.0.6 bundled gdb 10.2,
which did not). native.bbclass remaps DEPENDS to their -native variants
automatically, so crash-native builds, but cross.bbclass does not - so
crash-cross failed in gdb's configure with:
configure: error: Building GDB requires GMP 4.2+, and MPFR 3.1.0+.
List the build-host dependencies (gmp/mpfr, plus readline/ncurses that crash
links) explicitly for class-cross.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The recipe passed --with-sysroot=${STAGING_DIR_TARGET} to the bundled gdb's
configure. gdb bakes that path in as its default target sysroot, so the
resulting /usr/bin/crash binary embedded the build-time recipe-sysroot path:
File /usr/bin/crash in package crash contains reference to TMPDIR [buildpaths]
This was worked around by demoting the buildpaths QA check to a warning
(ERROR_QA:remove / WARN_QA:append), which only hides the problem - the build
path is still wrong for a binary that runs on the target (or, for the
cross-canadian variant, in the SDK).
Set --with-sysroot=/ instead. crash takes the kernel/vmlinux and dump on its
command line, so gdb's compiled-in default sysroot is irrelevant at runtime;
"/" is both a sane default and contains no build path. With this the binary
no longer references TMPDIR, so the QA suppression can be removed and the
buildpaths check passes for real.
Verified with a clean build for qemux86-64: no buildpaths QA issue and no
TMPDIR references remain in the crash binary.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The do_compile:prepend ran "git init && git add . && git commit" inside the
staged gdb-16.2 tree. crash's build does not use git at all - the bundled gdb
is unpacked from a release tarball and merged with plain "patch -p0" - so this
served no purpose and only made the build depend on a working git identity.
In any environment where committer identity is unset, or where commit signing
is enabled globally (commit.gpgsign=true), do_compile fails with:
error: gpg failed to sign the data
fatal: failed to write commit object
Drop the git scaffolding entirely; the gdb patch still applies with patch(1).
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
std::allocator::construct was removed in C++20 (GCC 16 default).
Rewrite 0006-gdbsupport-fix-default-init-alloc to include <memory>
guard the using-declaration to pre-C++17, and add a forwarding
construct() overload.
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
The recipe was suppressing errors by including
'--compile-no-warning-as-error' and removing '-Werror=format-security'
from SECURITY_STRINGFORMAT. Remove both workarounds and carry upstream
patches that fix the underlying warnings instead.
Signed-off-by: Antonios Christidis <a-christidis@ti.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changes in 1.18.0
~~~~~~~~~~~~~~~~~
Released: 2026-06-08
Enhancements:
* Improve error handling and printed output of `flatpak-coredumpctl` (#6649,
#6680)
* Support the AMD vendor specific compute interface (`/dev/kfd`) via the DRI
device permission (#6648)
* Improve the output of `flatpak update` with failure causes (#6657)
* Improve startup time for fish shell integration (#6635)
* Translation updates: zh_CN (#6671)
Bug fixes:
* Fix building when HAVE_LIBSYSTEMD but not USE_SYSTEM_HELPER is defined (#6652)
* Ignore system bus failures in parental controls check (#6663)
* Fix some return values and replace deprecated `GTimeVal` with
`g_get_real_time()` (#6646)
* Suppress an unused-result warning in the tests (#6655)
Changes in 1.17.7
~~~~~~~~~~~~~~~~~~
Released: 2026-05-06
Enhancements:
* Add the new permission conditionals `has-usb-device` and `has-usb-portal` to
allow apps to drop --device=all and --device=usb permissions (#6560)
* Always send the `Flatpak-Upgrade-From` header when updating instead of
freshly installing, to improve the quality of statistics (#6626)
* Improve how the absence of the system repo is handled (#6621)
* Changes to repos are now more atomic which helps to avoid them being in an
invalid state. This could be observed when importing the GPG key failed,
because the system clock was wrong. (#6547)
* A function to report the age of the configuration was added to libflatpak,
which will help GNOME Software to prevent unnecessary work (#6532)
* Improvements to the build system (#6614, #6610)
* Improve various tests (#6604, #6606, #6619, #6617, #6605, #6625)
* Translation updates: tr (#6629), zh_CN (#6630)
Bug fixes:
* Fix a regression in handling of the fallback-x11 permission, which was
affecting overrides from Flatseal (#6632)
* Fix a memory leak in the Flatpak portal (#6613)
* Install SELinux configuration files to the right directory (#6622)
* Silence wrong `lseek()` errors when creating sub-sandboxes (#6609)
Signed-off-by: Markus Volk <f_l_k@t-online.de>
Upgrade zbar from 89e7900d85dd (2020-12-31) to 0.23.93 (2024-01-09).
Removed all patches because they have been merged upstream.
Enabled pthread integration by default and renamed configs to match
upstream.
Tested the python API and gstreamer integration, I wasn't able to test
any of the various package configs that are related to GUIs because I
don't have a access to boards with displays.
Signed-off-by: Walter Werner Schneider <contact@schnwalter.eu>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
lftp 4.9.3 bundles gnulib sources that fail to build with the OpenEmbedded
clang + lld toolchain. Carry a single patch with the gnulib compatibility
fixes:
1. Single-argument static_assert (lib/dirent.in.h, lib/uchar.in.h) is a
C++17 feature; clang in its default C++14 mode rejects it with
"static_assert with no message is a C++17 extension". Add a message.
Reported upstream: https://github.com/lavv17/lftp/issues/766
2. lib/stdlib.in.h pre-includes <string> to pre-instantiate std::strtoull
before the "#define strtoull rpl_strtoull" macro fires, but guarded the
workaround with "&& !defined __clang__" so it never triggered under
clang + libstdc++, rewriting std::strtoull to the non-existent
std::rpl_strtoull. Extend the guard to cover clang.
3. After gnulib split md5.c/sha1.c into primary + -stream.c files, both
define GL_OPENSSL_INLINE to _GL_EXTERN_INLINE before including the
header, so with the OpenSSL md5/sha1 backends both translation units
emit out-of-line wrapper copies and lld fails with duplicate symbol
errors. Drop the override from the -stream.c files.
Consolidates the three previously separate patches into one; verified by
building lftp for qemux86-64 with clang + lld (the duplicate-symbol link
failure reproduces without the patch and is resolved with it).
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
0001-build-Do-not-display-full-path-in-generated-headers.patch
removed since it's included in 4.21.2
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
0001-feat-Add-option-in-cmake-to-remove-awk.patch
0002-feat-Add-option-in-autotools-to-remove-awk.patch
removed since they're included in 4.12.0
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
============
- Add Pytest 9 support
- Add Python 3.14 support
- Keep latest Pytest tests on supported Python versions
- Refactor CI to use the tox test matrix
- Replace pre-commit workflow with prek and mise
- Add Context7 project metadata
- Update linting tools
- Update GitHub Actions versions
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
=============
- Fix exception leaks
- MsgpackSerializer.loadsCall: honor ext_hook (symmetric with loads)
- Fixed slow locate_ns() on Windows: skipped reverse DNS lookup of 127.0.1.1 which caused 5+ second delays due to DNS timeout.
- Fixed exception leaks in message handling
- Fixed GC issue with daemon property
- Fixed thread race condition in nameserver remove()
- Fixed possible resource leaks in client
- Fixed IPv6 NAT port parse error in server
- Fixed crash related to None environment variable handling
- Fixed a deadlock scenario when using multiple proxies with different daemon connections
- Improved logging performance by avoiding eager string formatting
- Gracefully handle unreachable network in ip address resolution fallback
- Fixed potential socket leak from broadcast discovery when nameserver is unreachable
- Added extra message protocol validation for robustness
- Fixed nameserver metadata lookup returning incorrect results for None values
- Fix msgpack serializer loadsCall to make sure custom arguments get properly deserialized
- Various documentation and spelling corrections
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
===========
- Filesystems may now define a ~Operations.poll method to support the epoll and select system calls.
- The FileHandleT and InodeT types are no longer declared as NewTypes but are now simply aliases for int.
- Future releases of pyfuse will be signed with signify rather than GPG.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
Fix a segfault when calling Unpacker.unpack() or Unpacker.skip() after an unpacking failure.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
- Fixed snapshot updates when pytest reuses stale assertion-rewrite cache files
after a test folder is moved, which could leave cached code objects pointing at
the old source path
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
===========
- make RAB feature production ready
- run async background boundary refresh on detached session
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
============
- Make sure client disconnects when write loop exits
- Address flaky unit test
- Stop using codecov service, since it has been failing for a long time
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Changelog:
===========
- Fix: some messages were being written to stdout, making coverage json -o -
useless for capturing JSON output. Now messages are written to stderr
- Fix: CoverageData kept one SQLite connection per thread that recorded
coverage, but never closed them when those threads terminated. On long runs
with many short-lived threads this leaked one file descriptor per dead thread,
eventually failing with OSError: [Errno 24] Too many open files. Connections
belonging to terminated threads are now closed and dropped.
- Fix: when using sys.monitoring, we were assuming we could use the COVERAGE_ID
tool id. But other tools might also assume they could use that id.
Pre-allocated ids don't really make sense, so now we search for a usable one
instead.
- Following the advice of cibuildwheel, we no longer distribute wheels for
Python 3.13 free-threaded.
- Fix: the default exclusion rule now also matches function bodies whose
closing return-type bracket is on its own line (for example, after a long ->
dict[...] annotation that a formatter has split over multiple lines).
- Fix: On 3.13t, we incorrectly issued Couldn't import C tracer errors. We
can't import the C tracer because in 7.14.2 we stopped shipping compiled
wheels for 3.13t.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <khem.raj@oss.qualcomm.com>
Khem Raj
Robert Berger
Antonios Christidis
Markus Volk
Walter Werner Schneider
Hemanth Kumar M D
Sandeep J
Wang Mingyu