This drops most of our SSL/auth patches.
Also this update also ships a new amtider(1) command to perform
USB/CDROM etc redirection, that command needed a patch to drop the use
of Linux-specific signalfd(2). I haven't tested the amtider(1) command,
feedback welcome.
Tested with thinkpad x230 (jsg@) and my t14 Gen 3, ok jsg@
Add missing header and move variable so that they're usable from the
x86-only fallback code. This undoes part of
https://github.com/Hamlib/Hamlib/commit/d20a2358606bec98e232be0a7dbbfacafe98b2ab
Tweak #ifdef check to use the default code path on Unix/Linux. We don't
implement all the features specified by _POSIX_TIMERS, but we do
implement clock_gettime(CLOCK_MONOTONIC) as required by POSIX 2008.
numpy are no longer ABI-compatible following the update to numpy 2.x.
this may over-bump slightly, but I've seen problems with at least pandas
and scipy, and identifying others individually is too time-consuming.
- enable on aarch64 (it is fiddly as the npm cache distfile must
be generated on both amd64, then again from the same tree on aarch64,
to make sure all required files are downloaded - remains to be seen
if I will be able to keep on doing this in future)
- move npm dep install stage from post-extract to do-configure to
avoid a bunch of active steps that were previously done when you
"make patch"
add annotations near COMPILER for some other ports that don't have
COMPILER_LIBCXX in WANTLIB
not changing the actual compiler version of anything here (some could
possibly remove the COMPILER line completely where they only used
COMPILER due to an old WANTLIB entry which has since stopped using
C++, but changing that is too likely to break things)
(and then, not on IBT machines) due to it using the esbuild node module, which
fetches a binary. if upstream can update to newer esbuild we should be able
to add aarch64 support and fix build on amd64 IBT.
Mikolaj Kucharski for runtime tests.
zigbee2mqtt allows you to use your Zigbee devices without the vendor's
bridge or gateway.
It bridges events and allows you to control your Zigbee devices via
MQTT. In this way you can integrate your Zigbee devices with whatever
smart home infrastructure you are using.
To use it, you will need suitable Zigbee bridge hardware (typically
USB-based), Zigbee devices, and an MQTT server (for example, mosquitto
or rabbitmq).
zigbee2mqtt has mature support for adapters based on TI zStack, SiLabs
EmberZNet, and Dresden Elektronik deCONZ. It has experimental support
for some others. Most of these are USB devices presenting as a serial
UART (/dev/cuaU*) when running the correct firmware - it has some
support for network-based (wifi/ethernet) devices.
sthen