epel

#79 The %qt5_qtwebengine_arches macro in RHEL8
Closed: Fixed by tdawson. Opened by ellert.

Closed: Fixed
Reopen Issue

This issue was also reported to RHEL8 in bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=1757122

rpm -q --whatprovides /usr/lib/rpm/macros.d/macros.qt5-srpm

qt5-srpm-macros-5.11.1-2.el8.noarch

rpm -qi qt5-srpm-macros | grep Source

Source RPM : qt5-5.11.1-2.el8.src.rpm

The /usr/lib/rpm/macros.d/macros.qt5-srpm defines:

%qt5_qtwebengine_arches %{ix86} x86_64 %{arm} aarch64 mips mipsel mips64el

I.e. it declares that the qt5-qtwebengine package should exist on a number of architectures.

However, if I try to build a package that says:

%ifarch %{qt5_qtwebengine_arches}
BuildRequires: qt5-devel
BuildRequires: qt5-qtwebengine-devel
%endif

it fails with the error:

DEBUG util.py:593: No matching package to install: 'qt5-qtwebengine-devel'
DEBUG util.py:593: Not all dependencies satisfied

So, even though the rpm macro claims the package is available, it is not.

Should this be corrected in EPEL until it is fixed in RHEL?

Should EPEL 8 provide the missing qt5-qtwebengine package, or redeclare the %qt5_qtwebengine_arches to empty (or something that means "no arches" when used with %ifarch).

The package claims it is available for mips and Fedora doesn't ship mips so I think there is a plethora of problems I am not sure how to fix.

I am guessing epel-rpm-macros should declare %qt5_qtwebengine_arches to be empty since we aren't going to provide the package. However I would like to get some feedback from maintainers first.

EPEL8 playground does provide the qt5-qtwebengine and it's -devel package.
But it's still in -playground.

Don't have time to give my usual explanation on why it's currently in -playground only, but wanted to let you know. Please, don't mess with %qt5_qtwebengine_arches

The full KDE stack has been built for EPEL8-playground. There are many packages that use the %qt5_qtwebengine_arches so it would be good if we didn't mess with it at this time.

Why is it just in playground?
There are several KDE packages that either don't built, or have limited functionality due to and older QT5 in RHEL8, as well as missing -devel packages from RHEL8 codeready-builder.
When EPEL8 is able to do modules, we will be able to have the full KDE stack with all of it's functionality, through modules. modules will allow us to safely use the QT5 in the latest stable build of Fedora. modules will also alow us to create and use the -devel packages needed.
When we discussed with the Fedora KDE sig, whether we should deploy KDE in normal EPEL now, and then have to rip it out when we do modules, or just release what we can in EPEL8-playground until we can do modules. It was decided to release just in -playground for now. The effort required to remove all those packages, as well as the confusion it would bring when we took them out, was not worth the benefit we would get for the short period before modules came.

Also, re-reading this, the macro is correct.
The macro is not saying that qt5-qtwebengine-devel exists on those arches. It is saying that it is possible for it to built on those arches. And no other arches.

qt5-qtwebengine and qt5-qtwebengine-devel are now in EPEL8.
I believe this issue can now be closed.

Metadata Update from @tdawson:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

This issue has been migrated to Fedora Forge:
https://forge.fedoraproject.org/epel/steering/issues/79

Please continue any further discussion there.
Metadata
None
None
None
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.