pki/dogtag:

% svn status | grep -v ^$ | grep -v ^P | grep -v ^X | grep -v ^?
M      common/pki-common.spec
M      util/pki-util.spec

% svn commit
Sending        dogtag/common/pki-common.spec
Sending        dogtag/util/pki-util.spec
Transmitting file data ..
Committed revision 228.

Created attachment 331943 [details]
dogtag_diffs

attachment (id=331943) contains the addition of the osutil as a build-time requirement for pki-java-tools:

% svn status | grep -v ^$ | grep -v ^P | grep -v ^X | grep -v ^?
M      java-tools/pki-java-tools.spec

% svn commit
Sending        dogtag/java-tools/pki-java-tools.spec
Transmitting file data .
Committed revision 230.

pki-util not listing xerces-j2 as dependency:


Resolving Dependencies
--> Running transaction check
---> Package pki-util.noarch 0:8.0.0-12.beta set to be updated
--> Processing Dependency: jss >= 4.2.6 for package: pki-util
--> Running transaction check
---> Package jss.x86_64 0:4.2.6-1.el5idm set to be updated
--> Finished Dependency Resolution

pki-common:

Resolving Dependencies
--> Running transaction check
---> Package pki-common.noarch 0:8.0.0-12.beta set to be updated
--> Processing Dependency: tomcatjss >= 1.1.0 for package: pki-common
--> Running transaction check
---> Package tomcatjss.noarch 0:1.1.0-13.el5idm set to be updated
--> Processing Dependency: tomcat5 >= 5.5.9 for package: tomcatjss
--> Running transaction check
---> Package tomcat5.x86_64 0:5.5.23-0jpp.7.el5_2.1 set to be updated
--> Processing Dependency: xerces-j2 >= 2.7.1 for package: tomcat5
--> Running transaction check
---> Package xerces-j2.x86_64 0:2.7.1-7jpp.2 set to be updated
--> Finished Dependency Resolution

Spoke with Chandra.  Speak with him on details on how to test this.

this bug is to add xerces-j2 as BuildRequires on the spec file. 
To verify that you need to look at the source rpms not yum output.

At run time both pki-util and pki-common do not directly depend on xerces-j2.
xerces-j2 is direct run time dependency only for tomcat5

Look at rpm -q --requires <package>

To get the spec file from a source rpm, you can do rpm2cpio <source_rpm> | cpio <extract options>