It has built, I'm not sure how useful it is without a fix for 2). Maybe one could additionally remove /usr/lib/*/qt5/plugins/bearer/libqgenericbearer.so for testing?
For 2), we should generally not deviate from upstream as a rule and also because Ubuntu has other Qt 5 users like KDE. So we need to ship ~everything in any case, possibly just not installing it all. The preferred way would be any upstream acceptable way for eg. runtime disabling of the generic backend (or the effect it causes). The second possibility, if that testing method above removing the file is enough, would be to deviate from Debian and split the libqt5network5 package into four packages. Make it not require the generic plugin to be installed (Recommends: libqt5network5-plugin-generic/nm/connman from libqt5network5), and take care the generic plugin would not be included on the touch images. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1357321 Title: QNetworkAccessManager doesn't support roaming on Ubuntu Status in Platform API: Incomplete Status in The Savilerow project: New Status in “qtbase-opensource-src” package in Ubuntu: In Progress Bug description: scope images load fine in wifi, but not on hsdpa even when there is good connectivity and browsing works well. Results are return, but images do not load. To manage notifications about this bug go to: https://bugs.launchpad.net/platform-api/+bug/1357321/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
