Currently, when USE_TIMESTAMP and USE_GIT_COMMIT_ID is set,compose script generates correct SRPM in the format: <name>-<version>.<timestamp>.<git_id>.<release>.src.rpm.
USE_TIMESTAMP
USE_GIT_COMMIT_ID
compose
<name>-<version>.<timestamp>.<git_id>.<release>.src.rpm
However, the RPM generated from this SRPM drops <timestamp> and <git_id>.
<timestamp>
<git_id>
Proper info must be embedded on the spec file to fix the issue.
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 set to the milestone: 10.5
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue priority set to: critical
Per CS/DS meeting of 20180122: 10.6
Metadata Update from @mharmsen: - Issue set to the milestone: 10.6 (was: 10.5)
Metadata Update from @edewata: - Issue assigned to edewata (was: mharmsen)
Fixed in master:
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue set to the milestone: 10.6.0 (was: 10.6) - 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/2972
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.