Most of the PKI build dependencies are already specified in the spec file, but there's at least one dependency (i.e. gcc-c++, but there may be more) that is not specified in the spec file because it's assumed that the build system (i.e. Koji) will provide the package by default.
The problem is when someone tries to build PKI on a standard workstation it may fail since the gcc-c++ is not installed by default. And since it's not specified in the spec file it may not be very clear which packages are missing. To fix this all build dependencies not installed by default on a standard workstation should be specified in the spec file.
Steps to reproduce: 1. Prepare a standard workstation 2. Checkout PKI source code 3. Execute yum-builddep pki-core 4. Build PKI
Actual result: Build failed due to missing gcc-c++.
Expected result: All dependencies should be installed automatically with yum-builddep and the build should complete successfully.
Metadata Update from @edewata: - Issue set to the milestone: UNTRIAGED
This was fixed in #2228.
Metadata Update from @edewata: - Custom field feature adjusted to None - Custom field reviewer adjusted to None - Custom field version adjusted to None - Issue close_status updated to: duplicate - Issue set to the milestone: 10.3.4 (was: UNTRIAGED) - Issue status updated to: Closed (was: Open)
Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.
This issue has been cloned to GitHub and is available here: https://github.com/dogtagpki/pki/issues/2397
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.