thanks for the reports, I will fix this in the next couple days
Sebastian Ramacher <sramac...@debian.org> writes: > On 2020-12-30 15:06:19 +0100, Sebastian Ramacher wrote: >> Source: securefs >> Version: 0.11.1+ds-1 >> Severity: serious >> X-Debbugs-Cc: sramac...@debian.org >> >> securefs' autopkgtests hard-code dependencies on a bunch of shared >> libraries: libcrypto++6, libfuse2, libjsoncpp1, and libutf8profc2. This >> is most certainly wrong when securefs is rebuilt for transitions. At >> least the dependencies on libcrypto++6 and libjsoncpp1 are no longer >> correct. >> >> Having dependencies on the -dev packages there or installing securefs >> would make more sense to get the right runtime libraries. > > On second thought, installing securefs could also give the wrong > results. So the former would make more sense. In any case, this issue > causes autopkgtest failures: > > autopkgtest [05:13:56]: test command2: cd obj-x86_64-linux-gnu && > ./securefs_test > autopkgtest [05:13:56]: test command2: [----------------------- > ./securefs_test: error while loading shared libraries: libcrypto++.so.8: > cannot open shared object file: No such file or directory > autopkgtest [05:13:56]: test command2: -----------------------] > autopkgtest [05:13:56]: test command2: - - - - - - - - - - results - - - - - > - - - - - > command2 FAIL non-zero exit status 127 > > See > https://ci.debian.net/data/autopkgtest/testing/amd64/s/securefs/9241910/log.gz > > Cheers
