Bug#796956: Explanation
Hi Lisandro,
2016-01-15 15:16 GMT+01:00 Lisandro Damián Nicanor Pérez <perezmeyer@gmail.com>:
> severity 796956 important
> thanks
>
> OK everyone this is really not a serious bug (actually I still don't think
> this is a bug at all). I'll keep it open until we get Qt 5.6 into the archive
> with a "fix".
>
> Let's start with the basics: sadly libqt5xcbqpa5 is a missnamed package. it
> should have been something along qt5-xcb-platform-plugin... because it's a
> plugin which happens to ship a private lib (that's why we accidentally
> misnamed it).
>
> Now the reasoning: Qt 5 now works with "platform" plugins and not necessarily
> just on X. That means that as long as you don't depend on X-exclusive stuff
> (or any other platform-dependant code) you can run a Qt5 app on the
> frambuffer, Wayland and other interesting places.
>
> So, strictly speaking, libqt5xcbqpa5 (which again should have been named as a
> plugin) is not a strict dependency, and thus the recommendation. And people
> not using recommendations should handle it by hand.
Since a missing libqt5xcbqpa5 would make applications crash on X which is far
more popular than framebuffer or Wayland it does not seem to be a good idea to
handle it as a pure recommendation.
Libqt5xcbqpa5 being a true plugin or not is a semantic question. Users probably
does not call a component a plugin, when and application does not start at all
on their system. Developers can call those plugins, but making them mandatory
can make users not to think about that question.
...
> I'm now leaving this non-bug opened as important just to let people now that
> there is really no bug and how to solve this issue. I will close it with Qt
> 5.6.x if we get to merge the plugins.
5.6.x is beta in experimental and I can't tell when it enters
unstable. If it does not
get uploaded to unstable in a few days with a good chance of migrating
to testing
soon please upload a fix to 5.5.x.
Otherwise wireshark would have to be updated twice, once for adding
libqt5xcbqpa5 as a dependency and once for removing it for Qt 5.6.x.
Fixing this bug for Qt fixes many other packages and it will be fixed in Qt
anyway thus please consider updating Qt 5.5 in a few days. This problem
may be an "important" one in Qt, but for every other package affected it
creates an RC bug.
Thanks,
Balint
Reply to: