Ongoing Qt5 Transition with ABI-Change

[melmarker]

For all of us using Qt 5 - it is a bad time to make a d-u, there is a ongoing Qt-Transition with a abi-change. That means: All progs, compiled with the former Qt5 will go because of broken dependencies. In my case: qupzilla, 2048-qt  and OwnClient.

Hände weg von einem D-U, wenn ihr Qt5 benutzt.

https://release.debian.org/transitions/html/qtbase-abi-5-3-1.html

[seasons]

Users may want to dist-upgrade libav selectively (to 10.2-1) because of the lzo security bug. https://git.libav.org/?p=libav.git;a=commit;h=ccda51b14c0fcae2fad73a24872dce75a7964996

[devil]

That bug is rather harmless, because chances of a working exploit are near null.
http://fastcompression.blogspot.de/2014/06/debunking-lz4-20-years-old-bug-myth.html


greetz
devil

[melmarker]

libav in general is dangerous. With every new version i have fears about libav format my drives instead not or false processing audio and video data. Until now it was only the second.

[ayla]

guess the transition has passed. D-u-ed tonight, no removals, qupzilla still installed and working. libav was updated, too.

[melmarker]

i guess you are completely wrong in some ponits :
- some of the missing parts i have migrated from 5.3.0 to 5.3.1 before debian - but only the ones i currently use.
- there is no qtwebkit 5.3.1 i386 as of now. that means - no qupzilla, no owncloud-client, now 2048-qt. And no LXQt with Qt5.

But amd64 work, bad luck for i386 users