Update any build/runtime dependences to require the latest version of nuxwdog
Metadata Update from @mharmsen: - Custom field component adjusted to None - Custom field feature adjusted to None - Custom field fixedinversion adjusted to pki-core-10.5.4-1.fc27 - 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
master:
commit 3f9def4c5d6d6cfcc1ad2bf6b83f2bdec2030c92 (gerrit/master) Author: Matthew Harmsen <mharmsen@redhat.com> Date: Wed Jan 24 15:18:54 2018 -0700 Updated dependencies in spec files - https://pagure.io/dogtagpki/issue/2870 - openssl - https://pagure.io/dogtagpki/issue/2904 - nuxwdog - https://pagure.io/dogtagpki/issue/2911 - jss Change-Id: I1e5b5c7ea5d1f5be51e4b3eb262b04d71114f626
DOGTAG_10_5_BRANCH:
commit 9a066c1828867611b401fef2be92fa68a0b91261 (tag: v10.5.4, gerrit/DOGTAG_10_5_BRANCH) Author: Matthew Harmsen <mharmsen@redhat.com> Date: Wed Jan 24 11:13:37 2018 -0700 Updated dependencies in spec files - https://pagure.io/dogtagpki/issue/2870 - openssl - https://pagure.io/dogtagpki/issue/2904 - nuxwdog - https://pagure.io/dogtagpki/issue/2911 - jss Change-Id: I72c8ed5515c0b77034b2c9d92e8f3dfaa62a7957
Metadata Update from @mharmsen: - Issue close_status updated to: fixed - Issue set to the milestone: 10.5.4 (was: 10.5) - 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/3022
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.