Description of problem: BuildRequires: /usr/bin/execstack cannot be satisfied when building for EPEL7 on aarch64 and ppc64le. Version-Release number of selected component (if applicable): prelink-0.5.0-9.el7 How reproducible: Always. Steps to Reproduce: 1. Try building any package with BuildRequires: /usr/bin/execstack on epel7/aarch64 or epel7/ppc64le Actual results: DEBUG util.py:439: Error: No Package found for /usr/bin/execstack Expected results: Successful build.
Red Hat maintainer doesn't want to build prelink for these two arches, so a limited-arch EPEL package is required.
I requested an epel7 branch for execstack: https://admin.fedoraproject.org/pkgdb/package/requests/12565
I think you were supposed to build this for aarch64 and ppc64le ONLY. It's available on other EPEL7 arches already as part of prelink and you're violating EPEL policy by conflicting with the existing prelink package. Please untag your build as soon as possible.
Ah, sorry, I haven't noticed it was a scratch build from SRPM. Please disregard comment 3.
(In reply to Dominik 'Rathann' Mierzejewski from comment #3) > I think you were supposed to build this for aarch64 and ppc64le ONLY. It's > available on other EPEL7 arches already as part of prelink and you're > violating EPEL policy by conflicting with the existing prelink package. > Please untag your build as soon as possible. Yeah, it was meant as a test, but thanks for reminding me to set ExclusiveArch.
execstack-0.5.0-11.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-cb6ae5d6d4
execstack-0.5.0-11.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report. See https://fedoraproject.org/wiki/QA:Updates_Testing for instructions on how to install test updates. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-cb6ae5d6d4
execstack-0.5.0-11.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.