Hi, right. The problem doesn't occur in the test suite during the build run.
Tang's build dependencies need "libjansson4 (>= 2.10)" and everything looks fine. Installing the resulting package tang 6-1 in stretch (as-is) also works because interestingly, the above build generates a dependency in tang as "libjansson4 (>= 2.0.1)". Same for the amd64 build tang_6-1+b1 at debian.org, see https://buildd.debian.org/status/fetch.php?pkg=tang&arch=arm64&ver=6-1%2Bb1&stamp=1523611729&raw=0 In stretch, we have libjansson4 2.9-1 instead of testing/unstable 2.11-1. And this triggers the problem. On a fresh stretch system with libjansson4 2.9-1, install tang 6-1. After reboot or triggered by the activation documented in tang(8), /var/cache/tang/default.jws contains the invalid JSON as reported initially in the problem report. (This is also sent via the HTTP interface.) When using libjansson4 2.11-1, the problem is gone. I recommend depending on libjansson4 >= 2.11-1 in the binary package. Thanks and best regards, Roland
