[03:44] So we can keep track of things in Ubuntu — bug 1757320 [03:44] bug 1757320 in zbar (Ubuntu) "Remove Qt 4 from the archive" [Medium,New] https://launchpad.net/bugs/1757320 [08:29] @tsimonq2, Looks impressive [08:31] @mitya57: any chance the tests for armhf can be skipped in qtvirtualkeyboard debian? (while I agree that it is issue from qt side, it makes it harder for me to use qtvirtualkeyboard in Plasma Mobile :>) [08:32] (I am working on debian based plasma mobile image) [08:35] @bshah> @mitya57: any chance the tests for armhf can be skipped in qtvirtualkeyboard debian? (while I agree that it is issue from qt side, it makes it harder for me to use qtvirtualkeyboard in Plasma Mobile :, Yes, I think we can disable them [08:35] \o/ [08:36] I will try to remember about this later today :) [08:37] okay cool (and thanks) [08:41] @tsimonq2, Maybe you can also file a separate bug to track qtwebkit-source removal? [12:53] bshah, @mitya57: I just happened to ask the same to Mitya57 over into the Debian channel. The tests seems flaky, upstream is already blacklisting three of them [12:53] I'll upload to debian soon [12:54] lisandro: okay cool [15:54] @lisandro, Sorry, I did not have a chance to read IRC today. Please disable the tests on architectures where they are failing. [15:54] And maybe add a reference to https://bugreports.qt.io/browse/QTBUG-62066, I am quite sure it's the same bug [16:25] Not on all archs [16:30] On other architectures maybe it's something from this list: https://salsa.debian.org/qt-kde-team/qt/qtwebsockets/blob/master/debian/rules#L40 [16:34] nah, on qtvirtualkeyboard it's mostly flaky tests, they are even marked in test/foo/BLAKLIST by upstream [16:34] but I like how you solved that, I'll consider that for the next run [17:50] @mitya57, What's the purpose? :) [20:53] nanu_c was removed by: nanu_c [23:19] @mitya57, I figure that 19.04 gives plenty of time for packages that people care about