[Expired for qtbase-opensource-src (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: qtbase-opensource-src (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
Is this still an issue with the latest Trusty packages?
** Changed in: qtbase-opensource-src (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203867
Title:
K
Explicitly using QT_SELECT in all Qt using packages is tentatively now a
goal on Debian side, so I'd say that's the way to go.
Qt 5 as such shouldn't interfere, it just depends on the qtchooser
configuration. It would be beneficial though to sync qt4-x11 from Debian
to bring some more fallback fun
Actually I think CMake files were contaminated by a build attempt when
it tried to use Qt 5. Starting from scratch with QT_SELECT=qt4 set from
the very beginning seems to work OK.
What about just putting
QT_SELECT := qt4
export QT_SELECT
in debian/rules of KDE packages?
--
You received this bu
My guess would be some kind of problem with KDE CMake configuration,
particularly with determining paths to Qt libraries, and not a problem
within Qt itself, am I mistaken?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
It would be better to fix this in Qt5.
** Package changed: kde-workspace (Ubuntu) => qtbase-opensource-src
(Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1203867
Title:
KDE packages FTBFS i
