This ticket needs to apply to Dogtag 10.0 as well as Dogtag 10.1.
Propose manpages for the following:
Propose commenting internally as needed:
Finally, run rpmlint on Fedora 19 to excise a number of package warnings
Proposed Milestone: 10.2.3 (per CS Meeting of 09/17/2014)
Per Dogtag 10.2.X meeting of 01/14/2015: Milestone 10.2 Backlog
As this ticket relates to a man page, no specific Bugzilla Bug is required.
This ticket was originally created for the following man pages:
However, there should be man pages for the pki-server CLI as well based on the following page: http://pki.fedoraproject.org/wiki/PKI_Server_CLI
Fix for rpmlint warnings moved to #2375.
Replying to [ticket:691 mharmsen]:
Propose manpages for the following: * pki-setup-proxy
Resolved by the following tickets:
pkidaemon
Author: Matthew Harmsen <mharmsen@redhat.com> Date: Fri Jul 17 21:25:01 2015 -0600 Added 'pkidaemon' man page.
Eventually, it has been proposed for 'pki-server' to consume the functionality currently provided by 'pkidaemon':
at which time, the 'pkidaemon.1' man page will be removed.
This ticket was originally created for the man pages listed above, however there should be man pages for the pki-server CLI as well based on the following page: http://pki.fedoraproject.org/wiki/PKI_Server_CLI
This portion of the ticket was resolved by the following ticket:
pki-server.8 pki-server-instance.8 pki-server-migrate.8 pki-server-nuxwdog.8 pki-server-subsystem.8 pki-server-upgrade.8
Propose commenting internally as needed: * /usr/share/pki/server/conf/*
This portion of the ticket was granted its own ticket:
Metadata Update from @mharmsen: - Issue assigned to mharmsen - Issue set to the milestone: 10.3.4
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/1260
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.