Description of problem: psi-plus is built against obsolete qtwebkit. Version-Release number of selected component (if applicable): - How reproducible: yes Steps to Reproduce: 1. # dnf install psi-plus-plugins 2. start psi-plus 3. Actual results: Dependency to qtwebkit. Expected results: No dependency to qtwebkit and maybe to qtwebengine instead. Additional info: Am 19.04.19 um 10:51 schrieb Vitaly Tonkacheyev:> I do not know exactly why there is a web server, but the lead developer > and project owner (Rion) says that 2 years ago, when the support for the > qtwebengine was added, there was no other way out. Something related to > chat identification. > > чт, 18 апр. 2019 г., 23:25 Kevin Kofler <kevin.kofler > <kevin.kofler>>: > > Hi, > > Am Donnerstag, 18. April 2019 19:17:26 CEST schrieb Vitaly Tonkacheyev: > > Psi-plus (psi-im) already has support of QtWebEngine enabled by > default > > > https://github.com/psi-im/psi/blob/1a2628bf3830bc24a54744e2ad4bf2a2c00efa0d/CMakeLists.txt#L39 > > > > To use qtwebengine you need to update BuildRequires > > from > > BuildRequires: cmake(Qt5WebKit) > > BuildRequires: cmake(Qt5WebKitWidgets) > > to > > BuildRequires: cmake(Qt5WebEngine) > > BuildRequires: cmake(Qt5WebEngineWidgets) > > BuildRequires: cmake(Qt5WebChannel) > > I think this (building against QtWebEngine) is probably the better > option > than > QtWebKit at this point. Even annulen's fork (which we ship in > Fedora) has > not > seen a release for almost 2 years now! This means it is also horribly > bitrotting security-wise. (The last release from Nokia was of course > even > worse.) But… > > > But with qtwebengine support psi uses bundled 3rdparty libraries > qhttp > > and http-parser (submodules in our psi-im/psi repository > > https://github.com/psi-im/psi/tree/master/3rdparty ) > > … ewww, WTF?! Why does Psi need a custom HTTP SERVER (!) to serve > web pages > to > QtWebEngine?! There ought to be a better way to do this! :-( > > Kevin Kofler
Getting maintainers of qt5-qtwebengine into this. We've already discussed intials by e-mail, see below.
If psi-plus supports qtwebengine, I see no reason not to switch to it.
@Rex Please notice the comment about needs for an internal server. And: > Psi-plus (psi-im) already has support of QtWebEngine enabled by default > https://github.com/psi-im/psi/blob/1a2628bf3830bc24a54744e2ad4bf2a2c00efa0d/CMakeLists.txt#L39 Maybe first step is to ask maintainer of psi to switch as well, as psi-im is the source base for psi-plus.
Well, I expect this to not happen any soon.
new maintainer.
FEDORA-2020-c765787a4c has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-c765787a4c
FEDORA-2020-c765787a4c has been pushed to the Fedora 32 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-c765787a4c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-c765787a4c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-c765787a4c has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-4e8fd65187 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-4e8fd65187
FEDORA-2020-4e8fd65187 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-4e8fd65187` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-4e8fd65187 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-4e8fd65187 has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.