Hi Graham, The situation with rapidyaml mirrors c4core exactly. The package name `libryml0` is correct per Debian Policy 8.1 — it must track the embedded ELF SONAME (`libryml.so.0`), not the full versioned filename on disk. A CMake patch setting `SOVERSION` to the major version (as done in Gabriel's MR [0]) ensures a stable SONAME while allowing the on-disk library to be `libryml.so.0.11.1`. This keeps everything consistent without unnecessary transitions:
* Versioned filename: libryml.so.0.11.1 * SONAME symlink: libryml.so.0 => libryml.so.0.11.1 * Binary package: libryml0 Renaming the runtime package on every upstream release (e.g. to `libryml0.11.1`) would technically satisfy the policy but would create excessive churn during the 0.x series, even when there is no ABI break. This bug should be closed unless new evidence of an actual SONAME change emerges. [0] https://salsa.debian.org/debian/rapidyaml/-/merge_requests/1 Regards, Fukui
