Description of problem: In the spec file, it BuildRequires pkgconfig(QtOpenGL), which is being satisfied by qt-devel (ie. Qt4). I'm assuming this is an old dependency, and should be removed from the python-qt5 spec file. [root@nathanr-centos7 SPECS]# rpm -q --whatprovides 'pkgconfig(QtOpenGL)' qt-devel-4.8.5-8.el7.x86_64 [root@nathanr-centos7 SPECS]# I only discovered this after installing a new machine without Qt4 on it, and with Qt5, then trying to recompile python-qt5. Version-Release number of selected component (if applicable): python-qt5-5.3.2-4 Additional info: Here is the suggested patch: [nathanr@centos7 SPECS]$ !diff diff -u python-qt5.spec python-qt5.spec.orig --- python-qt5.spec 2014-11-11 14:55:42.992614523 +1100 +++ python-qt5.spec.orig 2014-11-11 14:55:24.215684218 +1100 @@ -38,7 +38,7 @@ BuildRequires: pkgconfig(Qt5DBus) pkgconfig(Qt5Declarative) BuildRequires: pkgconfig(Qt5Designer) BuildRequires: pkgconfig(Qt5Gui) pkgconfig(Qt5Multimedia) -BuildRequires: pkgconfig(Qt5Network) +BuildRequires: pkgconfig(Qt5Network) pkgconfig(QtOpenGL) BuildRequires: pkgconfig(Qt5Positioning) BuildRequires: pkgconfig(Qt5Quick) pkgconfig(Qt5QuickWidgets) BuildRequires: pkgconfig(Qt5Script) [nathanr@centos7 SPECS]$
I note all the other dependencies are pkgconfig(Qt5*). The pkgconfig(QtOpenGL) seems to stick out as an oversight.
Yes, that's a typo, should be Qt5OpenGL
python-qt5-5.3.2-5.fc21 has been submitted as an update for Fedora 21. https://admin.fedoraproject.org/updates/python-qt5-5.3.2-5.fc21
Package python-qt5-5.3.2-6.fc21: * should fix your issue, * was pushed to the Fedora 21 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing python-qt5-5.3.2-6.fc21' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-14962/python-qt5-5.3.2-5.fc21 then log in and leave karma (feedback).
python-qt5-5.3.2-6.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.