Hi Julien, On Tue, Jun 28, 2016 at 11:46:06AM +0200, Julien Cristau wrote: > On Sun, May 29, 2016 at 14:58:51 +0200, Guido Günther wrote: > > > Upstream has an internal test suite which we enabled for the package > > builds in nspr as well as nss (+ some autopkg smoke test in nss > > itself). Howver I don't know as to what extend ABI compatibility is > > tested upstream. Hopefully Mike (cc:) may have some input on this. > > > > In order get some ideas about ABI compatibility myself I ran > > abi-compliance-tester. The results for both NSS and NSPR are also > > attached. We would do that on all point release updates. > > > > Note that the only (as to my understanding) serious regression has been > > pointed out by Florian as well: > > > > https://lists.debian.org/debian-lts/2015/11/msg00037.html > > https://bugzilla.redhat.com/show_bug.cgi?id=1260698 > > > > and it's unclear if this part of the ABI. The API break (removal of > > CERT_FindCertURLExtension) is bogus since the symbol was not exported. > > > I don't understand why you seem to be talking about ABI stability > issues. There are other kinds of bugs.
The "other kind of bugs" were the reason why I enabled the test suites in nss/nspr and started to add some autpkg tests. What else would you expect? We could also add (and run) autopkg tests for reverse dependencies of nss/nspr over time. Cheers, -- Guido