#692 [MAN] pki-ca man pages
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by mharmsen.

This ticket needs to apply to Dogtag 10.0 as well as Dogtag 10.1.

Propose manpages for the following:

  • CS.cfg

Propose commenting internally as needed:

  • /usr/share/pki/ca/emails/*
  • /usr/share/pki/ca/profiles/ca/*.cfg
  • /usr/share/pki/ca/webapps/ca/admin/*
  • /usr/share/pki/ca/webapps/ca/agent/*
  • /usr/share/pki/ca/webapps/ca/ee/*
  • /usr/share/pki/ca/webapps/ca/ee/ca/*
  • remaining /usr/share/pki/ca/conf/*

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.

Fix for rpmlint warnings moved to #2375.

Per CS/DS Meeting of 08/08/2016: 10.3.6

Per PKI Bug Council of 02/09/2017: 10.3 => 10.4

Metadata Update from @mharmsen:
- Issue assigned to mharmsen
- Issue set to the milestone: 10.4

7 years ago

Metadata Update from @mharmsen:
- Custom field feature adjusted to ''
- Custom field proposedmilestone adjusted to ''
- Custom field proposedpriority adjusted to ''
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None
- Issue set to the milestone: 10.5 (was: 10.4)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: critical (was: major)

6 years ago

Metadata Update from @mharmsen:
- Issue priority set to: major (was: critical)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

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/1261

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata