packages, branch master

pulseaudio: detect intl and iconv through meson dependency objects

2026-09-14T15:46:54Z

The build probes for dgettext and iconv_open with bare symbol checks, which succeed against libc even when a standalone GNU libintl or libiconv is on the include path. Their headers redirect the calls to libintl_* and libiconv_* symbols, so the objects then need -lintl, which the Makefile supplied through TARGET_LDFLAGS for every link, and the standalone libiconv was bypassed through LIBICONV_PLUG. Add the two patches from upstream merge request 877, which switch the probes to meson's intl and iconv dependency objects. These compile a test including the header, so they fall back to linking the library exactly when the header requires it. With BUILD_NLS this links libintl-full and libiconv-full where they are used; without it, the libc implementations are used as before. The second patch makes the libm link conditional in the same way. Drop the -lintl workaround. Patches taken from merge request currently under review upstream: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/877 Signed-off-by: Mirko Vogt

pulseaudio: switch to git snapshot

2026-09-14T15:46:54Z

The last release, 17.0, dates from January 2024. Master has since accumulated fixes not available in any release, among them the SAP port byte order in module-rtp-recv, an out-of-bounds access in stream_get_timing_info_callback, multichannel processing in module-echo-cancel and several JSON UTF-8 handling fixes. Switch to the current master head. The snapshot tarball carries neither a .git directory nor the .tarball-version file of a release tarball, so git-version-gen has no source for the version string and meson would fail parsing the empty result. Write .tarball-version in Build/Prepare from the last release tag reachable from the snapshot plus the abbreviated commit, so the library version and the libpulsecommon file name derive from 17.0 as the build's own git describe would. Keep PKG_VERSION at 17.0 instead of the date-derived default, so the package version matches what the libraries and binaries report, the CI version check finds it in the --version output, and a later switch back to a release tarball still sorts as an upgrade. PKG_SOURCE_DATE and PKG_SOURCE_VERSION identify the snapshot, and the repacked tarball carries both in its name so that a later snapshot does not collide with this one in the download directory and on the source mirror. Upstream turned the doxygen and tests options into feature options; pass disabled instead of false. Normalise the indentation of the last three MESON_ARGS entries while touching them. Signed-off-by: Mirko Vogt

pulseaudio: split out libpulse client library

2026-09-14T15:46:54Z

Move the PulseAudio client libraries into a separate libpulse package, so a client can depend on just the client library instead of pulling in the whole daemon. Upstream ships three libraries whose names do not make the split obvious: libpulse and libpulse-simple are the client API, libpulsecommon is a private library shared by client and server, and libpulsecore is the server core used only by the daemon and its modules. libpulse, libpulse-simple and libpulsecommon go into the new package; libpulsecore, libpulsedsp and the module helper libraries stay with pulseaudio-daemon, which now depends on libpulse. The iconv and gettext users (pulse/utf8.c and pulsecore/i18n.c) are part of libpulsecommon, so libpulse carries the ICONV_DEPENDS and INTL_DEPENDS itself. Enable D-Bus support in both variants, not just the avahi one. D-Bus support adds the pa_dbus_* and rtkit helpers to libpulsecommon, which the daemon and its modules link against and which now ships in libpulse. Since a single libpulse package serves both variants, it has to be built the same way in both, or the avahi daemon would end up with a libpulsecommon lacking those symbols. Unconditional D-Bus support is the simplest way to achieve that; the price is that pure clients now pull in libdbus. Two follow-on changes: the D-Bus policy file, previously installed by the avahi variant only, is now installed by both daemon variants. The daemon also declares its own libdbus dependency, independent of libpulse, because libpulsecore links libdbus directly. Signed-off-by: Mirko Vogt

comrade: update to 0.2.2

2026-09-14T10:56:06Z

Since 0.2.0 comrade uses 64-bit atomics and its CMake links libatomic where the compiler cannot inline them; depend on it through ATOMIC64_DEPENDS under the same condition. Upstream changes: https://github.com/dangowrt/comrade/compare/v0.1.17...v0.2.2 Signed-off-by: Daniel Golle

prplmesh: add package

2026-09-14T08:45:49Z

Add the prplMesh 6.0.1 EasyMesh controller and agent for stock OpenWrt. The package keeps the installed hostapd/wpad stack and drives it over the existing UCI, ubus, nl80211 and hostapd control sockets. The hostapd control interface client is a small self-contained implementation added by patch 120, so no hostapd source tree is downloaded, bundled or duplicated at build time and the system hostapd stays the only hostapd. Binaries install under /usr/libexec/prplmesh, read-only data under /usr/share/prplmesh, shared libraries under /usr/lib, configuration under /etc/config/prplmesh. Of the prplOS helper scripts only prplmesh_utils.sh is installed: patch 161 teaches its platform guard stock OpenWrt and the init's daily log roller invokes it; the other helpers stay uninstalled. Its option parsing needs util-linux getopt (the busybox applet is off by default), hence the getopt dependency. At build time prplMesh generates its IEEE 1905 / EasyMesh TLV classes from YAML definitions with its own Python generator, hence the host Python and PyYAML build dependencies. Stock builds run without NBAPI, so the controller skips the CurrentOperatingClassProfile data-model cleanup for radios without a data model path, and legacy vendor diagnostic measurements default to off while standard EasyMesh metrics stay enabled. The controller also registers radios that appear only in Topology Responses: some stock agents never run WSC onboarding for a band (Wi-Fi 7 units and their 6 GHz radio), and such radios, their BSSes and their clients stayed invisible otherwise. Agents in turn import clients that are already associated when the agent starts: patch 150 walks hostapd's STA-FIRST/STA-NEXT list on the nl80211 AP and monitor HALs and reconciles the result every 60 seconds, so stations that associated while the agent was down appear without waiting for a reassociation, and stale entries are disconnected only after a cleanly enumerated sweep. The init preflights every binary the selected management mode needs before registering any procd instance, and the example credentials ship empty so an enabled but unconfigured service fails validation loudly instead of deploying a published passphrase. A test-version.sh verifies the installed version from the shipped version file instead of probing daemons, and a test.sh checks the shipped log levels and the roll-helper install. Production log levels default to error, info, warning and fatal for file and syslog output of both daemons. Log retention is enforced by the upstream roll helper (its platform guard now accepts openwrt): the init prunes previous-boot logs once per boot before the daemons come up (a /var/run stamp keeps procd reload triggers, which re-enter start_service with the daemons live, from re-rolling their logs) and a procd-supervised roller repeats the roll daily; an image stripped of the helper runs without rotation instead of refusing to start. Link-metrics reporting no longer warns about wireless-capable radios deliberately not used for backhaul. An earlier revision of this integration, differing only in the wpa_ctrl client origin and the install prefix, runs on OpenWrt 25.12.5 mediatek/mt7622 with two Ethernet-connected EasyMesh agents. Ref: https://gitlab.com/prpl-foundation/prplmesh/prplMesh Ref: https://gitlab.com/kreout/prpl-mesh-mercusys/-/merge_requests/1 Signed-off-by: Andrei Ovcharenko

dnsproxy: update to 0.84.2

2026-09-14T08:29:17Z

Update dnsproxy to upstream version 0.84.2. Release notes: - Updated Go to 1.26.8 - Fixed DoQ 0-RTT opcode handling Signed-off-by: Tawhidul Islam

hcxdumptool: pass TARGET_LDFLAGS and restore -std=gnu99

2026-09-14T04:14:47Z

Command-line CFLAGS overrides upstream's CFLAGS += -std=gnu99. Pass TARGET_LDFLAGS for OpenWrt PIE/RELRO, and keep -lpcap which that override would otherwise drop. Signed-off-by: Atanas Vladimirov

hcxtools: pass TARGET_LDFLAGS and restore -std=gnu99

2026-09-14T04:14:47Z

Command-line CFLAGS overrides upstream's CFLAGS += -std=gnu99. Without TARGET_LDFLAGS the tools also skip OpenWrt PIE/RELRO link flags. Signed-off-by: Atanas Vladimirov

hcxtools: update to version 7.1.2

2026-09-14T04:14:47Z

Match hcxdumptool 7.1.2. Use the upstream Makefile instead of meson, whose version is still 6.3.2. Add hcxpottool and drop unused libpcap. Full changelog here: https://raw.githubusercontent.com/ZerBea/hcxtools/refs/tags/7.1.2/changelog Signed-off-by: Atanas Vladimirov

hcxdumptool: build hcxdumptool target only

2026-09-14T04:14:47Z

Leaving hcxnmealog out is intentional. It is the GPS/wardriving helper that was split out of hcxdumptool in 6.3.5. It needs a GPS receiver (USB NMEA device such as /dev/ttyACM0, or gpsd wrapping one) and is not used for the usual handshake/PMKID capture on a stationary router. Signed-off-by: Atanas Vladimirov