Bug#804888: djview plugin unusable in debian testing...

Rethreading to l...@bottou.org On 12/29/15, 6:28 PM, "Leon Bottou" wrote: >I've already reported a bug against qt5 for this with a little test case. > > > >And also a bug upstream referencing the debian bug... > >- L. > > > > > >On

Bug#804888: djview plugin unusable in debian testing...

I've already reported a bug against qt5 for this with a little test case. And also a bug upstream referencing the debian bug... - L. On 12/29/15, 5:12 PM, "Barak A. Pearlmutter" wrote: >So maybe the best thing would be to file a b

Bug#804888: djview plugin unusable in debian testing...

So maybe the best thing would be to file a bug against qt5, fix things in this package by using qt4, and filing a wishlist bug against this package to use qt5, with a "blocked by" referring to the qt5 bug report above. That way when the qt5 issue is resolved the wishlist bug will be unblocked and n

Bug#804888: djview plugin unusable in debian testing...

The upstream code for djview has been improved. However the core of this problem is bug http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=809367 in Stretch's Qt-5.5.1. Absent a Qt fix, we have two ugly workarounds: * Compiling djview4 using Qt-4.8 instead of Qt-5. * Have djview4 recogni

Bug#804888: djview plugin unusable in debian testing...

Not a simple one. We would have to try embedding a window and observe the discrepancy between the size reported by xwininfo and the size reported by the qt program. This seems very complex (and requires a X server..) Happy new year, btw :-) - L. On 12/29/15, 4:48 PM, "Barak A. Pearlmutter"

Bug#804888: djview plugin unusable in debian testing...

Is there any reliable way to test for the buggy version of Qt-5? Because if there is we could do something in debian/rules or some place like that to fall back to Qt-4.8 iff Qt-5 is unavailable or buggy.