GCC5 library transition for xml-security-c -- needed or not?
Dear mentors,
I'm packaging a new upstream version of xml-security-c. The previous
sid version was 1.7.2-3, which had a transition bug filed for it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791323
Simon McVittie tagged it "unreproducible", because he suspected that the
exported cxx11 symbols were not part of the API, but "weak symbols for
template instantiations". I agree, because the demangled names (as
displayed in the bug report) are not even present in the sources. But
I've got no idea what "weak symbols for template instantiations" are, so
I'm unsure; please advise.
On the other hand, the package got an NMU to deal with the transition.
Now I think that was unnecessary, but could not look into the issue at
that time, thus I didn't object. So libxml-security-c17v5 was born.
Now I'm preparing 1.7.3-1. This minor version bump won't change the SO
version, it stays at 17. I guess I have to acknowledge the NMU some
way. Should I keep the SO version change introduced by the NMU or not?
If not, should I still incorporate its changelog entry? Or just close
the (already closed and archived) transition bug in my changelog entry?
--
Thanks in advance for your kind guidance,
Feri.
Reply to: