raring has seen the end of its life and is no longer receiving any
updates. Marking the raring task for this ticket as "Won't Fix".
** Changed in: qtchooser (Ubuntu Raring)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Kubuntu
Bugs, which i
saucy has seen the end of its life and is no longer receiving any
updates. Marking the saucy task for this ticket as "Won't Fix".
** Changed in: qt4-x11 (Ubuntu Saucy)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is s
Hmm, this is a bit complicated. qtchooser shouldn't be installed on non-
development machines, so KDE does not currently directly use it anyhow.
It seems that for 13.04 some KDE package was patched to forcefully add
/usr/lib/[your-arch]/qt4/bin to PATH which is why it works for most
people now (but
Hi. Thanks for the good thoughts, they clarify things well. I think I'd
be fine with both qtchooser not handling qdbus and binary moving away
from multi-arch directory. Although the direct /usr/bin/qdbus symlink
would be problematic since the executable inside qdbus-qt5 package is
still called just
Linux M3-581T 3.8.0-21-generic #32-Ubuntu SMP Tue May 14 22:16:46 UTC 2013
x86_64 x86_64 x86_64 GNU/Linux
my apology, I'm waiting for with this symbolic link, of course :
/usr/bin/qtchooser -> /usr/lib/x86_64-linux-gnu/qt4/bin/qdbus
/usr/bin/qtchooser.bk
--
You received this bug notification be
There is now a lot of progress in Debian, and qtchooser 26 got now
synced to Ubuntu thanks to Dmitry's sync request.
I should also do a sync qtbase once again to get the latest changes -
there will be qt5-triplet kind of configurations for qtchooser, they
will be again in libqt5core5 instead of -d
