xtkoba

Seems to work well with zsh (using `mcfly 0.5.12` and `zsh 5.8.1` packages in the Termux official repository).

Does anyone else reproduce this?

I would suggest using `strace` command: ```bash strace -f dbus-daemon --system ``` Also `logcat` might help, if the system under Termux is killing the daemon.

I don't like this.

> Writing guidelines on how commits should preferably be written should be a good idea in any case. This is true. We have seen a bunch of PRs of which...

My proposal: * If a commit is about to modify a single package, then the subject should contain the package name. And only this. Unnecessarily complex rules are just hard...

CI runs for all 4 architectures. But you can temporarily set `TERMUX_PKG_BLACKLISTED_ARCHES`: ```bash TERMUX_PKG_BLACKLISTED_ARCHES="arm, i686, x86_64" ``` CI for an excluded arch normally finishes in 3 to 4 minutes.

I see the following lines in `$PREFIX/include/QtCore/qtcore-config.h` of the artifact: ```c #define QT_FEATURE_sharedmemory -1 #define QT_NO_SHAREDMEMORY ``` and ```c #define QT_FEATURE_systemsemaphore -1 #define QT_NO_SYSTEMSEMAPHORE ``` I doubt if this PR...

This is caused by a bug in GNU Binutils 2.35 which is fixed in 2.35.2. Upstream issue: https://sourceware.org/bugzilla/show_bug.cgi?id=27128. We could make the test skipped for the buggy versions of `nm`,...

A test failure due to a behavior change in OpenSSL 3.0.0 (https://github.com/openssl/openssl/issues/16321): ``` 1) Failure: OpenSSL::TestHMAC#test_hmac [test/openssl/test_hmac.rb:12]: expected but was . ``` A repro for convenience: ```ruby require "openssl" instance...