Fixed in master branch:

• https://github.com/dogtagpki/pki/commit/a6b6cd07ba3a1c3554afe70aa999e437d7a61fbb
• https://github.com/dogtagpki/pki/commit/b63892eebc633fa592ed089de79793eaf7e8c967
• https://github.com/dogtagpki/pki/commit/be8b0ff95ab316260374ab6d0ac9f420da26f753
• https://github.com/dogtagpki/pki/commit/64c8c9824ee74c3f5d7975eb87833679c1052c9f

mharmsen's comments:

(1) I would like a couple of comment lines added (a) after the "Source:" line, add a comment placeholder for patches -- # Patches and (b) after the "%autosetup" line, add in a # Apply Patches comment placeholder, (2) since build.sh moves all of the RPMS out under <work_dir>/RPMS, have it remove the empty directoris (RPMS/noarch and RPMS/<arch>);

Per discussion with mharmsen we may need to:

• provide an option to generate an srpm that will generate certain packages only (e.g. base, ca, kra).
• provide an option to override the %{?dist} macro
• generate tarball and patch files from git repo and include it automatically in srpm
• provide an option to squash the patch files into a single file

Need to add -S to use git-style patches (see http://rpm.org/user_doc/autosetup.html). No need to add # Apply Patches.

Please apply the following "tweak" to "build.sh" to allow specifying work-dir=<relative dir>.

        work-dir=?*)
-              WORK_DIR="$LONG_OPTARG"
+              WORK_DIR=`readlink -f "$LONG_OPTARG"`

in order to allow users to specify relative directory paths to override $WORK_DIR

This depends on ticket #1547.

The 4 source packages have been reduced into just 2 packages:

• pki-core now contains base, ca, kra, ocsp, tks, tps, and console subpackages
• dogtag-pki now contains theme and meta subpackages

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

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.