Debian Patches

Status for tinyalsa/2.0.0+git20241128-1

Patch Description Author Forwarded Bugs Origin Last update
0001-meson-add-tests-option-and-gtest-based-test-suite.patch Add a "tests" Meson option building a gtest-based test suite This wires up tests/src/*.cc (the existing gtest-based test sources, which
upstream's Meson build never builds) into a new "tinyalsa_test" executable,
gated behind a "tests" feature option (auto, like the other options in this
file). The binary is only installed, not registered as a Meson test(), since
most of the suite requires real ALSA hardware (a generic card at index 0
and, for loopback-specific tests, a snd-aloop card at index 2) and would
fail outright on any buildd. It is packaged as "tinyalsa-tests" and run via
autopkgtest instead, where a suitable testbed can be requested.		 Lukas Märdian <lukas.maerdian@oss.qualcomm.com> not-needed 2026-09-08
0002-pcm_io-hide-internal-hw_ops-and-plug_ops-symbols.patch Hide the internal hw_ops/plug_ops symbols from the shared library ABI hw_ops and plug_ops are declared in the private, non-installed src/pcm_io.h
header and are only ever used internally by src/pcm.c to select between the
real ALSA and plugin backends. They were never intended as public API (they
are not declared in any include/tinyalsa/*.h header), but since they lack a
"static" or visibility annotation, they end up with default visibility and
are exported in libtinyalsa.so's dynamic symbol table, which caused them to
be picked up by dpkg-gensymbols into debian/libtinyalsa2.symbols. Mark them
hidden so they stop leaking into the ABI, matching mixer_hw_ops/
mixer_plug_ops in src/mixer_hw.c/src/mixer_plugin.c, which are already
"static" for the same reason.		 Lukas Märdian <lukas.maerdian@oss.qualcomm.com> not-needed 2026-09-08
0003-tests-expect-avail_min-to-default-to-period_size.patch tests: expect avail_min to default to period_size Since commit 5a2ae9c ("pcm: fix for mmap usecase"), pcm_open() sets
pcm->config.avail_min to the period size if the caller passed 0. The
PcmOutTest fixture's kDefaultConfig still leaves avail_min at 0, so
PcmOutTest.GetConfig, which memcmp()s the config returned by
pcm_get_config() against kDefaultConfig, always fails. Set avail_min
explicitly to the value pcm_open() would pick anyway, which doesn't change
the behaviour of any other test using this fixture.		 Lukas Märdian <lukas.maerdian@oss.qualcomm.com> yes 2026-10-27

All known versions for source package 'tinyalsa'

Links