git was recently added as a dependency to include git commit id.
git
By default, the USE_GIT_COMMIT_ID and USE_TIMESTAMP should not be included in the build. This fixes the issue in Travis: https://transfer.sh/XDvT8/pkitravis.txt
USE_GIT_COMMIT_ID
USE_TIMESTAMP
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field origin adjusted to None - Custom field proposedmilestone adjusted to None - Custom field proposedpriority adjusted to None - Custom field reviewer adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None - Issue assigned to mharmsen
Metadata Update from @mharmsen: - Issue set to the milestone: 10.5
Author: Matthew Harmsen mharmsen@redhat.com Date: Fri Sep 22 15:11:11 2017 -0600
Unset build env variables By default, unset the USE_TIMESTAMP and USE_GIT_COMMIT_ID environment variables. https://pagure.io/dogtagpki/issue/2816 Change-Id: I7286892644ed65845cef7df98b22014b40c02240
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.0 (was: 10.5) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field fixedinversion adjusted to dogtag-pki-10.5.0-1.fc27, dogtag-pki-theme-10.5.0-1.fc27, pki-core-10.5.0-1.fc27, pki-console-10.5.0-1.fc27
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/2936
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.
Login to comment on this ticket.