Mathieu Peresse wrote: Mathieu, It sounds as if you may have installed Dogtag 1.2 (the most recent packages on the Dogtag site), and then perhaps checked out subversion, and attempted to replace specific packages (perhaps using pki-setup 1.3 with pki-ca 1.2)? The errors that you are seeing are a result of ongoing development on the Dogtag Subversion TIP (currently referred to as 1.3) to comply with Fedora packaging requirements: * 1.2 - /usr/share/java/pki-ca/ca/ca.jar; 1.3 - /usr/share/java/ca.jar * 1.3 - removed most of the pki "helper" scripts (e. g. - 'pkiarch', 'pkiname', and 'pkiflavor', etc.) * 1.2 - individual instances had their own instance named start/stop scripts (owned by the instance itself); 1.3 - provides a single master script (e. g. - pki-cad) which controls starting/stopping ALL instances of that subsystem type and is owned by the associated top-level PKI subsystem (this is currently being implemented for ALL Dogtag subsystems) * by default, 1.2 automatically creates a default instance upon installation of the top-level package (e. g. - pki-ca); 1.3 requires creation of an instance utilizing the pkicreate tool (which is part of the pki-setup package) --- we continue to provide code which allows removal of legacy 1.2 instances, but creation of 1.3 instances all utilize the associated 1.3 implementation It is our hope that the 1.3 release will be accepted into a future version of Fedora, at which time these changes will be documented on the Dogtag Wiki. As there are numerous ways of building and installing (individually, collectively, yum repos, SRPMS, etc.), to make certain that there isn't any problem, I might suggest when performing a yum install of 1.2, to use the associated 1.2.0 SRPMS for the related source code. If utilizing Subversion from the TIP, be certain to update ALL packages, as the 1.3 release will differ substantially from the 1.2 release. As always, we attempt to keep the TIP buildable and installable, although we do apologize for any confusion. Thanks, -- Matt