Comment 10 for bug 1987678

OK, so to make sure I understand: nothing in the archive is directly affected by this bug. But if a user builds their own thing with both jansson and json-c, then the symbol conflict arises.

I think this is still fine in principle to SRU, but I would like your out-of-archive component (vvas) tested against the proposed pocket as part of the SRU verification please, and your confirmation that the problem is fixed, before we release it.

Separately, above I asked:

> On the specific fix, there is quite a bit of noise here. Did you consider cherry-picking the symbol versioning change only? I think this should be safe and not an ABI break, but I'm not that familiar in this area. Is there something I'm missing - why is a backport required instead?

I think this question is still outstanding. Why can we not make the minimal necessary changes?