hmmm... actually, python-qt4-core is a dependency of python-qt4 and probably contains the correct libraries. However, it is build for python 2.7

$ rpm -ql python-qt4-core-4.11.4-10.mga6 | grep "PyQt4$"
/usr/lib64/python2.7/site-packages/PyQt4

Same problem with PyQt5 now...

$ frescobaldi 
Traceback (most recent call last):
  File "/bin/frescobaldi", line 7, in <module>
    import main
  File "/usr/lib/python3.5/site-packages/frescobaldi_app/main.py", line 33, in <module>
    from PyQt5.QtCore import QSettings, QTimer, QUrl
ImportError: No module named 'PyQt5'

Fixed in Cauldron with frescobaldi-3.1.2-2.mga8. Sorry for the huge delay in investigating and fixing this.

I'll work on an update for Mageia 7 too.

Summary: frescobaldi requires pyqt4 but the requirement is not stated in the package => frescobaldi requires pyqt5 but the requirement is not stated in the package
Version: Cauldron => 7

Pushed an update with frescobaldi-3.1.2-1.mga7 and python-qt5-webengine-5.12.1-2.1.mga7 to hopefully fix dependencies in Mageia 7.


Advisory:
=========

Updated frescobaldi and python-qt5-webengine fix dependencies

  frescobaldi in Mageia 7 did not explicitly depend on all PyQt5 modules that it
  requires to work. This update fixes it, while also providing the latest version
  3.1.2 of frescobaldi.

  The python{2,3}-qt5-webenginewidgets packages now properly require the matching
  python{2,3}-qt5-webenginecore packages.

References:

 - https://github.com/frescobaldi/frescobaldi/blob/v3.1.2/ChangeLog


SRPMs in core/updates_testing:
==============================

frescobaldi-3.1.2-1.mga7
python-qt5-webengine-5.12.1-2.1.mga7


RPMs in core/updates_testing:
=============================

frescobaldi-3.1.2-1.mga7

python2-qt5-webengine-5.12.1-2.1.mga7
python2-qt5-webenginecore-5.12.1-2.1.mga7
python2-qt5-webenginewidgets-5.12.1-2.1.mga7

python3-qt5-webengine-5.12.1-2.1.mga7
python3-qt5-webenginecore-5.12.1-2.1.mga7
python3-qt5-webenginewidgets-5.12.1-2.1.mga7
python3-qt5-webengine-qsci-api-5.12.1-2.1.mga7

Source RPM: frescobaldi-2.18.2-2.mga6.src.rpm => frescobaldi-3.0.0-6.mga7, python-qt5-webengine-5.12.1-2.mga7
Assignee: rverschelde => qa-bugs

mga7, x64

Installed frescobaldi and found these libraries installed:
lib64kf5webengineviewer5-19.04.0-1.mga7
qtwebengine5-5.12.6-1.mga7
lib64qt5webenginewidgets5-5.12.6-1.mga7
lib64qt5webenginecore5-5.12.6-1.mga7
lib64qt5webengine5-5.12.6-1.mga7
but no python* webengine modules.

$ rpm -qa | grep qt5-webengine
$

frescobaldi launches from the command line and it is possible to import and display lilypond files.  Little idea of what to do after that.
Segfault when frescobaldi is closed.

Updated frescobaldi:
$ rpm -qa | grep qt5-webengine
python3-qt5-webenginewidgets-5.12.1-2.1.mga7
python3-qt5-webenginecore-5.12.1-2.1.mga7

$ rpm -q python3-qt5-webchannel
python3-qt5-webchannel-5.12.1-2.mga7

Looks like the last package was also picked up as a dependency.
But these are not - they have to be installed manually.
$ sudo urpmi python3-qt5-webengine
$ sudo urpmi python3-qt5-webengine-qsci-api

The python2 packages are not picked up as dependencies - is that relevant?
I deliberately did not install them pre-update to see if they would be picked up.
$ sudo urpmi python2-qt5-webengine
  Package                        Version      Release       Arch    
(medium "Core Release")
  python2-pyqt5-sip              4.19.16      1.mga7        x86_64  
  python2-qt5-core               5.12.1       2.mga7        x86_64  
(medium "Core Updates Testing")
  python2-qt5-webengine          5.12.1       2.1.mga7      x86_64  

$ sudo urpmi python2-qt5-webenginecore
media/core/updates_testing/
installing python2-qt5-webenginecore-5.12.1-2.1.mga7.x86_64.rpm
$ sudo urpmi python2-qt5-webenginewidgets
installing python2-qt5-webenginewidgets-5.12.1-2.1.mga7.x86_64.rpm

frescobaldi works at entry level.  Opened a lilypond file - musical score displayed.  No segfault when frescobaldi is closed.

This looks OK but leaving it for packager attention regarding the dependencies.

CC: (none) => tarazed25

It's a Python 3 application, it's normal that the python2 packages are not installed. I think everything is fine in the testing otherwise?

Keywords: feedback => (none)
Assignee: rverschelde => qa-bugs

It seems thanks you Rémi! Back to QA.

Thanks Rémi - giving this an OK.

Whiteboard: (none) => MGA7-64-OK

Validating update, Packages and Advisory in Comment 4.
Advisory pushed to SVN.

Keywords: (none) => advisory, validated_update
CC: (none) => sysadmin-bugs

An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2020-0229.html

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED