This is needed in particular for dogtag 9 -> 10 instances , which now also need apache-commons-codec and junit jars to operate as normal.
But in general, its a good way to resolve the missing link/ moved link on upgrade problem. Better to do it here rather than in spec files.
Resolved in Dogtag 9:
commit 0ceef74b9d6ef39d2fca51c92ebab61575a59ddb Author: Matthew Harmsen <mharmsen@redhat.com> Date: Mon Aug 27 20:43:22 2012 -0700 Verify symbolic links * TRAC Ticket #301 - Need to modify init scripts to verify needed symlinks in an instance
Resolved in Dogtag 10:
commit 48e68f928f72a782afa6ab165a026901efd53b22 Author: Matthew Harmsen <mharmsen@redhat.com> Date: Mon Aug 27 20:48:34 2012 -0700 Verify symbolic links and update CS.cfg for Dogtag 10 * TRAC Ticket #301 - Need to modify init scripts to verify needed symlinks in an instance * TRAC Ticket #303 - Dogtag 10: CS.cfg parameters for Dogtag 9 instance running under Dogtag 10 packages . . .
An issue was discovered that a new instance cannot be successfully created unless it uses its "default" instance name.
Resolved in Dogtag 9 to support non-default instance names:
commit 06cf1d1c56089b3de9802c6bd4219d31908907ed Author: Matthew Harmsen <mharmsen@redhat.com> Date: Fri Sep 7 19:49:08 2012 -0700 Verify symbolic links * TRAC Ticket #301 - Need to modify init scripts to verify needed symlinks in an instance (support non-default instance names)
Resolved in Dogtag 10 to support non-default instance names:
commit 5dff3de4434aad7cce8ccfe79c061e60f1e71a05 Author: Matthew Harmsen <mharmsen@redhat.com> Date: Fri Sep 7 16:21:43 2012 -0700 Verify symbolic links * TRAC Ticket #301 - Need to modify init scripts to verify needed symlinks in an instance (support non-default instance names)
Metadata Update from @vakwetu: - Issue assigned to mharmsen - Issue set to the milestone: Dogtag 10.0.0.a1
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/872
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.