Hi Joachim, Thanks, and you are right.
I had checked the built package payload and staged package tree, but I did not carry that through to the installed-state behavior. In this case, the dh_makeshlibs/ldconfig trigger creates the libpicohttpparser.so.1 symlink after installation, so my earlier SONAME concern was too strong. So please disregard that part of my previous mail. The part that still looks worth checking is the test side: - debian/changelog says the tests were changed to test the installed library with autopkgtest - I still do not find a debian/tests/ setup in the source package - and debian/rules appears to disable dh_auto_test in normal builds by filtering on "check" rather than "nocheck" So unless I am missing something else, I think the remaining question is not the SONAME link, but whether the intended test/autopkgtest coverage is really in place yet. Regards, James On Sat, 25 Apr 2026 11:03:41 +0200 Joachim Zobel wrote: > Hi. > > Thanks for reviewing this, I am actually unsure if what I did is > correct. > > Am Samstag, dem 25.04.2026 um 13:44 +0000 schrieb > [email protected]: > > - but the runtime package does not actually ship > > libpicohttpparser.so.1 -> libpicohttpparser.so.1.2 > > It actually does. After installing the package an activate-noawait > ldconfig trigger has created the link: > > $ ls -l /usr/lib/x86_64-linux-gnu/libpicohttpparser.so* > lrwxrwxrwx 1 root root 24 25. Apr 18:00 /usr/lib/x86_64-linux- > gnu/libpicohttpparser.so.1 -> libpicohttpparser.so.1.2 > -rw-r--r-- 1 root root 14248 28. Mär 10:42 /usr/lib/x86_64-linux- > gnu/libpicohttpparser.so.1.2 > > I don't know why this link is created by a trigger while the others > have to be explicitly installed. Actually I had to silence 2 library > symlink related lintian warnings, which is one of the reasons I am > unsure. But the result seems correct to me. > > Thanks, > Joachim
