Bug 1811647 - %{?_isa} qualifier unnecessary / broken for BuildRequires
Summary: %{?_isa} qualifier unnecessary / broken for BuildRequires
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: CGAL
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Laurent Rineau
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-03-09 13:03 UTC by Fabio Valentini
Modified: 2020-03-09 15:34 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-09 15:18:45 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Fabio Valentini 2020-03-09 13:03:42 UTC
These lines in the CGAL .spec file are causing issues:

BuildRequires: qt5-qtbase-devel%{?_isa} >= %{qt_version}
BuildRequires: qt5-qtsvg-devel%{?_isa} >= %{qt_version}
BuildRequires: qt5-qtscript-devel%{?_isa} >= %{qt_version}
BuildRequires: qt5-qttools-devel%{?_isa} >= %{qt_version}

See: https://src.fedoraproject.org/rpms/CGAL/blob/master/f/CGAL.spec#_30-33

They cause broken dependencies on every architecture that the source package was *not* built on. For example, the currently available source package from rawhide requires:

qt5-qtbase-devel(armv7hl-32) >= 5.9
qt5-qtscript-devel(armv7hl-32) >= 5.9
qt5-qtsvg-devel(armv7hl-32) >= 5.9
qt5-qttools-devel(armv7hl-32) >= 5.9

Which creates broken dependencies on x86_64 (and every arch other than armv7hl).

Please drop the %{?_isa} qualifier from these BuildRequires, they are unnecessary and create broken dependencies.

Comment 1 Laurent Rineau 2020-03-09 15:18:45 UTC
Thanks for the report.

That is fixed by https://bodhi.fedoraproject.org/updates/FEDORA-2020-535ea4f40c.

Do you think I should backport the fix to F30/F31/F32, or just wait for the next opportunity to rebuild the package for those releases?

Comment 2 Fabio Valentini 2020-03-09 15:34:41 UTC
Thanks for fixing it!

Waiting for the next update to push this for older releases works for me. Thanks!


Note You need to log in before you can comment on or make changes to this bug.