On 09/01/2019 10:26, Boris Pek wrote: >>> This is my first binNMUs, so please correct me if I am doing anything >>> wrong. >> >> qxmpp didn't bump the SONAME. So why does kadu need a rebuild? > > Library API was not changed, so where were no reasons to bump SOVERSION. > But it looks what there are some changes in ABI which cause to segmentation > fault during connection to XMPP network (after entering of password): > > (gdb) bt full > #0 0x00007ffff617ed98 in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #1 0x00007ffff618e7e0 in QString::compare_helper(QChar const*, int, char > const*, int, Qt::CaseSensitivity) () > at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > #2 0x00007fffe07f5fb5 in QXmppRosterManager::handleStanza(QDomElement > const&) () > at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0 > #3 0x00007fffe07d8661 in QXmppClient::_q_elementReceived(QDomElement const&, > bool&) () > at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0 > #4 0x00007fffe0820545 in () at /usr/lib/x86_64-linux-gnu/libqxmpp.so.0 > #5 0x00007ffff62e36cb in QMetaObject::activate(QObject*, int, int, void**) () > at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 > ... > > After rebuilding of kadu with new qxmpp it works fine.
Then qxmpp ABI was broken and that needs a SONAME bump on qxmpp. Cheers, Emilio
