Your message dated Wed, 09 Jan 2019 14:42:23 +0300
with message-id <2953531547034...@sas1-d856b3d759c7.qloud-c.yandex.net>
and subject line Re: Bug#918748: nmu: kadu_4.1-1.1
has caused the Debian Bug report #918748,
regarding nmu: kadu_4.1-1.1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
918748: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=918748
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
User: release.debian....@packages.debian.org
Usertags: binnmu
X-Debbugs-CC: sha...@debian.org
Package with qxmpp library was updated today and is successfully built for all
supported architectures: https://buildd.debian.org/status/package.php?p=qxmpp
Please schedule the binNMUs for rebuilding of kadu packages with qxmpp/1.0.0-1.
nmu kadu_4.1-1.1 . ANY . buster . -m "rebuild after update of qxmpp"
This is my first binNMUs, so please correct me if I am doing anything wrong.
Thanks,
Boris
--- End Message ---
--- Begin Message ---
>>> 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.
Ok. Thank you.
Best regards,
Boris
--- End Message ---